Hibernate on Dell laptop occasionally hangs

Bug #663575 reported by Alex Cabal
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have a Dell Vostro 1400 laptop, stock parts. I have it set to hibernate on closing the lid. Hardy thru Lucid had no problems with hibernate. However, on a clean Maverick install, occasionally the hibernate process hangs. I close the lid and the system remains in a powered on state. When I open the lid to check what's happened, I see a black screen with a blinking cursor in the upper left corner. The system must then be powered off by holding the power button and then boots fresh, without hibernate data.

This doesn't happen every time; maybe every 3rd time. I'm not sure what causes it, other than it happens frequently enough to be a problem for me.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.34
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 2788 F.... pulseaudio
 /dev/snd/pcmC0D0p: alex 2788 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 47'
   Mixer name : 'SigmaTel STAC9228'
   Components : 'HDA:83847616,10280227,00100201 HDA:14f12c06,14f1000f,00100000'
   Controls : 27
   Simple ctrls : 18
Date: Wed Oct 20 00:31:05 2010
HibernationDevice: RESUME=UUID=b5c9bb05-3418-4c43-9b3b-9e57fccc6cd1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Dell Inc. Vostro 1400
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=df392af0-8d30-4115-b251-38bfdc23f1fa ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 07/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0TT347
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/10/2008:svnDellInc.:pnVostro1400:pvr:rvnDellInc.:rn0TT347:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1400
dmi.sys.vendor: Dell Inc.

Revision history for this message
Alex Cabal (acabal) wrote :
Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :

Same here, Dell inspiron 1525 with Intel i915 graphics. Worked fine with 10.04, busted on 10.10.

See also #664269

Revision history for this message
Joe Pimentel (joe-b-pimentel) wrote :

Same here (Kubuntu), Dell Vostro 1320. I suffer from it in 10.04 before upgrade using hibernate-disk in a command line. Sometimes hibernate-disk hangs itself (but it seems to be less frequent before upgrade). Sometimes it does nothing and return to the graphic session (may be related to ammount of memory used by apps).

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Radek Maňásek (radek-manasek+ubuntu) wrote :

Same here Ubuntu 11.04 laptop Dell Latitude D620. I use hibernate-disk command. The indications are exactly like Alex described. Only difference is that I can see message "Looking for splash screen ... none" on the screen.

Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :

This is an older Kernel bug as far as I can tell. Are you all up to date ? Do you have any network mounts ?

Revision history for this message
Alex Cabal (acabal) wrote :

This seems to have been fixed at some point with a Maverick kernel update, however now on Natty the problem has returned. I'm using a different Dell laptop now though. Maybe 1/3 of the time the system will freeze at a black console screen when hibernating and won't power down. I have to power cycle to get it to turn off. After power cycling it goes through a normal boot, so hibernate data wasn't saved.

Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :

Try logging in at the command line (CTRL-ALT-F1) then run
# sudo -i
then
# tail -f /var/log/messages &
then trigger a hibernate from the command line (not sure of how Natty does that, sorry !(

Revision history for this message
Radek Maňásek (radek-manasek+ubuntu) wrote :

to Tom:
After fresh restart of the system I do not have any local/network mounts, but usually later I access a NTFS partition from GUI- My Places, which is mounted automatically into /media/DATA. I have also some network mounting of samba configured in fstab, which is not mounted automatically after start of the system. I am pretty confident I did not have mounted the network devices when the problem appeared again.
What should be the outcome from the #7 ? Should I try it when it does not want to hibernate by normal way? I will try it when I am on the Dell laptop.
Thanks

Revision history for this message
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote :

Yes, you should try to tail the log when it doesn't work.

You say you have network mounts, it maybe these are not being unmounted before the network is brought down, which will lead to a hang while they timeout, this could be minutes.
It's a known bug e.g. https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/681829

Revision history for this message
penalvch (penalvch) wrote :

Alex Cabal, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → 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.