Bug 200695 - Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected)
Summary: Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-31 18:32 UTC by Claude Heiland-Allen
Modified: 2019-04-02 23:34 UTC (History)
11 users (show)

See Also:
Kernel Version: 4.17.19, 4.18.5 -- 4.18.20, 4.19-rc1 -- 4.19.32, 4.20-rc1 -- 4.20.17, 5.0-rc1 -- 5.0.5, 5.1-rc3
Tree: Mainline
Regression: No


Attachments
dmesg after boot with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6 (88.77 KB, text/plain)
2018-07-31 18:32 UTC, Claude Heiland-Allen
Details
dmesg after replugging monitor with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6 (121.06 KB, text/plain)
2018-07-31 18:33 UTC, Claude Heiland-Allen
Details
dmesg after boot with amdgpu.dc=0 drm.debug=6 (125.36 KB, text/plain)
2018-07-31 18:34 UTC, Claude Heiland-Allen
Details
Xorg.0.log with amdgpu=1 (65.20 KB, text/plain)
2018-07-31 18:37 UTC, Claude Heiland-Allen
Details
Xorg.0.log with amdgpu.dc=0 (59.73 KB, text/plain)
2018-07-31 18:37 UTC, Claude Heiland-Allen
Details
xorg.conf (5.16 KB, text/plain)
2018-07-31 18:38 UTC, Claude Heiland-Allen
Details
dmesg for 4.19-rc1 amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6 (90.82 KB, text/plain)
2018-08-28 15:42 UTC, Claude Heiland-Allen
Details
dmesg logs after booting to X with displays connected to both DVI and HDMI (50.38 KB, application/x-bzip-compressed-tar)
2019-04-02 16:38 UTC, Claude Heiland-Allen
Details

Description Claude Heiland-Allen 2018-07-31 18:32:58 UTC
Created attachment 277633 [details]
dmesg after boot with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6

When amdgpu.dc=1 is initialized at boot, the console goes blank as it thinks all displays are disconnected.  Xorg is not able to enable the display either.  With amdgpu.dc=0 all is fine.  Tried with various (mostly Debian) kernels from 4.16 through 4.18~rc4, all have the issue.  I built a 4.18~rc7 from kernel.org to rule out Debian patches being the issue and will provide logs.
Comment 1 Claude Heiland-Allen 2018-07-31 18:33:49 UTC
Created attachment 277635 [details]
dmesg after replugging monitor with amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6
Comment 2 Claude Heiland-Allen 2018-07-31 18:34:24 UTC
Created attachment 277637 [details]
dmesg after boot with amdgpu.dc=0 drm.debug=6
Comment 3 Claude Heiland-Allen 2018-07-31 18:37:12 UTC
Created attachment 277639 [details]
Xorg.0.log with amdgpu=1
Comment 4 Claude Heiland-Allen 2018-07-31 18:37:40 UTC
Created attachment 277641 [details]
Xorg.0.log with amdgpu.dc=0
Comment 5 Claude Heiland-Allen 2018-07-31 18:38:49 UTC
Created attachment 277643 [details]
xorg.conf
Comment 6 Claude Heiland-Allen 2018-08-28 15:40:23 UTC
still an issue with 4.18.5

still an issue with 4.19-rc1, I will attach dmesg
Comment 7 Claude Heiland-Allen 2018-08-28 15:42:13 UTC
Created attachment 278167 [details]
dmesg for 4.19-rc1 amdgpu.dc=1 amdgpu.dc_log=1 drm.debug=6
Comment 8 Claude Heiland-Allen 2018-09-06 06:51:53 UTC
still an issue with 4.18.6

still an issue with 4.19-rc2

if you need more logs, let me know which boot options I should add

console displays fine on first boot but after a few seconds dmesg reports
[    5.318879] [drm] Cannot find any crtc or sizes
and screen goes blank, and the monitor turns itself off after a few moments
Comment 9 Claude Heiland-Allen 2018-09-10 13:45:33 UTC
still an issue with 4.18.7

still an issue with 4.19-rc3
Comment 10 Andrey Arapov 2018-09-17 17:46:20 UTC
Could you try enabling CONFIG_DRM_AMD_DC_PRE_VEGA option when rebuilding the kernel and see if that works with amdgpu.dc=1 ?
Comment 11 Andrey Arapov 2018-09-17 18:09:29 UTC
Oh, that option is gone from 4.18.
Comment 12 Claude Heiland-Allen 2018-09-18 02:10:01 UTC
not an issue with 4.14.70 (I think it does not have amdgpu.dc as an option?)

