https://bugs.freedesktop.org/show_bug.cgi?id=91291
Bug ID: 91291 Summary: kernel panic and freeze on resume in [radeon] [ttm] Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel@lists.freedesktop.org Reporter: kparal@redhat.com
A few times in a month, my computer fails to resume and just hangs, with black screen, and needs hard reset. This time I got lucky and kernel panic text was shown on my screen, so I took a shot of it. There's a lot of [ttm] and [radeon] strings in it, so it looks like it is related to my Radeon card. The text on the screen has "scrolled" once in a while (it seemed to be rotation), I hope I captured everything important.
Components: Radeon R9 270: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] fully updated Fedora 22: kernel-4.0.7-300.fc22.x86_64 xorg-x11-server-Xorg-1.17.2-1.fc22.x86_64 xorg-x11-drv-ati-7.5.0-3.fc22.x86_64 libdrm-2.4.61-3.fc22.x86_64 mesa-dri-drivers-10.6.1-1.20150629.fc22.x86_64
Please tell me if I can add more useful information somehow. That issue is not easily reproducible, it happens rarely and usually I just see a black screen, so I can't even tell whether it is always the same issue or not.
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #1 from Kamil Páral kparal@redhat.com --- Created attachment 117026 --> https://bugs.freedesktop.org/attachment.cgi?id=117026&action=edit kernel trace - shot1
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #2 from Kamil Páral kparal@redhat.com --- Created attachment 117027 --> https://bugs.freedesktop.org/attachment.cgi?id=117027&action=edit kernel trace - shot2
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #3 from Michel Dänzer michel@daenzer.net --- The traces look like some kind of deadlock in on_each_cpu/smp_call_function_many, not a problem in TTM or the radeon driver. Please report that problem against the kernel.
As for the hang on resume, can you still log into the system via ssh when that happens, or does it at least respond to ping?
https://bugs.freedesktop.org/show_bug.cgi?id=91291
Kamil Páral kparal@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTOURBUG
--- Comment #4 from Kamil Páral kparal@redhat.com --- I can't say for this exact case, but usually the system is dead, doesn't even respond to pings.
I'll report against the kernel, thank you. Would you happen to know against which product and component this should be reported against? https://bugzilla.kernel.org/enter_bug.cgi
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #5 from Michel Dänzer michel@daenzer.net --- (In reply to Kamil Páral from comment #4)
I can't say for this exact case, but usually the system is dead, doesn't even respond to pings.
Note that that sounds like it might be a different problem than the one shown in the attached traces.
I'll report against the kernel, thank you. Would you happen to know against which product and component this should be reported against? https://bugzilla.kernel.org/enter_bug.cgi
Not sure. :( In the worst case, you could try Other / Other. But it might be better to contact the maintainers / maintenance mailing lists of the files containing the on_each_cpu/smp_call_function_many functions directly by e-mail. You can use scripts/get_maintainer.pl to find out what those are.
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #6 from Kamil Páral kparal@redhat.com --- Good to know about that script. Thanks for help.
https://bugs.freedesktop.org/show_bug.cgi?id=91291
--- Comment #7 from Kamil Páral kparal@redhat.com --- For the record, this got reported here: https://bugzilla.kernel.org/show_bug.cgi?id=102321
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org