[Dell Inc. XPS M1530] suspend/resume failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Fully updated karmic system. Fails to suspend. The system blanks the screen and there's some hard drive activity, but the backlight stays on, and the power light never begins to fade in and out (as it would if suspended). This worked just fine in jaunty. I tried it with and without the nvidia kernel modules installed. This report is from the install without the nvidia modules.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 21'
Mixer name : 'SigmaTel STAC9228'
Components : 'HDA:83847616,
Controls : 29
Simple ctrls : 19
Date: Wed Oct 14 06:37:49 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. XPS M1530
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RelatedPackageV
SourcePackage: linux
Tags: resume suspend
Title: [Dell Inc. XPS M1530] suspend/resume failure
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:
dmi.bios.date: 07/14/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0D501F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS M1530
dmi.sys.vendor: Dell Inc.
I have a similar problem in terms of symptoms on a Dell Inspiron 9400, also running Karmic.
In my case, the suspend only fails the _second_ time I attempt it after a fresh boot. The first time seems to suspend and resume fine (although obviously something is different). It began to occur after the last kernel upgrade (although it may be related to one of the other many packages that also upgraded), so its only been happening the last couple of days.
Scott, is this the same with you? If not i'll open a new bug report.