iwlwifi sometimes needs reload on suspend with kernel 4.9 #3008
Comments
|
I can reproduce it on Qubes 4.0, with 4.9.35 in sys-net. |
marmarek
added
T: bug
|
I think I'm having this same problem. I haven't tried blacklisting [user@sys-net ~]$ iwconfig wlp0s1
wlp0s1 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
[user@sys-net ~]$ iwlist wlp0s1 scan
wlp0s1 Failed to read scan data : Network is down
[user@sys-net ~]$ ifconfig wlp0s1
wlp0s1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 0a:16:47:09:50:23 txqueuelen 1000 (Ethernet)
RX packets 473208 bytes 520017957 (495.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 290478 bytes 55321101 (52.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[user@sys-net ~]$ sudo ifconfig wlp0s1 up
SIOCSIFFLAGS: Connection timed out
[user@sys-net ~]$ sudo service network restart
Restarting network (via systemctl): [ OK ]
[user@sys-net ~]$ sudo ifconfig wlp0s1 up
SIOCSIFFLAGS: Connection timed out |
|
On Thu, Aug 17, 2017 at 1:08 PM, Micah Lee ***@***.***> wrote:
I think I'm having this same problem. I haven't tried blacklisting iwlmvm
yet though. Here's what happens after waking up from suspend:
Blacklisting iwlmvm has solved the problem for me.
|
|
I'm also having the same problem but using a debian-9 template for sys-net. |
|
Blacklisting |
|
I still have the same problem even though I blacklisted iwlwifi. |
|
@DrWhax I would double-check this page: https://www.qubes-os.org/doc/wireless-troubleshooting/ My system needed iwldvm blacklisted instead of iwlmvm. It appears to be working well so far. |
|
Thanks adding the driver iwlmvm to /rw/config/suspend-module-blacklist |
|
@DrWhax Also added |
|
@tasket this works for me 1 out of 10 times. It probably is easier if I just buy an Atheros card since it's getting really unworkable. |
|
@DrWhax I had better luck with both modules listed, |
|
This issue is being closed because:
If anyone believes that this issue should be reopened, please let us know in a comment here. |
|
Hello, I have this issue in Qubes 4.0 on a Thinkpad X1 Carbon with iwlwifi. |
|
I am having this issue in Qubes 4.0 on DELL Latitude 7480. Doesn't seem to happen when wifi is disconnected before suspend. Tried running I am running a script from dom0 to automatically restart |
|
For me this was fixed by adding both iwlwifi and iwlmvm to For me this issue can be closed as there is a workaround and it is not a Qubes problem. |
|
@marmarek, do you agree with closing this? |
|
@andrewdavidwong I don’t think this should be closed. If the drivers need to be blocklisted then that should be part of the default configuration. |
|
|
@marmarek good that you asked. Yesterday after adding both Today somehow the wifi device again disappears over suspend. I tested over multiple suspends with and without Then out of interest I tried removing So actually in my case the device being in a blacklists is causing the problem? And the device being being mentioned in two blacklists, maybe undos the blacklisting (like negative+negative=positive? Or something totally different that I am not aware of. |
iwd? does it conflict with NetworkManager? the default suspend script does try to stop/start it, unless you disable it via |
iwd is a replacement for wpa_supplicant, and NetworkManager can call into it. |
|
|
Is this still a problem in 4.1? |
Qubes OS version (e.g.,
R3.2):R3.2, with kernel-4.9.35-19.pvops.qubes
Affected TemplateVMs (e.g.,
fedora-23, if applicable):fedora-25
After today's upgrade to kernel-4.9 from kernel-4.4, I sometimes lose wireless on suspend. I have an Intel AC 7265 chip. I need to unload and reload the module in sys-net to get wireless back. I see the following in dmesg after suspend:
[ 4434.400132] iwlwifi 0000:00:01.0: Failed to load firmware chunk!
[ 4434.400169] iwlwifi 0000:00:01.0: Could not load the [0] uCode section
[ 4434.400211] iwlwifi 0000:00:01.0: Failed to start INIT ucode: -110
[ 4434.400234] iwlwifi 0000:00:01.0: Failed to run INIT ucode: -110
This does not always seem to occur, but I can't isolate why it fails.
The text was updated successfully, but these errors were encountered: