https://bugzilla.kernel.org/show_bug.cgi?id=198745
Bug ID: 198745 Summary: Blank screen on RX 580 with AMDGPU Display Core enabled Product: Drivers Version: 2.5 Kernel Version: 4.15.2 Hardware: Other OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: kyle.devir@mykolab.com Regression: No
Created attachment 274089 --> https://bugzilla.kernel.org/attachment.cgi?id=274089&action=edit journalctl output for amdgpu
When enabling AMDGPU Display Core for my Gigabyte RX 580, I get nothing more than a blank screen on my HDMI monitor.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #1 from Kyle De'Vir (kyle.devir@mykolab.com) --- Created attachment 274091 --> https://bugzilla.kernel.org/attachment.cgi?id=274091&action=edit journalctl output for drm
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Kyle De'Vir (kyle.devir@mykolab.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.devir@mykolab.com
--- Comment #2 from Kyle De'Vir (kyle.devir@mykolab.com) --- Comment on attachment 274091 --> https://bugzilla.kernel.org/attachment.cgi?id=274091 journalctl output for drm
Feb 10 17:33:47 valmar-desktop kernel: [drm] Cannot find any crtc or sizes
This is the only error from the log.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #3 from Kyle De'Vir (kyle.devir@mykolab.com) --- Is there anything I can do to get any interest debug output?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com
--- Comment #4 from Alex Deucher (alexdeucher@gmail.com) --- Please attach your full dmesg output and xorg log if you are using X.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #5 from Kyle De'Vir (kyle.devir@mykolab.com) --- Created attachment 274115 --> https://bugzilla.kernel.org/attachment.cgi?id=274115&action=edit dmesg log
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #6 from Kyle De'Vir (kyle.devir@mykolab.com) --- Created attachment 274117 --> https://bugzilla.kernel.org/attachment.cgi?id=274117&action=edit xorg log
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Harry Wentland (harry.wentland@amd.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |harry.wentland@amd.com
--- Comment #7 from Harry Wentland (harry.wentland@amd.com) --- Please capture dmesg again with amdgpu.dc_log=1 and drm.debug=6 kernel options.
What monitor are you using? Is it connected via a dongle?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #8 from Kyle De'Vir (kyle.devir@mykolab.com) --- Created attachment 274131 --> https://bugzilla.kernel.org/attachment.cgi?id=274131&action=edit dmesg log with amdgpu.dc_log=1 and drm.debug=6
My monitor is an AOC I2379VHE. It's attached via a HDMI cable.
What do you mean by dongle? Wifi?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #9 from Alex Deucher (alexdeucher@gmail.com) --- (In reply to Kyle De'Vir from comment #8)
What do you mean by dongle? Wifi?
A display dongle (e.g., DP to HDMI adapter).
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #10 from Kyle De'Vir (kyle.devir@mykolab.com) --- Ah. None ~ just your average HDMI to HDMI cable.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #11 from Kyle De'Vir (kyle.devir@mykolab.com) --- Any progress on this issue? Are there any other logs or debugging output that I might be able to supply to help with this issue? If so, how do I acquire them?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #12 from Harry Wentland (harry.wentland@amd.com) --- It looks like we detect no display. We haven't yet had a chance to repro the problem. I'll see if I can find this display in the office.
It'd be difficult debugging this remotely but if I can't repro this I might send you some extra logging patches in the hopes of getting more info.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #13 from Kyle De'Vir (kyle.devir@mykolab.com) --- Is there something that plain AMDGPU is doing that Display Core isn't, perhaps? Is there a way to find what the difference could be?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #14 from Harry Wentland (harry.wentland@amd.com) --- Created attachment 274477 --> https://bugzilla.kernel.org/attachment.cgi?id=274477&action=edit [PATCH] drm/amd/display: Disable HPD filter for HDMI
This is a bit of a shot in the dark but I'm curious if HPD filtering causes us to lose the HPD signal for some reason.
Do you have a chance to try this patch and see if it fixes the issue?
Note: This patch is really only for debug purposes and might lead to other instability with display detection.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #15 from Kyle De'Vir (kyle.devir@mykolab.com) --- Am trying it out soon. Will try and capture dmesg log if it matters.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #16 from Kyle De'Vir (kyle.devir@mykolab.com) --- No change... dmesg looks no different. :/
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #17 from Harry Wentland (harry.wentland@amd.com) --- Thanks for checking. Non-DC display driver and DC do detection somewhat differently. It's somewhat difficult to say what's going wrong there.
Do you see different behavior when booting headless, then plugging in the display?
If you're interested in debugging I'd probably use ftrace to get started, checking that the functions get hit: - handle_hpd_irq (only on hotplug) - dc_link_detect (crucial to detection) - dc_sink_create - dm_helpers_read_local_edid - drm_get_edid - dm_helpers_parse_edid_caps - amdgpu_dm_update_connector_after_detect - drm_mode_connector_update_edid_property
Script to do ftrace debugging (run as root):
#!/bin/bash cd /sys/kernel/debug/tracing/
echo handle_hpd_irq >> set_ftrace_filter echo dc_link_detect >> set_ftrace_filter echo dc_sink_create >> set_ftrace_filter echo dm_helpers_read_local_edid >> set_ftrace_filter echo drm_get_edid >> set_ftrace_filter echo dm_helpers_parse_edid_caps >> set_ftrace_filter echo amdgpu_dm_update_connector_after_detect >> set_ftrace_filter echo drm_mode_connector_update_edid_property >> set_ftrace_filter
echo function_graph >> current_tracer echo '' >> trace cat trace_pipe
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #18 from Kyle De'Vir (kyle.devir@mykolab.com) --- Actually, there was a change! Didn't have to boot headless at all, happily.
Your patch didn't seem to change anything, but the update to 4.15.6 might have done something...? Did anything change for Display Core in the latest stable update?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #19 from Harry Wentland (harry.wentland@amd.com) --- I don't see any DC or other DRM change in the stable kernel between 4.15.5 and 4.15.6.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #20 from Kyle De'Vir (kyle.devir@mykolab.com) --- I'm going to test without your patch to see if the problem pops up again.
https://bugzilla.kernel.org/show_bug.cgi?id=198745
--- Comment #21 from Kyle De'Vir (kyle.devir@mykolab.com) ---
I don't see any DC or other DRM change in the stable kernel between 4.15.5 and 4.15.6.
What about any of the other point releases? I tried without your patch, and amdgpu.dc=1 mysteriously just works... so strange that it just didn't before.
I don't understand what even happened, and that's even more frustrating than it not working... urgh. :/
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Kyle De'Vir (kyle.devir@mykolab.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UNREPRODUCIBLE
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Claude Heiland-Allen (claude@mathr.co.uk) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |claude@mathr.co.uk
--- Comment #22 from Claude Heiland-Allen (claude@mathr.co.uk) --- I think I have this exact same issue with my RX 580. 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'm building a 4.18~rc7 from kernel.org now to rule out Debian patches being the issue and will be able to provide logs.
Should I open a new issue as this one has been closed? Or can this one be reopened?
https://bugzilla.kernel.org/show_bug.cgi?id=198745
Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nicholas.kazlauskas@amd.com
--- Comment #23 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) --- (In reply to Claude Heiland-Allen from comment #22)
Feel free to create a new ticket and include your dmesg and Xorg logs.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org