Bug 201183

Summary: AMDGPU Dual displays and only DP screen works after grub.
Product: Drivers Reporter: marten (marten.b)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: NEW ---    
Severity: high CC: harry.wentland, nicholas.kazlauskas
Priority: P1    
Hardware: Intel   
OS: Linux   
Kernel Version: 4.18.* Subsystem:
Regression: No Bisected commit-id:
Attachments: kernel 4.18.7 dmesg
Working kernel 4.17 dmesg
Kernel 4.18 with drm.debug=6
kernel 4.18 drm.debug=4
Kernel 4.18 drm.debug=6

Description marten 2018-09-19 09:17:01 UTC
Created attachment 278653 [details]
kernel 4.18.7 dmesg

Kernel 4.17 is working but the last 2 versions of 4.18.* will not register my HDMI TV connected to an RX 480. 

I have a Dell LCD on DP and an LG TV on HDMI.

If I unplug the DP display after grub screen the computer will have no display.
Comment 1 marten 2018-09-19 09:17:41 UTC
Created attachment 278655 [details]
Working kernel 4.17 dmesg
Comment 2 Michel Dänzer 2018-09-19 09:26:57 UTC
For the time being, maybe amdgpu.dc=0 on the kernel command line can serve as a workaround.
Comment 3 marten 2018-09-19 09:43:33 UTC
Thank you Michel.
That fixes it.
Comment 4 Nicholas Kazlauskas 2018-09-19 12:42:27 UTC
Do you only see this problem occur before you start an X session?

It might help if you could post a log from 4.18 with drm.debug=6 included in your boot parameters.
Comment 5 marten 2018-09-20 05:12:22 UTC
Created attachment 278677 [details]
Kernel 4.18 with drm.debug=6
Comment 6 marten 2018-09-20 05:20:50 UTC
(In reply to Nicholas Kazlauskas from comment #4)
> Do you only see this problem occur before you start an X session?
> 
> It might help if you could post a log from 4.18 with drm.debug=6 included in
> your boot parameters.

Im running Fedora 28 so it wayland. When I remove the quiet from the kernel line the HDMI display works so a few seconds until the GUI for the boot drive encryption displays only on the second display only.

I attached the file with drm.debug=6
Comment 7 Nicholas Kazlauskas 2018-09-20 12:38:09 UTC
It doesn't look like your log buffer was large enough to hold the full log.

A log with drm.debug=4 might have enough information to work off of. The other option is reposting the drm.debug=6 log with a large log buffer size in the kernel config.
Comment 8 marten 2018-09-20 13:26:24 UTC
Hay the machine can do a large buffer. How do I enable that. I saw it cut off at 30 seconds.

Its ryzen 1700, 16G ram and many hd's
Comment 9 Nicholas Kazlauskas 2018-09-20 13:28:22 UTC
It should be the CONFIG_LOG_BUF_SHIFT option. For example, CONFIG_LOG_BUF_SHIFT=21.
Comment 10 marten 2018-09-20 13:33:07 UTC
Created attachment 278683 [details]
kernel 4.18 drm.debug=4
Comment 11 marten 2018-09-20 23:18:32 UTC
Created attachment 278687 [details]
Kernel 4.18 drm.debug=6
Comment 12 marten 2018-09-20 23:19:17 UTC
(In reply to Nicholas Kazlauskas from comment #9)
> It should be the CONFIG_LOG_BUF_SHIFT option. For example,
> CONFIG_LOG_BUF_SHIFT=21.

Updated the file.