http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c2 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |obs@akr.yagii.de, | |tiwai@suse.com Flags| |needinfo?(obs@akr.yagii.de) --- Comment #2 from Takashi Iwai --- Can you disable Secure Boot on BIOS, and try the latest kernel in OBS Kernel:SLE15-SP4 repo to see whether the problem persists? -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c4 Alexander Krupp changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(obs@akr.yagii.de) |needinfo?(tiwai@suse.com) --- Comment #4 from Alexander Krupp --- The new kernel did not exhibit the described bug, but it also does not suspend properly: Message from syslogd@think14 at Feb 22 14:38:42 ... kernel:[17488.372735][ C5] watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [systemd-sleep:22414] I thought, that this may be caused by a qemu-kvm machine which I did not send to sleep before suspend while being attached to the filesystem via 9p. However, the soft lockup message shows up regardless, after deactivating the vm. Another symptom was a hot device bottom cover, after the lid stayed closed for ~1h, the device cover LED was flashing slowly throughout, which indicates sleep state, usually. Wake-up from suspend by simply opening the lid did not work anymore. Pressing the Fn-Key caused a wake-up. I don't think that this kernel is usable without reliable suspend. Please advise. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c6 --- Comment #6 from Alexander Krupp --- Created attachment 856438 --> http://bugzilla.opensuse.org/attachment.cgi?id=856438&action=edit /var/log/message with BUG: notifications I cannot provide dmesg output, because the last suspend did not wake up and required a hard reset. Please find attached an excerpt of /var/log/messages. I did not expect those to be of use with respect to the original issue. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c8 Alexander Krupp changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #856439|0 |1 is obsolete| | --- Comment #8 from Alexander Krupp --- Created attachment 856442 --> http://bugzilla.opensuse.org/attachment.cgi?id=856442&action=edit dmesg with soft lockup BUG Finally, a reproduction for dmesg. I cannot exactly pinpoint how to reproduce the bug. It seems necessary to close the lid (suspend) for more than 1-2 minutes under battery power. Then, if opening the lid does not wake-up the system, the bug has been triggered. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c10 --- Comment #10 from Alexander Krupp --- MOK asked for enrollment of a your key even with SecureBoot disabled. I enrolled your key. After additionally enrolling a new TPM2 key for the luks swap partition, I am able to run in SecureBoot mode as with the original kernel, when the crashes occurred - if that is not the intended test mode, please notify me. I will report back in a couple of days, or as soon as I experience any buggy behaviour. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c12 --- Comment #12 from Alexander Krupp --- Suspend seems OK after first experiments. The vhba module is missing with the new kernel, which I had in use, usually, during past weeks. Loading /lib/modules/5.14.21-150400.3-default/extra/vhba.ko gives modprobe: ERROR: could not insert 'vhba': Exec format error I suspect, that the module carries at least the wrong signature to be inserted, if not other incompatibilities are in play, here. It is not of primary importance, however, I cannot run everything (e.g. on wine) as before. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1196213 http://bugzilla.opensuse.org/show_bug.cgi?id=1196213#c15 Alexander Krupp changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(obs@akr.yagii.de) | --- Comment #15 from Alexander Krupp --- Created attachment 856738 --> http://bugzilla.opensuse.org/attachment.cgi?id=856738&action=edit messages across crash I could not observe the same crash, again, over the past days. However, sometimes resume from hibernate crashes w/o any recognizable error log messages, only caps-lock and power button are flashing. I did switch the suspend method to "Linux S3" in the BIOS configuration a week ago. The crash may be connected to the suspend-then-hibernate setting. I have attached the log messages present after the last crash a couple of minutes ago. -- You are receiving this mail because: You are the assignee for the bug.