[Dell XPS L702X] hibernate/resume failure

Bug #1073447 reported by Sparhawk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Crashed while hibernating. This occurs about 20–30% of the time. (And crashes while resuming about 10% of the time.)

ProblemType: KernelOops
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lee 2442 F.... pulseaudio
CRDA:
 country AU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (3, 23)
  (5250 - 5330 @ 40), (3, 23), DFS
  (5735 - 5835 @ 40), (3, 30)
Date: Wed Oct 31 17:36:57 2012
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28
InstallationDate: Installed on 2012-01-25 (279 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python3.2mu
MachineType: Dell Inc. Dell System XPS L702X
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro acpi_backlight=vendor
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
SourcePackage: linux
Title: [Dell Inc. Dell System XPS L702X] hibernate/resume failure
UpgradeStatus: Upgraded to quantal on 2012-10-19 (12 days ago)
UserGroups:

dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0XN71K
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L702X
dmi.sys.vendor: Dell Inc.

Revision history for this message
Sparhawk (sparhawkthesecond) 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? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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, 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.7-rc2-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
Revision history for this message
Sparhawk (sparhawkthesecond) wrote :

I tried to install the latest kernel [1], but ran into some errors.

Error! Bad return status for module build on kernel: 3.7.0-030700rc6-generic (x86_64)
Consult /var/lib/dkms/nvidia-current/304.43/build/make.log for more information.
Error! Bad return status for module build on kernel: 3.7.0-030700rc6-generic (x86_64)
Consult /var/lib/dkms/virtualbox/4.1.18/build/make.log for more information.

I checked the respective logs, but couldn't make much sense of them. Should I post them here? Apparently they failed to build?

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc6-raring/

Revision history for this message
Sparhawk (sparhawkthesecond) wrote :

FWIW I tried hibernating with this kernel anyway. It froze on a black screen when resuming the first time. I've marked the bug as "kernel-bug-exists-upstream" and "confirmed", but I suppose there is the caveat that the upstream kernel broke two things as mentioned.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: needs-upstream-testing regression-potential
tags: added: latest-bios-a19
summary: - [Dell Inc. Dell System XPS L702X] hibernate/resume failure
+ [Dell XPS L702X] hibernate/resume failure
Revision history for this message
penalvch (penalvch) wrote :

Sparhawk, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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>

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
Revision history for this message
Sparhawk (sparhawkthesecond) wrote :

Sorry for the delay. However, I'm not really in a position to test at the moment, so I'm happy with this bug remaining closed.

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.