From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211649] "drm/amd/display: reuse current context instead of recreating one" cause hdmi hotplug blackscreen on amdgpu
Date: Wed, 10 Feb 2021 18:29:09 +0000 [thread overview]
Message-ID: <bug-211649-2300-NO3zG4mwXj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211649-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211649
--- Comment #7 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
That makes more sense then, that's the behavior I'd expect on CrOS/Android.
Also explains why we haven't seen this on X/Wayland based compositors like
GNOME on Ubuntu.
One more log I'd like captured here, the trace log. Please record a log from
before the black screen occurs until after.
I've included a snippet below that shows how to capture this log:
#!/bin/bash
set +x
OUTPUT_DIR=$(pwd)
mount -o remount,rw /
echo 4 > /sys/module/drm/parameters/debug
echo 65536 > /sys/kernel/debug/tracing/buffer_size_kb
cd /sys/kernel/debug/tracing/
echo amdgpu_dm* > set_ftrace_filter
echo function > current_tracer
echo 1 > events/amdgpu_dm/enable
echo 1 > tracing_on
echo > trace
echo "Capturing a trace...\n"
read -n 1
cat trace > $OUTPUT_DIR/trace.txt
echo "Saved trace to ${OUTPUT_DIR}/trace.txt"
dmesg > $OUTPUT_DIR/dmesg.txt
echo "Saved dmesg to ${OUTPUT_DIR}/dmesg.txt"
--
You may reply to this email to add a comment.
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:[~2021-02-10 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 6:51 [Bug 211649] New: "drm/amd/display: reuse current context instead of recreating one" cause hdmi hotplug blackscreen on amdgpu bugzilla-daemon
2021-02-10 14:35 ` [Bug 211649] " bugzilla-daemon
2021-02-10 14:42 ` bugzilla-daemon
2021-02-10 16:14 ` bugzilla-daemon
2021-02-10 16:41 ` bugzilla-daemon
2021-02-10 16:57 ` bugzilla-daemon
2021-02-10 17:28 ` bugzilla-daemon
2021-02-10 18:29 ` bugzilla-daemon [this message]
2021-02-10 19:35 ` bugzilla-daemon
2021-02-10 19:46 ` bugzilla-daemon
2021-02-10 19:51 ` bugzilla-daemon
2021-02-10 19:55 ` bugzilla-daemon
2021-02-10 19:56 ` bugzilla-daemon
2021-02-15 15:22 ` bugzilla-daemon
2021-02-18 14:35 ` bugzilla-daemon
2021-02-25 20:40 ` bugzilla-daemon
2021-03-04 12:54 ` bugzilla-daemon
2021-03-04 14:01 ` bugzilla-daemon
2021-03-04 14:16 ` bugzilla-daemon
2021-03-04 17:40 ` 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-211649-2300-NO3zG4mwXj@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