From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209939] New: radeontop causes kernel panic
Date: Thu, 29 Oct 2020 13:22:23 +0000 [thread overview]
Message-ID: <bug-209939-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=209939
Bug ID: 209939
Summary: radeontop causes kernel panic
Product: Drivers
Version: 2.5
Kernel Version: 5.9.1
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: janpieter.sollie@edpnet.be
Regression: No
Created attachment 293297
--> https://bugzilla.kernel.org/attachment.cgi?id=293297&action=edit
kernel .config file of 3 PCs
(view 3 .config files)
> PC1: problem pc, Ryzen 2400GE APU with Vega 11 and 5.9.1 kernel (Xorg
> running)
> PC2: working pc, ryzen V1605 APU with vega 8 and 5.8.14 kernel (Xorg running)
> PC3: working pc, Threadripper 1950 + Fiji GPU and 5.9.1 kernel (CLI only)
As the subject states: on PC1, the kernel can't handle the radeontop program,
one way or another, these methods work / do not on PC1:
> - while hardware-accelerated content is running, panic
> - When in console mode, it's fine
> - when switching from console to X, it's fine for a few moments
> - when trying it early (X running sddm, radeontop via ssh), panic
with *panic*, I mean: the PC does not react anymore: the num lock trigger is no
longer working, no input is accepted, the clock on the GUI does not change
anymore, no SSH.
I tried everything:
> - pstore is empty
> - dd if=/dev/kmsg of=/dev/sdb1 & while [ 1]; do echo s > /proc/sysrq-trigger;
> sleep 10; done & radeontop (and pulling it out of this partition afterwards)
The mainboard does not have a RS232 port, so debugging this way is not
possible;
also, I doubt I'd be able to use KDB if the screen stucks at GUI mode ...
If I can do anything to gather more info, let me know
--
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 reply other threads:[~2020-10-29 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 13:22 bugzilla-daemon [this message]
2020-10-29 13:31 ` [Bug 209939] radeontop causes kernel panic bugzilla-daemon
2020-10-29 20:21 ` bugzilla-daemon
2020-10-29 21:00 ` bugzilla-daemon
2020-10-30 7:53 ` bugzilla-daemon
2020-11-04 7:41 ` bugzilla-daemon
2024-09-23 6:53 ` 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-209939-2300@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