still an issue with 4.17.19 compiled with CONFIG_DRM_AMD_DC_PRE_VEGA=y

still an issue with 4.18.8

still an issue with 4.19-rc4
Comment 13 Andrey Arapov 2018-09-18 13:43:20 UTC
Could you please try reverting this commit https://github.com/torvalds/linux/commit/e03fd3f300f6184c1264186a4c815e93bf658abb , rebuilding your kernel and let us know if it fixes your issue?

Not sure if your problem is related to mine here https://github.com/Dunedan/mbp-2016-linux/issues/73#issuecomment-422397681

But it has helped in my case.
Comment 14 Claude Heiland-Allen 2018-09-18 15:02:45 UTC
I checked out linux v4.19-rc4 from git, then reverted that commit - no change, display goes blank about 5 seconds into boot.

I noticed something else in the dmesg (it was there in 4.19-rc1,rc2,rc3,rc4,rc4 with reverted commit, but not earlier versions):

[    5.109572] amdgpu: [powerplay] Failed to retrieve minimum clocks.
[    5.109577] amdgpu: [powerplay] Error in phm_get_clock_info 
[    5.109627] [drm] DM_PPLIB: values for Engine clock
[    5.109629] [drm] DM_PPLIB:	 300000
[    5.109631] [drm] DM_PPLIB:	 600000
[    5.109632] [drm] DM_PPLIB:	 900000
[    5.109633] [drm] DM_PPLIB:	 1145000
[    5.109634] [drm] DM_PPLIB:	 1215000
[    5.109636] [drm] DM_PPLIB:	 1257000
[    5.109637] [drm] DM_PPLIB:	 1300000
[    5.109638] [drm] DM_PPLIB:	 1366000
[    5.109640] [drm] DM_PPLIB: Validation clocks:
[    5.109641] [drm] DM_PPLIB:    engine_max_clock: 136600
[    5.109642] [drm] DM_PPLIB:    memory_max_clock: 200000
[    5.109644] [drm] DM_PPLIB:    level           : 8
[    5.109646] [drm] DM_PPLIB: values for Memory clock
[    5.109647] [drm] DM_PPLIB:	 300000
[    5.109648] [drm] DM_PPLIB:	 1000000
[    5.109649] [drm] DM_PPLIB:	 2000000
[    5.109651] [drm] DM_PPLIB: Validation clocks:
[    5.109652] [drm] DM_PPLIB:    engine_max_clock: 136600
[    5.109653] [drm] DM_PPLIB:    memory_max_clock: 200000
[    5.109655] [drm] DM_PPLIB:    level           : 8
[    5.124083] [drm] Display Core initialized with v3.1.59!

The last (largest) value for "engine clock" and "memory clock" are 10x the validation values for "engine clock max" and "memory clock max".  I see in the amd/powerplay sources some values are in units of 10kHz, some in units of 1kHz(?) - maybe a conversion was missed somewhere? Or maybe the printout is totally normal and I know nothing :)

The error message common to all kernels with amdgpu.dc=1 since 4.17 is:

[    5.256378] [drm] Cannot find any crtc or sizes
Comment 15 Claude Heiland-Allen 2018-10-01 17:30:48 UTC
still an issue in 4.18.9
still an issue in 4.18.10
still an issue in 4.18.11
still an issue in 4.19-rc5
still an issue in 4.19-rc6
Comment 16 Claude Heiland-Allen 2018-10-10 21:16:44 UTC
still an issue in 4.18.12
still an issue in 4.18.13
still an issue in 4.19-rc7
Comment 17 Claude Heiland-Allen 2018-10-22 18:52:39 UTC
still an issue in 4.18.14
still an issue in 4.18.15
still an issue in 4.18.16
still an issue in 4.19-rc8
still an issue in 4.19
Comment 18 Claude Heiland-Allen 2018-11-06 16:13:10 UTC
still an issue in 4.18.17
still an issue in 4.19.1
still an issue in 4.20-rc1 (configured with HSA enabled)
Comment 19 Claude Heiland-Allen 2018-11-13 19:54:47 UTC
still an issue in 4.18.18
still an issue in 4.20-rc2
Comment 20 Claude Heiland-Allen 2018-11-19 18:15:05 UTC
still an issue in 4.18.19
still an issue in 4.19.2
still an issue in 4.20-rc3
Comment 21 Claude Heiland-Allen 2018-12-04 23:12:59 UTC
still an issue in 4.18.20 4.19.3 4.19.4 4.19.5 4.19.6 4.20-rc4 4.20-rc5
Comment 22 Dev Bazilio 2018-12-28 06:07:45 UTC
> amdgpu: [powerplay] Failed to retrieve minimum clocks. 
Confirmed, I started getting this error and entire black screen from 4.19.4 and all latest kernels

