[ASUSTeK COMPUTER INC. G75VW] hibernate/resume failure [non-free: nvidia]

Bug #1224218 reported by Rainer Rohde
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
uswsusp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My laptop hung after trying to come out of hibernate, and I had to power it off and back on to let it reboot normally.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-7-generic 3.11.0-7.13
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: nvidia
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rrohde 2224 F.... pulseaudio
 /dev/snd/controlC0: rrohde 2224 F.... pulseaudio
Date: Wed Sep 11 17:15:33 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InterpreterPath: /usr/bin/python3.3
MachineType: ASUSTeK COMPUTER INC. G75VW
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=4dac4492-a4d7-4a6d-97bf-ed5c1ee0b1a0 ro elevator=noop quiet splash resume=/swapfile.swap vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.113
SourcePackage: linux
StagingDrivers: zram
Title: [ASUSTeK COMPUTER INC. G75VW] hibernate/resume failure [non-free: nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

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? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0].

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, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

@Joseph,

this is not a kernel issue, however, a plymouth vs uswsusp.

This seems to be a known issue, and the question is why can't this be fixed by Canonical?

Here's the note I have:

"Aha! I figured it out -- I'd worked around this in the previous release
but forgotten about it. It's a bad interaction between uswsusp and
plymouth. So this is basically a duplicate of #816859, which has an
easy workaround, which makes me wonder why Ubuntu maintainers can't take
the trouble of adding a two-line fix to /usr/share/initramfs-
tools/scripts/local-premount/uswsusp."

The workaround:

patch <<EOF uswsusp
--- uswsusp.orig
+++ uswsusp
@@ -34,4 +34,6 @@
      mknod /dev/snapshot c ${DEV%:*} ${DEV#*:}
 fi

+[ -x /bin/plymouth ] && plymouth quit
+
 /sbin/resume
EOF

affects: linux (Ubuntu) → uswsusp (Ubuntu)
Changed in uswsusp (Ubuntu):
importance: Medium → Undecided
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in uswsusp (Ubuntu):
status: New → Confirmed
Revision history for this message
zhanghongce (zhanghongce) wrote :

@Rainer Rohde
I'm not sure if I did correctly to get it fixed as you suggested. After adding that line to "/usr/share/initramfs-tools/scripts/local-premount/uswsusp", resume from hibernation goes on without problems, but normal boot is affected, too. Plymouth seemed to be killed halfway when booting, and I got no splash. What's more, lightdm wouldn't start automatically, and I had to press "crtl-alt-F1" to console and type
"sudo service lightdm start"
I'm not sure what's wrong with it, any suggestion?

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.