Interesting that the d3cold_allowed change made some differences (I'm
assuming it was failing 100% of the times before that change).
Few more questions. After a bad resume:
1) are there unkillable processes (D state) in the system (`ps axuw |
grep D`)?
2) does `sudo iwlist wlp4s0 scan` return any error or does it hang
indefinitely?
3) do you have bluetooth enabled (what's the output of `sudo rfkill
list`)?
As a temporary workaround you can automate the modprobe trick (#3) doing
something like the following:
$ cat /lib/systemd/system-sleep/iwlmvm.sh
#!/bin/sh
case $1 in
pre)
modprobe -r iwlmvm
;;
post)
modprobe iwlmvm
;;
esac
But it'd be nice to find a proper solution to this. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828134
Title:
Wifi not working after suspend/resume cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
