> 1. timeout happens after a resume, if we see below message in dmesg:
> "mwifiex_pci 0000:02:00.0: Refused to change power state, currently in D0"
For me, it says instead:
`mwifiex_pcie 0000:02:00.0: Refused to change power state, currently in D3`
> 2. if device is connected before the 1st suspend, no issue is seen after 1st
> resume;
> 3. if device is connected before 2nd suspend(i.e after 1st suspend_resume),
> then issue is seen after 2nd resume
Yes. However, the "cmd_timeout" will sometimes also occur after 1st resume for
me. Also in this case, the message from mwifiex is the same as No. 1.
> 4. if device is not at all connected during suspend_resume stress test, no
> issue is seen
For me, the "cmd_timeout" will occur regardless of AP connection status/rfkill
status/power_save status.
What changed by No. 4 is that, it will not cause the "lockup" (e.g. not
preventing system shutdown)
Also, I tried the patch 0001-mwifiex-set-PCIE-to-PCI_D0-power-state-on-resume
on comment#105.
- So far, the wifi is still working after several suspend.
- I remember I've done exactly the same thing before and it did not
work before. Hmm…?
- The same message as No. 1 will still be printed on dmesg after
the patch.
- It may still not connect to AP automatically because it fails to find APs
(`nmcli d wifi list` shows empty). This is easily fixed by reloading
"mwifiex_pcie" module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730924
Title:
Wifi does down "crash" in Surface Pro 4
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
