http://bugzilla.opensuse.org/show_bug.cgi?id=1140320 http://bugzilla.opensuse.org/show_bug.cgi?id=1140320#c1 --- Comment #1 from Patrick Finie --- Created attachment 809375 --> http://bugzilla.opensuse.org/attachment.cgi?id=809375&action=edit Full log with everything prior to the kernel panic. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1140320 http://bugzilla.opensuse.org/show_bug.cgi?id=1140320#c6 --- Comment #6 from Patrick Finie --- (In reply to Takashi Iwai from comment #5)

Hrm, so it's hard to judge.

Patrick, could you test more recent kernels? At least the latest 5.1.x one in Kernel:stable repo, and 5.2-rc in Kernel:HEAD repo.

If you want to check whether 5.0.x was already broken, a kernel package is available in OBS home:tiwai:kernel:5.0 repo, too.

I did some more testing. There was a USB 3 card that was not functioning in the sense that no data would go through it. So on the discord support channel soomeone mentioned to remove that and see if things work. Well it got as far as Loading X to the desktop and now it is hardlocked with no control not even the enabled sysrq keys. Not sure how to debug this further as it seems to have booted fine. I cannot drop into a TTY, i cannot SSH in, the machine is absolutely unresponsive once it locks up. This time there is no trace. Let me know and i will boot into the older kernel and get the full unadulterated log for you. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1140320 http://bugzilla.opensuse.org/show_bug.cgi?id=1140320#c8 --- Comment #8 from Patrick Finie --- The latest 5.2 in the kernel stable repo has the same issue. kernel-default-5.2.0-1.1.g580cec3.x86_64.rpm I am able to log in via run level 3 but shortly after the system locks up. Journalctl isnt showing much as the last thing before the current lock was DKMS. SOMETIME LATER: Well i logged back into 4.20 and through i would make a log to compair 4.20 with 5.2.0. The command used was journalctl -b -1 | tee bootlog5.2.0.log for kernel 5.2.0 and journalctl -b -0 | tee bootlog4.20.log. from the 5.2 log it crashed shortly after logging into the tty. i had journalctl running and htop and noticed htop froze which alerted me that the system might be hardlocked. No key input would get it out of this and no safe means of bringing the system down other than holding the power button for 20S was able to resolve it. If i had any hair on my head it would be pulled out. Any hints and suggestions on how to debug this would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1140320 http://bugzilla.opensuse.org/show_bug.cgi?id=1140320#c10 --- Comment #10 from Patrick Finie --- Created attachment 809756 --> http://bugzilla.opensuse.org/attachment.cgi?id=809756&action=edit Succesful boot to 5.2.0 and log in then hardlock command used once in kernel 4.20: journalctl -b -1 | tee bootlog5.2.0.log This boot i was successful in logging in via TTY as root and had Jornalctl -b -1 to diagnose the previous crash and htop running before it locked. -- You are receiving this mail because: You are on the CC list for the bug.