Bug 104319

Summary:

AMDGPU/DC: Internal display corrupted when connecting (mirroring/extending) an external monitor on HDMI

Product:

DRI

Reporter:

Carlo Caione <carlo>

Component:

DRM/AMDgpu

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

medium

CC:

harry.wentland, jordan.lazare

Version:

XOrg git

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
dc-mirroring-journal	none
dc-warning-hdmi-detached	none
dc-extended-journal	none

Description Carlo Caione 2017-12-18 13:05:41 UTC

Created attachment 136245 [details]
dc-mirroring-journal

Same machine as on the https://bugs.freedesktop.org/show_bug.cgi?id=104281 but reproduced on multiple ACER laptops.

Using the latest Linus master compiled with CONFIG_DRM_AMD_DC_PRE_VEGA=y we have that sometimes the image on the internal panel gets corrupted when mirroring on an external HDMI display (see [0]).

We have verified that this is a regression introduced by the DC code. In attachment the journal output.

[0] https://imgur.com/a/rnItJ

Comment 1 Carlo Caione 2017-12-18 13:08:44 UTC

Created attachment 136246 [details]
dc-warning-hdmi-detached

We have also verified that when disconnecting the HDMI cable, the system is not stable anymore, with corruption and flickering on the internal panel also without the HDMI cable connected.

As you can see from the attached journal that the log is filled with WARNINGS from the DC code.

Comment 2 Carlo Caione 2017-12-18 13:53:37 UTC

Created attachment 136248 [details]
dc-extended-journal

I just reproduced the same issue this time with the external HDMI monitor in extended mode, not mirroring. It attachment the log.

Comment 3 Daniel Drake 2017-12-21 12:28:38 UTC

Need to do more testing to be sure, but it appears that this is not reproducible on the development branch https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next

Comment 4 Harry Wentland 2017-12-21 14:57:48 UTC

Thanks, Daniel. The fix should land for 4.16 then.

Comment 5 Harry Wentland 2018-04-24 18:54:42 UTC

Marking resolved as reported to work fine on amd-staging-drm-next. If this is still an issue feel free to reopen.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.