[hardy] sometimes fails to suspend, lots of kernel messages in logs

Bug #219396 reported by Jos Dehaes
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.24

In gutsy, my laptop (dell latitude D820, nvidia) could suspend/resume without problems. It also worked fine in hardy some time earlier. But lately, often the machine refuses to suspend, it sits on a console for some time, and then switches back to X. When I check the logs, there are many entries that look like kernel stacktraces (see attachment). This is a regression.

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Jos,

Care to pull in the latest updates and if the issue still exists, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
Jos Dehaes (jos-dehaes) wrote :
Revision history for this message
Jos Dehaes (jos-dehaes) wrote :
Revision history for this message
Jos Dehaes (jos-dehaes) wrote :
Revision history for this message
Jos Dehaes (jos-dehaes) wrote :
Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

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.

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

I was wrong in the previous post, the SMB daemon is not running, in fact it is not even installed. Why is it blocking on some CIFS call?

The following related packages are installed:

jos@duet ~ $ dpkg-query -l smb*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii smbclient 3.0.28a-1ubunt a LanManager-like simple client for Unix
ii smbfs 3.0.28a-1ubunt mount and umount commands for the smbfs (for
un smbfsx <none> (no description available)
un smbget <none> (no description available)

jos@duet ~ $ dpkg-query -l samba*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
in samba <none> (no description available)
un samba-client <none> (no description available)
ii samba-common 3.0.28a-1ubunt Samba common files used by both the server a

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

Ok, the CIFS error put me on the right track. There was a CIFS mount defined in /etc/fstab, from the work network, that is not accessible from home. I forgot the noauto parameter. After I added the noauto mount option, I was able to suspend resume 6 times in a row without problem. Marking as invalid.

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.