product: Lexa PRO [Radeon RX 550/550X]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
Comment 23 Alex van Kaam 2019-01-12 11:18:30 UTC
same issue with an HP Notebook - 17-ca0710nd
Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da)
Kernel 4.19.12

need to use amdgpu.dc=0 OR video=1024x768M@60m to get the build in screen to work
Comment 24 Claude Heiland-Allen 2019-01-13 19:35:39 UTC
still an issue in 4.19.15 4.20.2 5.0-rc1 (I didn't check intermediate versions since comment 21 above https://bugzilla.kernel.org/show_bug.cgi?id=200695#c21 )

[drm] Cannot find any crtc or sizes

followed by screen going blank, monitor turning off, no display detected
Comment 25 Claude Heiland-Allen 2019-02-25 17:51:28 UTC
still an issue in 4.19.25 4.20.12 5.0-rc8 (I didn't check intermediate versions since comment 24 above)
Comment 26 Alex van Kaam 2019-02-26 16:43:44 UTC
hi

on request of the people over at SUSE I tested my Tumbleweed install with the Kernel of the Day.

first did:  BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet

and it booted with a screen

then did:   BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet amdgpu.dc=1

and it also booted with a screen

so on this specifik hardware HP Notebook - 17-ca0710nd, Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] it seems to be fixed
Comment 27 Dev Bazilio 2019-02-27 12:42:16 UTC
My RX550 is successfully booted up with 4.20 kernels and newer, but my OS freezes every minute for 30 secs if I open youtube or play game, and anything doesn't work upon freeze - I couldn't move mouse or press REISUB. Entire system is stuck. I downgraded kernel to 4.14 - and it works like a charm without lags/freezes/stucks. And it seems 4.14 doesn't have AMD DC (amdgpu.dc=0 doesn't work for me)
Comment 28 Bogomil Vasilev 2019-03-07 15:42:41 UTC
(In reply to Alex van Kaam from comment #26)
> hi
> 
> on request of the people over at SUSE I tested my Tumbleweed install with
> the Kernel of the Day.
> 
> first did:  BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default
> root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent
> resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet
> 
> and it booted with a screen
> 
> then did:   BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default
> root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent
> resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet
> amdgpu.dc=1
> 
> and it also booted with a screen
> 
> so on this specifik hardware HP Notebook - 17-ca0710nd, Advanced Micro
> Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] it seems to be
> fixed

Why do you set amdgpu.dc=1? Isn't this the default value anyway?
From what I understood, you tested exactly the same thing.
Comment 29 Dev Bazilio 2019-03-07 16:26:07 UTC
amdgpu.dc=1 set by default for all kernels since 4.17 and it seems that amdgpu.dc=0 is deprecated attribute as new Display core is replacement for old amdgpu code


5.0 version is works same as 4.20 with a lot of warnings and messages in dmesg
https://bugzilla.kernel.org/show_bug.cgi?id=201957
Comment 30 Alex van Kaam 2019-03-07 16:57:59 UTC
> 
> Why do you set amdgpu.dc=1? Isn't this the default value anyway?
> From what I understood, you tested exactly the same thing.

just to be sure, nothing more. I did not know for 100% it was the default now and is the default in the opensuse daily kernel.
Comment 31 Claude Heiland-Allen 2019-04-02 16:38:43 UTC
Created attachment 282101 [details]
dmesg logs after booting to X with displays connected to both DVI and HDMI

Good news: the bug only seems to affect the DVI output from my card.

I managed to connect another screen via an HDMI port and it works ok with amdgpu=1 (both screens have kernel messages mirrored until about 5 seconds into boot, when the DVI screen turns off - the HDMI screen stays on and I can log into X).

Attached are 7 dmesg logs, with amdgpu=1 unless specified.

Note You need to log in before you can comment on or make changes to this bug.