[Presario C500] Hibernate command fails and returns to userspace

Bug #898615 reported by Luis Andrés Gonzalez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

When issuing the "Hibernate" command on the panel, or via the terminal, the screen goes black for seconds and then returns to userspace as if resuming from a suspension.
Hibernate Script Version 1.99

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-13-generic 3.0.0-13.22
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
Uname: Linux 3.0.0-13-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: luis 1911 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0340000 irq 42'
   Mixer name : 'Conexant CX20549 (Venice)'
   Components : 'HDA:14f15045,103c30a5,00100100'
   Controls : 20
   Simple ctrls : 9
Date: Thu Dec 1 10:40:56 2011
HibernationDevice: RESUME=UUID=4e8b0c55-0342-49d0-aac7-99eefff55276
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario C500 (GB125LA#AC8)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic root=UUID=c016a54f-5b56-4f36-adcc-a8cb375febe5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic N/A
 linux-backports-modules-3.0.0-13-generic N/A
 linux-firmware 1.60
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-10-19 (43 days ago)
dmi.bios.date: 03/09/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.15
dmi.board.name: 30C6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.15:bd03/09/2007:svnHewlett-Packard:pnPresarioC500(GB125LA#AC8):pvrF.15:rvnHewlett-Packard:rn30C6:rvr78.10:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario C500 (GB125LA#AC8)
dmi.product.version: F.15
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Thanks in advance.

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Joseph:
I've installed the .deb of the 3.2-rcN kernel from here http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc3-oneiric/, but it doesn't appear on the GRUB boot screen. Any ideas?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you post the output from the following: dpkg -l | grep linux-image

tags: added: kernel-fixed-upstream-v3.2-rc2
removed: needs-upstream-testing
Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Worked with the with the v3.2 rc2 kernel

tags: added: kernel-bug-exists-upstream
removed: kernel-fixed-upstream-v3.2-rc2
Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Bad news. After a series of attempts apparently it's not working again. Now it works only sometimes, but I can't tell what's different when it succeeds and when it doesn't.

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :
Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Update: Running in command line mode, it works.
Suspension is having the same problem now.

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Booting with nomodeset option doesn't solve the suspension issue.

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Does this dmesg mean anything?

[ 198.632108] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
[ 198.632226] mount.nfs D ff001100 0 932 931 0x00800004

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Tried this:
    luis@fenix:~$ s2ram
    KMS graphics driver is in use, skipping quirks.
    /sys/power/state does not exist; what kind of ninja mutant machine is this?

Also tried to unmount fuse filesystems using fusermount -u, without any success.

According to the #ubuntu channel user "sipior":
> "I would say that the information about the mount.nfs error and fuse might be a useful thing to add to your bug report. it seems > likely that hibernate is stalling on some pending volume unmount. the person dealing with the bug reports might have a better
> idea about how to test that further (or perhaps it's a duplicate of a bug seen elsewhere)"

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Here is a succession of attempts to suspend.
Note that on the first attempts it works (from [10835.279254] to [10835.773093]), and after that there's a second failed attempt ([10862.938115] to end).

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

Output of mount
===============

luis@fenix:~$ mount
/dev/sda5 on / type ext3 (rw,errors=remount-ro,commit=0)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
/dev/sda1 on /media/sda1 type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)
/dev/sda7 on /media/Datos type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)

Output of fstab
===============
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=c016a54f-5b56-4f36-adcc-a8cb375febe5 / ext3 errors=remount-ro 0 1
/dev/sda6 none swap sw 0 0
/dev/sda1 /media/sda1 ntfs nls=iso8859-1,umask=000 0 0
/dev/sda7 /media/Datos ntfs nls=iso8859-1,umask=000,owner,uid=luis 0 0
192.168.1.15:/home/rodrigo/Música /mnt/musicas nfs defaults 0 0

Revision history for this message
Luis Andrés Gonzalez (luisandresgonzalez) wrote :

The problem appears to be SOLVED.

I commented out the last line of the fstab that mounts an nfs file share (thanks to the suggestion of user roadmr).
Restarted and now after 3 attemps of suspending and hibernating worked without any problems.

Tomorrow I'll try a stress test to see if the solution is stable, using https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting.

Revision history for this message
penalvch (penalvch) wrote :

Luis Andrés Gonzalez, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume ? As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please note that one will need to install Ubuntu to test hibernate, as at this time, hibernate does not work in a live environment.

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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