https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c2 David Walker changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(David@WalkerStree | |t.info) | --- Comment #2 from David Walker --- (In reply to Takashi Iwai from comment #1)

Are you using vmware stuff?

No VMware or any other virtualization. Your comment, though, lends credence to my more recent suspicions that my diagnosis was wrong. What I have noticed over the past few days is that I still have the problem at times. I was busy, so I switched to hibernate, instead of suspend, in /etc/systemd/logind.conf.d: [Login] HandleLidSwitch=hibernate HandleLidSwitchExternalPower=hibernate That resolved the issue, but I'd rather be using suspend. I'm now thinking that the "i8042.reset i8042.nomux=1" that I added to the kernel command line (when the laptop was new and had this problem) no longer has the desired effect. Does that make any sense? Would there be another workaround if so? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c4 --- Comment #4 from David Walker --- (In reply to Takashi Iwai from comment #3)

Can you try to pass i8042.reset=1 i8042.nomux options instead?

I've made this change to the kernel command line and changed the configuration in /etc/systemd/logind.conf.d back to suspend. So far, so good. Unfortunately, the problem has been intermittent, so I'll let you know how it goes over the next 2-3 days. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c6 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(David@WalkerStree | |t.info) --- Comment #6 from Takashi Iwai --- If it's 6.9, the kernel should be still available in TW history repo http://donwload.opensuse.org/history/ and could you verify whether it works stable there? Also, an unofficial build for the last 6.9 is found in OBS home:tiwai:kernel:6.9 repo, too, in case it's gone from TW history repo. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c8 David Walker changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(David@WalkerStree | |t.info) | --- Comment #8 from David Walker --- Well it's been a couple of days (including a few sessions of opening and closing the laptop lid 10-15 times) running 6.8.8-1.1 and, later, 6.8.9-1.1 with no problems resuming from a suspend, so it looks like this started with a 6.9 kernel. I'll keep 6.8.9-1.1 around but upgrade to the latest Tumbleweed snapshot (I'm currently on 20240613) to see if anything recent has resolved this problem. Is there's anything I should do to help debug under the assumption that the problem has not been resolved? I'll at least attach log records. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c10 --- Comment #10 from David Walker --- Even stranger... After upgrading to TW 20240619, wifi doesn't work under any of the 6.9 kernels I now have installed (6.9.1, 6.9.3, 6.9.5). It does, though, still work under 6.8.9. I've attached dmesg output after booting 6.9.5. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c12 --- Comment #12 from Takashi Iwai --- And, since this seems like a regression in 6.9, could you report it to the upstream? You can open the report in bugzilla.kernel.org, and better to report as a regression: https://www.kernel.org/doc/html/latest/admin-guide/reporting-regressions.htm... Feel free to put me (tiwai@suse.de) to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c14 --- Comment #14 from Takashi Iwai --- Yes, it makes sense. The log showed that there were another input devices for touchpad, and the incorrectly working PS2 emulation might have interfered that. Could you give the dmesg output after disabling PS2 emulation on BIOS? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1226065 https://bugzilla.suse.com/show_bug.cgi?id=1226065#c16 --- Comment #16 from David Walker --- Thanks. I've attacked the dmesg after disabling PS2 emulation. -- You are receiving this mail because: You are on the CC list for the bug.