[Dell Inc. Latitude D820] suspend/resume failure [non-free: nvidia]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Suspend failure, computer never successfully suspended, kernel panic on screen when I opened laptop. I'm not sure if I have enough information - this is the first time I've encountered this on this installation.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
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 0xefffc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,
Controls : 12
Simple ctrls : 7
Date: Thu Oct 8 12:55:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Latitude D820
NonfreeKernelMo
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RelatedPackageV
SourcePackage: linux
Tags: resume suspend
Title: [Dell Inc. Latitude D820] suspend/resume failure [non-free: nvidia]
Uname: Linux 2.6.31-12-generic x86_64
UserGroups:
dmi.bios.date: 06/04/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0JF240
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D820
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this crash and helping to make
Ubuntu better. This particular crash has already been reported and is a
duplicate of bug #429899, so is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Please continue to report any other bugs you may
find.