From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204227] Visual artefacts and crash from suspend on amdgpu
Date: Thu, 19 Sep 2019 21:09:01 +0000 [thread overview]
Message-ID: <bug-204227-2300-hw6E5C6yjC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204227-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204227
--- Comment #13 from Mirek Kratochvil (exa.exa@gmail.com) ---
After the BIOS upgrade the kernel parameters can be removed, but the kernel
(5.2.16) now locks up when entering XFCE (it survives lightdm though). The
error is almost same as as in the posted dmesg; I'll attach mine with
backtraces in a few seconds.
Highlights:
This gets printed out before each warning:
[ 66.159175] [drm] pstate TEST_DEBUG_DATA: 0x36F60000
R08 gets increased by some value between 49 and 56 after each next warning (the
value is sometimes in R10)
Userspace seems working otherwise (the logs are from syslog), just the display
won't show anything.
I will try a few other kernels available for debian and eventually bisect.
--
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:[~2019-09-19 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 22:49 [Bug 204227] New: Visual artefacts and crash from suspend on amdgpu bugzilla-daemon
2019-07-18 22:50 ` [Bug 204227] " bugzilla-daemon
2019-07-19 19:16 ` bugzilla-daemon
2019-07-20 15:27 ` bugzilla-daemon
2019-08-26 23:42 ` bugzilla-daemon
2019-08-27 13:12 ` bugzilla-daemon
2019-08-27 18:07 ` bugzilla-daemon
2019-08-27 18:31 ` bugzilla-daemon
2019-08-28 0:47 ` bugzilla-daemon
2019-08-28 1:48 ` bugzilla-daemon
2019-09-09 8:29 ` bugzilla-daemon
2019-09-09 11:07 ` bugzilla-daemon
2019-09-09 11:14 ` bugzilla-daemon
2019-09-19 21:09 ` bugzilla-daemon [this message]
2019-09-19 21:11 ` bugzilla-daemon
2019-09-23 7:36 ` 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-204227-2300-hw6E5C6yjC@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).