[Bug 1197558] New: kernel 5.17 not recovering from sleep or hibernation
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 Bug ID: 1197558 Summary: kernel 5.17 not recovering from sleep or hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: graeme.w.murray@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Latest Kernel 5.17.0-4.gcae6180-default not recovering from sleep or hibernation correctly. Sleep - machine restarts but no display and no usb, so impossible to gain access to machine. Hibernation- machine restarts same results but then reboots. On kernel 5.16 all working fine on this hardware. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c2 --- Comment #2 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857540 --> http://bugzilla.opensuse.org/attachment.cgi?id=857540&action=edit hwinfo for 5.17 sorry for delay, info as requested -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c3 --- Comment #3 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857541 --> http://bugzilla.opensuse.org/attachment.cgi?id=857541&action=edit 5.16 hwinfo -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c4 --- Comment #4 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857542 --> http://bugzilla.opensuse.org/attachment.cgi?id=857542&action=edit journal log for 5.17 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c5 --- Comment #5 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857543 --> http://bugzilla.opensuse.org/attachment.cgi?id=857543&action=edit journal log for 5.16 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c6 Graeme Murray <graeme.w.murray@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(graeme.w.murray@g | |mail.com) | --- Comment #6 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857545 --> http://bugzilla.opensuse.org/attachment.cgi?id=857545&action=edit no_console_suspend -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c7 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- There was a warning in 5.16 kernel, but it's probably a different issue and it should have been already fixed, as it's gone with 5.17. Unfortunately there is no log at all indicating any crash, so currently we have no clue what broke. Does the machine succeed to suspend or hibernate, but fail to resume, right? Then maybe hibernate might give better chance to catch the crash. Try no_console_suspend and hibernate. Also, don't forget to test with the latest kernel in OBS Kernel:stable repo. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c8 --- Comment #8 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857577 --> http://bugzilla.opensuse.org/attachment.cgi?id=857577&action=edit journal log for 5.17.1-2 Sorry, misreported, hibernate is working on 5.17 on my machine. It is only sleep which is not working. I have tried 5.17.1-2 and attached the journal log. Same issue with sleep. As before, looks like machine enters sleep correctly, power led blinks, as normal. After moving the mouse, power led does go solid but nothing else happens so only option is to reboot. I have had a look at the kernel configs for both 5.16 and 5.17 can't see anything which makes a difference. More than happy to try anything which might help. Thanks, -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c9 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(graeme.w.murray@g | |mail.com) --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- OK, that's interesting. Could you try the kernel-vanilla in OBS home:tiwai:kernel:drm-tip repo? http://download.opensuse.org/repositories/home:/tiwai:/kernel:/drm-tip/stand... And, do you still have control after the resume, even magic-sysrq? i.e. Does the machine react to alt-sysrq-S for sync, alt-sysrq-B for reboot after the hang at resume? Or is it a hard freeze that doesn't react to it? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c10 Graeme Murray <graeme.w.murray@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(graeme.w.murray@g | |mail.com) | --- Comment #10 from Graeme Murray <graeme.w.murray@gmail.com> --- OK, tried kernel-vanilla from your repo, same result. Power led goes solid and fan starts, no display, it stays on standby. my keyboard (logi mx keys) does not have sysrq, (that I can find) so can't test sysrq +S or +B. I will go on a hunt for another keyboard and let you know if I can find one. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- The sysrq key is often mapped to a different one, e.g. PrtScr or some equivalent key in other keyboards. See each language page of Wikipedia: https://en.wikipedia.org/wiki/Magic_SysRq_key -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c12 --- Comment #12 from Takashi Iwai <tiwai@suse.com> --- And, let's check with nomodeset boot option. This will boot without the native graphics (amdgpu), driving with EFI framebuffer. It might be that it won't reach to the graphics environment, but it's fine with Linux console. There you can run manually like "systemctl suspend". At resume, you'll likely lose the graphics screen, but the system should still live. You can type blindly or reach via network there. e.g. run a command (e.g. "systemctl suspend" again) and see whether it works as expected. If the suspend/resume works without graphics, it's narrowed to be a problem of amdgpu. If it still hangs up, it's something else. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c13 --- Comment #13 from Graeme Murray <graeme.w.murray@gmail.com> --- Thanks, I have been looking at the wiki page, the keyboard has a print screen ( at least it starts spectacle) nothing else seems to work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c14 --- Comment #14 from Graeme Murray <graeme.w.murray@gmail.com> --- Ok same again, boot with nomodeset, got graphics desktop just a little big. Same result after sleep. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c15 --- Comment #15 from Takashi Iwai <tiwai@suse.com> --- So, no reaction *at all* with the keyboard or access from the outside? You can try caps-lock change and see LED or whatever, just to see whether the system lives. The point here is only to know whether it's a hard crash other than graphics or it's just a graphics disabled after resume. In the latter case, that's expected. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c16 --- Comment #16 from Graeme Murray <graeme.w.murray@gmail.com> --- OK, managed to get Alt+prtscr+b working when not in sleep, so believe key seq is working. Tried it again when machine sleeping, no change, tried caps-lock, no led, then tried Alt+prtscr+o again no change. so looks like machine is not responding, (it's dead Jim). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c17 --- Comment #17 from Graeme Murray <graeme.w.murray@gmail.com> --- Not sure if this helps but on kernel 5.17.1-3 default, machine sleeping, after a key stroke, wait 1 min 30 about, machine reboots. I did try this on kernel 5.17.1-3 vanilla and nothing happens after 5 mins. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c18 --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- Hm, it might be some watchdog, but it doesn't explain why it happens with the newer kernel... Maybe we should try kdump for capturing the crash. Could you try to set up kdump (e.g. via YaST)? You likely need to give a higher RAM size than suggested there. After setting it up and reboot, try manually "alt-sysrq-c" combo. This will trigger a crash and it should result in a crash dump under /var/crash/*. If dmesg file is found there, it's good. Then we can try suspend/resume, and check whether we get either a dmesg file or a vmcore there. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c19 --- Comment #19 from Graeme Murray <graeme.w.murray@gmail.com> --- kdump set up and working. Tried suspend/resume and got both dmesg and vmcore. Should I attach both or just dmesg? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c20 --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- vmcore is too large to attach, please upload only dmesg. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c21 --- Comment #21 from Graeme Murray <graeme.w.murray@gmail.com> --- cannot post -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c22 --- Comment #22 from Graeme Murray <graeme.w.murray@gmail.com> --- trying to upload dmesg.txt but get "server internal error....., please contact opensuse support" ? is there someone I can report this too? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c23 --- Comment #23 from Takashi Iwai <tiwai@suse.com> --- Must be an intermittent error. If you still can't upload, just send via e-mail to me :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c24 --- Comment #24 from Graeme Murray <graeme.w.murray@gmail.com> --- Thanks, email on it's way -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c25 --- Comment #25 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857639 --> http://bugzilla.opensuse.org/attachment.cgi?id=857639&action=edit crash dmesg.txt my fault couldn't upload, wrong permissions on file, doh. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c26 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(graeme.w.murray@g | |mail.com) --- Comment #26 from Takashi Iwai <tiwai@suse.com> --- Thanks. The critical hit was: [ 251.498921] Enabling non-boot CPUs ... [ 251.498921] ------------[ cut here ]------------ [ 251.498921] kernel BUG at kernel/time/timer.c:1965! And it's the code: int timers_dead_cpu(unsigned int cpu) { struct timer_base *old_base; struct timer_base *new_base; int b, i; ==> BUG_ON(cpu_online(cpu)); It means that the given CPU is already online while it shouldn't be. But it's not clear why the teardown is called at this stage. Maybe another step failed and rolling back caused the problem. I'm building a test kernel with a debug patch in OBS home:tiwai:bsc1197558 repo. Once after the build finishes (takes an hour or so), it'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1197558/standard/ This replaced BUG_ON() with WARN_ON_ONCE(), so it shouldn't stop at the point. Please test with it and give the dmesg output after suspend/resume. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c27 --- Comment #27 from Graeme Murray <graeme.w.murray@gmail.com> --- OK, will do -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c28 --- Comment #28 from Takashi Iwai <tiwai@suse.com> --- BTW, another kernel WARNING before the BUG line is likely a different problem, but maybe a spurious issue. It seems hitting on many others, too: https://bugzilla.redhat.com/show_bug.cgi?id=2048838 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c29 --- Comment #29 from Graeme Murray <graeme.w.murray@gmail.com> --- OK, thanks. This would affect VMs I guess? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c30 --- Comment #30 from Takashi Iwai <tiwai@suse.com> --- (In reply to Graeme Murray from comment #29)
OK, thanks. This would affect VMs I guess?
Not sure, I guess it's a spurious issue that happens only at resume, but we need to check once when we get a working resume. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c31 --- Comment #31 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857678 --> http://bugzilla.opensuse.org/attachment.cgi?id=857678&action=edit crash dmesg.txt from test 5.17.1-1.g26e13dc-default -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c32 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov@suse.com --- Comment #32 from Takashi Iwai <tiwai@suse.com> --- Thanks. Hrm, it hits a failure at a different point now. The best we can do at this moment is to perform git-bisect, I guess. Can you try it in your side? Meanwhile, let's add Boris to Cc, as it might be his area. Boris, it's a regression between 5.16 and 5.17. Judging from two crash logs, thaw_secondary_cpus() at resume hits weird bugs, eventually leading to a BUG_ON() somewhere. It seems happening only with suspend-to-RAM, not with hibernation. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c33 --- Comment #33 from Graeme Murray <graeme.w.murray@gmail.com> --- OK, what can I do to help? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c34 --- Comment #34 from Borislav Petkov <bpetkov@suse.com> --- That thing has a proprietary module in there: ... loaded Tainted: P OE 5.17.1-3.g58205bc-default... ... wl(POE) amdgpu r8168(OE)... [ 2.052104] wl: module license 'MIXED/Proprietary' taints kernel. [ 2.052108] Disabling lock debugging due to kernel taint And that thing warns first in the AMD iommu code and the warning adding commit a8d4a37d1bb9 ("iommu/amd: Restore GA log/tail pointer on host resume") talks about some guest vapic log getting a chance to resume. The timer BUG_ON() points to a CPU not coming online, presumably CPU1 or so. So, can you reproduce the same thing with that wl module completely removed from your system? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c35 --- Comment #35 from Takashi Iwai <tiwai@suse.com> --- Also r8168 driver is a downstream one, this should be disabled while testing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c36 --- Comment #36 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857705 --> http://bugzilla.opensuse.org/attachment.cgi?id=857705&action=edit crash dmesg.txt, r8168 removed ok, removed r8168, same test as before. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c37 --- Comment #37 from Borislav Petkov <bpetkov@suse.com> --- Your proprietary module is still loaded. You need to remove it completely from the system so that it doesn't load automatically. [ 1.946359] wl: loading out-of-tree module taints kernel. [ 1.946366] wl: module license 'MIXED/Proprietary' taints kernel. [ 1.946368] Disabling lock debugging due to kernel taint [ 1.948274] wl: module verification failed: signature and/or required key missing - tainting kernel -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c38 --- Comment #38 from Graeme Murray <graeme.w.murray@gmail.com> --- Sorry but I have no idea what the wl module is? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c39 --- Comment #39 from Graeme Murray <graeme.w.murray@gmail.com> --- I can see it in lsmod so will try and remove -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c40 --- Comment #40 from Graeme Murray <graeme.w.murray@gmail.com> --- ok, so it's the broadcom wireless lan driver. Can i modprobe -r it or should I deinstall completely? I guess I will not have a network connection after. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c41 --- Comment #41 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857709 --> http://bugzilla.opensuse.org/attachment.cgi?id=857709&action=edit crash dmesg.txt wl removed OK, i think i removed wl completely. Can't see it in lsmod or dmesg and have removed package broadcom-wl-kmp-default. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c42 --- Comment #42 from Borislav Petkov <bpetkov@suse.com> --- Ok, it still explodes even with the broadcom driver removed. Now, add "amd_iommu=off" to the kernel command line in /boot/grub/grub.cfg - this will be there temporarily until the next time you install a kernel but it should be enough to test - and do the exact same thing. Thx. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c43 --- Comment #43 from Graeme Murray <graeme.w.murray@gmail.com> --- Created attachment 857710 --> http://bugzilla.opensuse.org/attachment.cgi?id=857710&action=edit crash dmesg.txt amd_iommu=off hopefully this gives us a bit more. thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c44 Borislav Petkov <bpetkov@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jroedel@suse.com Flags| |needinfo?(jroedel@suse.com) --- Comment #44 from Borislav Petkov <bpetkov@suse.com> --- Thanks, apparently, one can't simply disable the iommu. Ok, back to the previous situation. Joerg, pls have a look at comment #41, there's: WARNING: CPU: 0 PID: 3514 at drivers/iommu/amd/init.c:851 amd_iommu_enable_interrupts+0x336/0x410 Something about interrupt remapping and something GA_LOG timeoutting. Also, Graeme, I see you have BIOS from almost two years ago: BIOS AF5NV701.25 12/15/2020 You could try updating it to see whether the IOMMU issue is fixed. Might be related to the resume failure... Thx. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c45 --- Comment #45 from Takashi Iwai <tiwai@suse.com> --- Note that the iommu problem is a fairly oft-seen problem, see the commit 28. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c46 --- Comment #46 from Takashi Iwai <tiwai@suse.com> --- (In reply to Takashi Iwai from comment #45)
Note that the iommu problem is a fairly oft-seen problem, see the commit 28.
I meant comment 28. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c47 --- Comment #47 from Graeme Murray <graeme.w.murray@gmail.com> --- I have updated the BIOS to the latest one dated 07/27/2021, (scary process as had to boot in windows). Anyway, looks like suspend/resume is working fine. I have removed the boot option of amd_iommu=off and suspend/resume still works. I do have the journal log around the time of resume/suspend if needed. Next for me is to re-install the wifi driver and see if wl is a dependency and check that all is working. Thanks to everyone for the help given, brilliant. Will update later. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c48 --- Comment #48 from Borislav Petkov <bpetkov@suse.com> --- Ah, interesting. So it looks like with the kernel getting new features constantly and using them, the BIOS needs to "catch up", so to speak. Unfortunately, one can't know what got changed to fix your problem. Oh well... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197558 http://bugzilla.opensuse.org/show_bug.cgi?id=1197558#c49 Graeme Murray <graeme.w.murray@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #49 from Graeme Murray <graeme.w.murray@gmail.com> --- I guess we will never know for sure, the closest we can say is the change between 5.16.16-- to 5.17.rc8 caused my machine to start having the problem. Thanks again, will set status of bug to resolved. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com