[Bug 106225] Kernel panic after modesetting (not on every boot) on ryzen 5 2400g

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Apr 25 22:36:27 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106225

Francisco Pina Martins <f.pinamartins at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #139081|0                           |1
        is obsolete|                            |

--- Comment #2 from Francisco Pina Martins <f.pinamartins at gmail.com> ---
Created attachment 139114
  --> https://bugs.freedesktop.org/attachment.cgi?id=139114&action=edit
journaltcl log file

Apologies, as this was the wrong logfile (I was getting some journalctl
corruption).
But it seems you are correct and this is not a kernel panic, as I still can
reboot using the "Magic SysRq key" (which I usually can't during kernel
panics), albeit the "Caps Lock" key is unresponsive.

Attached is a log that should show the issue. Note the line:
abr 25 23:23:09 ZenBox systemd-udevd[297]: worker [308] failed while handling
'/devices/pci0000:00/0000:00:08.1/0000:09:00.0'

Where '/devices/pci0000:00/0000:00:08.1/0000:09:00.0' seems to be the "graphics
card".

Symptoms are the same. During some boots, modesetting "seems" to occur, but I
get a black screen instead. System is unresponsive, including "Caps Lock"
lights not changing on key press. Magic SysRq key does seem to successfully
reboot the system.

How should I edit the title to correctly to reflect this?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20180425/fb8ce441/attachment-0001.html>


More information about the dri-devel mailing list