https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c12 Fritz Hudnut <non.space.1@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(non.space.1@gmail | |.com) | --- Comment #12 from Fritz Hudnut <non.space.1@gmail.com> --- (In reply to Takashi Iwai from comment #10)

(In reply to Fritz Hudnut from comment #9)

...

(In reply to Takashi Iwai from comment #7)

...

Could you give hwinfo output, and the dmesg output before the suspend? Also, check journal outputs if it got some kernel Oops or crash.

Last but not least, please check with the kernel from OBS Kernel:stable:Backport repo (only kernel-default.rpm) for the latest 6.1.x kernel, and verify whether the problem persists with it or not.

@Takashi

Had a few spare moments to try to find this "OBS Kernel" data, but it seemed to lead to a list of links, none of which said "6.1" . . . so I would need a direct link to whatever site you are suggesting that I check into to get a newer kernel going in Leap 15.5 . . . !!???

It's available at

http://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/

@Takashi: Alrighty, got the 6.1.12 xxx kernel installed and used SuperGrub2 to boot that selection, and that does seem to have revived from suspend several times and the GUI is working (as I'm typing this) . . . so that would be the preferred condition . . . . After I booted the new kernel Package Updater showed "84 packages+-" to update and when I ran the zypper dup -l it showed "2 problems" relating to, "do I want to move the 5.14 kernels from OBS to openSUSE??" Couldn't make the decision right at that moment, like, I don't need that kernel because it didn't fix the problem, so it isn't too critical . . . but, then it might be one of the back ups??? Anyway, I'll monitor the operation of Leap 15.5 for a bit, but it does seem like the 6.1.12 Backports kernel addresses the problem. Thanks kindly for the help on it. -- You are receiving this mail because: You are on the CC list for the bug.