Bug 107072 - 4k hdmi monitor stays black on kaveri [regression]
Summary: 4k hdmi monitor stays black on kaveri [regression]
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-29 19:49 UTC by Clemens Eisserer
Modified: 2019-11-19 08:42 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg-log + strack traces (89.01 KB, text/plain)
2018-06-29 19:55 UTC, Clemens Eisserer
no flags Details
xorg log file with 4.17.3 (51.00 KB, text/plain)
2018-07-05 13:07 UTC, Clemens Eisserer
no flags Details

Description Clemens Eisserer 2018-06-29 19:49:19 UTC
After updating Fedora 28 on my Kaveri System (A8-7650K) with AMDGPU enabled from 4.16.16 to 4.17.2 my 4K HDI display stays black (the FHD display connected via HDMI continues to work as expected).

Please let me know what kind of information is required find the root cause.
Comment 1 Clemens Eisserer 2018-06-29 19:50:29 UTC
correction: the FHD monitor is not connected via HDMI, but DVI
Comment 2 Clemens Eisserer 2018-06-29 19:55:03 UTC
please find attached the dmesg output including some stack-traces.
Comment 3 Clemens Eisserer 2018-06-29 19:55:32 UTC
Created attachment 140392 [details]
dmesg-log + strack traces
Comment 4 Clemens Eisserer 2018-06-29 19:57:55 UTC
I am using amdgpu after a rather severe performance regression was introduced  with commit8b3a257851905ff444d981e52938cbf2b36ba830 which hits glamor for certain workloads pretty hard. 

AMDGPU didn't suffer that much from this change: https://bugs.freedesktop.org/show_bug.cgi?id=105171
Comment 5 Alex Deucher 2018-06-29 20:15:24 UTC
What mode are you trying to run on your monitor?  Can you attach your xorg log if you are using X?  Might be related to bug 106959.
Comment 6 Michel Dänzer 2018-07-02 08:06:57 UTC
Does amdgpu.dc=0 avoid the problem? DC will be disabled by default again for Kaveri.
Comment 7 Clemens Eisserer 2018-07-05 13:07:21 UTC
Created attachment 140472 [details]
xorg log file with 4.17.3
Comment 8 Clemens Eisserer 2018-07-05 13:10:42 UTC
amdgpu.dc=0 did the trick - behaviour is back to normal.

I guzess it is not related to  bug 106959. - kaveri doesn't support HDMI2, so my refresh rate was 30Hz even with the old display stack.
Comment 9 Pontus Gråskæg 2018-08-14 19:24:57 UTC
Looking at your dmesg output, it looks like you might have hit this bug/issue: bug 105880

"[dc] No support for LVDS or VGA connectors (Cannot find any crtc or sizes)"

AMD/Harry Wentland/Alex Deucher have commits in the mainline kernel to disable the DC code by default for Bonaire, Kabini, Kaveri, and Mullins as certain hardware interfaces are not supported in the DC code. Your cpu (from dmesg) is an AMD A8-7650K Radeon R7, codename Kaveri.

The clue in dmesg output is the following errors:

[   14.186318] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3
[   14.186458] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
[   14.186592] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3
[   14.186725] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3

You might try forcing amdgpu.dc=0 in the kernel command line to ensure you use the old driver code.

graaskaeg
Comment 10 Alex Deucher 2018-08-15 18:03:48 UTC
(In reply to Pontus Gråskæg from comment #9)
> Looking at your dmesg output, it looks like you might have hit this
> bug/issue: bug 105880
> 
> "[dc] No support for LVDS or VGA connectors (Cannot find any crtc or sizes)"
> 
> AMD/Harry Wentland/Alex Deucher have commits in the mainline kernel to
> disable the DC code by default for Bonaire, Kabini, Kaveri, and Mullins as
> certain hardware interfaces are not supported in the DC code. Your cpu (from
> dmesg) is an AMD A8-7650K Radeon R7, codename Kaveri.

Unless you are using VGA or LVDS connectors this is a different issues.  That does not seem to be the case here (HDMI and DVI are supported in the DC code).
Comment 11 Alex Deucher 2018-08-15 18:07:22 UTC
This is likely a duplicate of bug 106940.
Comment 12 Alex Deucher 2018-08-15 18:08:55 UTC
Does reverting f0c0761b38ac30b04d4fed436ff10e894ec0e525 help?
Comment 13 Pontus Gråskæg 2018-08-15 18:11:44 UTC
OK, I was misled by the errors in the dmesg log:

[   14.186318] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:1! type 0 expected 3
[   14.186458] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
[   14.186592] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3
[   14.186725] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3

Apologies for the misconception.

graaskaeg
Comment 14 Martin Peres 2019-11-19 08:42:46 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/436.


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.