Comment 6 for bug 1828134

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!