From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled
Date: Wed, 28 Feb 2018 15:26:00 +0000 [thread overview]
Message-ID: <bug-198745-2300-vnEbmOrf67@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198745-2300@https.bugzilla.kernel.org/>
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
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-28 15:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 17:49 [Bug 198745] New: Blank screen on RX 580 with AMDGPU Display Core enabled bugzilla-daemon
2018-02-10 17:50 ` [Bug 198745] " bugzilla-daemon
2018-02-10 17:51 ` bugzilla-daemon
2018-02-10 20:07 ` bugzilla-daemon
2018-02-11 16:57 ` bugzilla-daemon
2018-02-11 18:29 ` bugzilla-daemon
2018-02-11 18:29 ` bugzilla-daemon
2018-02-12 15:47 ` bugzilla-daemon
2018-02-12 16:58 ` bugzilla-daemon
2018-02-12 16:59 ` bugzilla-daemon
2018-02-12 17:03 ` bugzilla-daemon
2018-02-23 13:02 ` bugzilla-daemon
2018-02-23 14:37 ` bugzilla-daemon
2018-02-24 1:23 ` bugzilla-daemon
2018-02-27 20:21 ` bugzilla-daemon
2018-02-28 9:15 ` bugzilla-daemon
2018-02-28 11:03 ` bugzilla-daemon
2018-02-28 15:26 ` bugzilla-daemon [this message]
2018-02-28 16:01 ` bugzilla-daemon
2018-02-28 16:17 ` bugzilla-daemon
2018-02-28 16:40 ` bugzilla-daemon
2018-02-28 16:47 ` bugzilla-daemon
2018-03-21 7:12 ` bugzilla-daemon
2018-07-31 18:04 ` bugzilla-daemon
2018-07-31 18:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-198745-2300-vnEbmOrf67@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).