[Bug 1203713] New: kernel 5.14.21-150400.24.21-default leads to sporadic cpu stucks
http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 Bug ID: 1203713 Summary: kernel 5.14.21-150400.24.21-default leads to sporadic cpu stucks Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: ralf.koelmel@kit.edu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 861709 --> http://bugzilla.opensuse.org/attachment.cgi?id=861709&action=edit example of the console traces since update from kernel 5.14.21-150400.24.18-default to 5.14.21-150400.24.21-default i'm observing on different systems (Dualprocessorsystem with AMD Opteron(tm) Processor 6172,Dualprocessorsystem AMD EPYC 7742 64-Core Processor, VMs) sporadic kernel stucks during runtime. On the console there are traces in the manner [155369.287478][ C30] watchdog: BUG: soft lockup - CPU#30 stuck for 24614s! [kworker/u134:0:49915] Login on console is possible, but a command can't be executed without blocking. The network is dead. No critical messages before or at the date when this state is occuring. No message is written into system log after reaching this state. The systems are mainly compute systems, but according to monitoring they were in idle mode. For now i've reverted all systems to the previous kernel which doesn't show this problem. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 Ralf K�lmel <ralf.koelmel@kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 http://bugzilla.opensuse.org/show_bug.cgi?id=1203713#c1 --- Comment #1 from Ralf K�lmel <ralf.koelmel@kit.edu> --- it seems that already another bugreport is addressing a similiar problem with this new kernel: https://bugzilla.opensuse.org/show_bug.cgi?id=1203539 My problems are occuring after booting and the systems were running several hours before the problem is occuring. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 http://bugzilla.opensuse.org/show_bug.cgi?id=1203713#c2 --- Comment #2 from Ralf K�lmel <ralf.koelmel@kit.edu> --- I've one system which i can use for detailed analysis (if possible) and which is still in this blocked state. If there is something which i can do in this state for deeper analysis of this problem, please let me know. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203713 http://bugzilla.opensuse.org/show_bug.cgi?id=1203713#c3 --- Comment #3 from Ralf K�lmel <ralf.koelmel@kit.edu> --- Created attachment 861717 --> http://bugzilla.opensuse.org/attachment.cgi?id=861717&action=edit extract of the begin of the stacktraces of one affected system -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com