Ok, I retried with latest updates, and the behaviour has changed. I freshly booted, and then did the 4 command as described, and attached above. Then I tried to suspend 3 times, every time it took *very* long to go to sleep, more than one minute. Eventually it flashes some text on the screen about CIFS, and then goes to sleep. Before it would flash said text, and then come back up in X. In the dmesg I could find the text, it is:
This message is repeated every time I try to suspend the machine. Laptop was running on battery power, and no CIFS shares are mounted. The SMB daemon is running however, but I have not defined any shares.
After the second suspend, the machine would power on again, and go into X, and the password dialog came up, but I could not type anything, move the mouse or switch VT. I suspended the machine again, and the next time it came up fine.
Attached is a dmesg after 3 suspend/resume cycles.
Ok, I retried with latest updates, and the behaviour has changed. I freshly booted, and then did the 4 command as described, and attached above. Then I tried to suspend 3 times, every time it took *very* long to go to sleep, more than one minute. Eventually it flashes some text on the screen about CIFS, and then goes to sleep. Before it would flash said text, and then come back up in X. In the dmesg I could find the text, it is:
[ 27.635409] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 27.635476] CIFS VFS: cifs_mount failed w/return code = -101
This message is repeated every time I try to suspend the machine. Laptop was running on battery power, and no CIFS shares are mounted. The SMB daemon is running however, but I have not defined any shares.
After the second suspend, the machine would power on again, and go into X, and the password dialog came up, but I could not type anything, move the mouse or switch VT. I suspended the machine again, and the next time it came up fine.
Attached is a dmesg after 3 suspend/resume cycles.