[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume
https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: holgi@suse.com QA Contact: qa-bugs@suse.de CC: tiwai@suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c1 --- Comment #1 from Holger Sickenberg <holgi@suse.com> --- Created attachment 840123 --> https://bugzilla.suse.com/attachment.cgi?id=840123&action=edit NetworkManager log Added NetworkManager log -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c2 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |holgi@suse.com Flags| |needinfo?(holgi@suse.com) --- Comment #2 from Takashi Iwai <tiwai@suse.com> --- Could you give dmesg output, too? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c3 --- Comment #3 from Holger Sickenberg <holgi@suse.com> --- Created attachment 840132 --> https://bugzilla.suse.com/attachment.cgi?id=840132&action=edit dmesg output -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(holgi@suse.com) | -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c4 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #840132|0 |1 is obsolete| | --- Comment #4 from Holger Sickenberg <holgi@suse.com> --- Created attachment 840144 --> https://bugzilla.suse.com/attachment.cgi?id=840144&action=edit dmesg output -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(holgi@suse.com) --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- We see a fatal firmware loading error of iwlwifi at resume: [ 1859.606056] iwlwifi 0000:03:00.0: Error sending REPLY_SCAN_ABORT_CMD: time out after 2000ms. .... And it's an old chip (6205) which firmware hasn't been updated for 8 years log. So it must be a kernel side problem. Could try to boot with TW kernel on this system while keeping the rest, and check whether the similar issue is seen or not? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c6 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(holgi@suse.com) | --- Comment #6 from Holger Sickenberg <holgi@suse.com> --- Unfortunately that's not working for my system. After installing TW kernel, I can no longer boot into my system on encrypted LVM, that's just working with the current 15.2 kernel. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c7 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- (In reply to Holger Sickenberg from comment #6)
Unfortunately that's not working for my system. After installing TW kernel, I can no longer boot into my system on encrypted LVM, that's just working with the current 15.2 kernel.
That's bad. I don't know of such an issue, maybe some problem with initrd. Do you get the emergency shell? In the worst case, you can try some TW Live image. We want to see only whether the suspend/resume works, after all. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c8 --- Comment #8 from Holger Sickenberg <holgi@suse.com> --- Created attachment 840227 --> https://bugzilla.suse.com/attachment.cgi?id=840227&action=edit dmesg output Tumbleweed OK, I installed Tumbleweed alongside and see the same behavior. See dmesg log -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- Thanks! I forgot to ask, though, whether it's a regression. Did it work on Leap 15.1? If yes, could you check installing Leap 15.1 kernel onto Leap 15.2 system and retest? (Only if you still have Leap 15.2 system on your machine; TW installation wouldn't work with Leap 15.1 kernel due to the compressed firmware files.) If it's confirmed to be a kernel regression since Leap 15.1 and TW kernel suffers, we should report it to upstream. Please report it to upstream devs, e.g. bugzilla.kernel.org? Feel free to put me (tiwai@suse.de) in Cc there. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c10 --- Comment #10 from Holger Sickenberg <holgi@suse.com> --- So far my tests on 15.2 with 15.1 kernel are successful - I have not seen any crash. Since I do not have an account on kernel.org, I'd appreciate if you can move that issue there. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c11 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- (In reply to Holger Sickenberg from comment #10)
So far my tests on 15.2 with 15.1 kernel are successful - I have not seen any crash.
OK, at least it's a good news. Leap 15.1 kernel is based on 4.12, but the WiFi stack and iwlwifi driver are almost equivalent with 4.19. There are a few other older kernels available in OBS home:tiwai:kernel:4.19, home:tiwai:kernel:4.20, home:tiwai:kernel:5.0, home:tiwai:kernel:5.1 and home:tiwai:kernel:5.2, corresponding to each kernel version. If you can find out which kernel starts regression, it can be a great help.
Since I do not have an account on kernel.org, I'd appreciate if you can move that issue there.
Then you can report to linux-wireless ML instead, too. This can be even a better path :) But it'd be better to narrow down the regression at first. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c12 --- Comment #12 from Holger Sickenberg <holgi@suse.com> --- Created attachment 840275 --> https://bugzilla.suse.com/attachment.cgi?id=840275&action=edit dmesg output kernel-default-5.0 I did not have any problems with 4.X kernels up to 4.20. But starting with the 5.0 kernel, I see that crashes. dmesg for 5.0 output attached -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- Thanks. Now let's communicate with the upstream devs. I'm going to report to linux-wireless ML. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c15 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(suse@trimoon.clou | |dns.eu) --- Comment #15 from Holger Sickenberg <holgi@suse.com> --- (In reply to Tripple Moon from comment #14)
Not sure if it is related but maybe worth mentioning also, i had a problem with networking after a resume which i solved with a workaround. It was systemd-networkd related: https://github.com/systemd/systemd/issues/14987 Maybe it can be of use in this case also, aside the problem with the driver loading.
Did you - with your problem - see any similar crash in dmesg as in my logs? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c16 --- Comment #16 from Holger Sickenberg <holgi@suse.com> --- Issue still around with current 15.2 kernel (5.3.18-lp152.44-default) -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c17 --- Comment #17 from Takashi Iwai <tiwai@suse.com> --- Unfortunately no reaction to my upstream report. So it's little chance to get it fixed magically without action. And, it's tough to find out the culprit; basically you need to bisect the commits between 4.20 and 5.0. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c18 --- Comment #18 from Takashi Iwai <tiwai@suse.com> --- BTW, do you get the network again if you reload the driver? Try "modprobe -r iwlmvm" and "modprobe iwlwifi" -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c19 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suse@trimoon.clou | |dns.eu) | --- Comment #19 from Holger Sickenberg <holgi@suse.com> --- yes, "modprobe -r iwldvm; modprobe iwlwifi" will make it work again -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c20 --- Comment #20 from Takashi Iwai <tiwai@suse.com> --- You may put some hacks in either systemd or something else for the suspend/resume to perform those module reloads, too. Of course, it's a quite ugly workaround and should be seen as the last resort... -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c21 --- Comment #21 from Takashi Iwai <tiwai@suse.com> --- FWIW, a simple workaround would be to create a script /usr/lib/systemd/system-sleep/iwlwifi-reload.sleep, containing the content like: #!/bin/sh if [ "$1" = "pre" ]; then modprobe -r iwlmvm else modprobe iwlwifi fi exit 0 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c23 --- Comment #23 from Takashi Iwai <tiwai@suse.com> --- There are kernels for each major version in OBS home:tiwai:kernel:* repo, e.g. home:tiwai:kernel:5.4, home:tiwai:kernel:5.5, etc. It'd be helpful if you can try and check which kernel works and which doesn't. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c24 Miroslav Bene�� <mbenes@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes@suse.com --- Comment #24 from Miroslav Bene�� <mbenes@suse.com> --- Holger, has the situation improved since back then (there is also Leap 15.3, 15.2 is not supported anymore)? Or are you satisfied with the workaround Takashi proposed? Michael V, have you tried old kernels Takashi provided? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c25 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 15.2 |Leap 15.3 --- Comment #25 from Holger Sickenberg <holgi@suse.com> --- Unfortunately not, the problem is still the same. I have updated to 15.3 in the meantime and still suffering from the same issue. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c26 --- Comment #26 from Miroslav Bene�� <mbenes@suse.com> --- Ok, that was a long shot. Anyway, if the problem started to appear between 4.20 and 5.0, the easiest would be just to bisect it. Would you be able to do that? If we found the offending commit, it would be easier to fix it (or to force upstream to fix it). Just to be sure, could you also try the latest TW kernel, please? Kernel:stable project in OBS (you might need Kernel:stable:Backport due to some recent incompatible changes. I am not sure.). -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c27 --- Comment #27 from Holger Sickenberg <holgi@suse.com> --- My impression is that this is no longer an issue starting with openSUSE 15.4. I'm not 100% sure, but hopeful. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1174622 https://bugzilla.suse.com/show_bug.cgi?id=1174622#c28 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #28 from Takashi Iwai <tiwai@suse.com> --- OK, then let's close for now. Feel free to reopen if the problem reappears again. Thanks. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com