[Dell Inc. Latitude D830] late resume failure [non-free: nvidia]

[Rockwalrus]

Crash occurred on resume.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally.
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nsummers 4586 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2472 @ 40), (3, 27)
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21'
   Mixer name : 'SigmaTel STAC9205'
   Components : 'HDA:838476a0,102801fe,00100204 HDA:14f12c06,14f1000f,00100000'
   Controls : 25
   Simple ctrls : 16
Date: Mon Apr 26 23:26:22 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: late resume
HibernationDevice: RESUME=UUID=86c66d25-492e-4752-ae25-bea66258bcf7
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Latitude D830
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-20-generic 2.6.31-20.58
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=2901cb8b-2558-464e-8c80-ce031718503a ro quiet splash crashkernel=384M-2G:64M,2G-:128M
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
SourcePackage: linux
Tags: resume suspend resume-late-hang
Title: [Dell Inc. Latitude D830] late resume failure [non-free: nvidia]
Uname: Linux 2.6.31-20-generic x86_64
UserGroups:

WifiSyslog:
 Apr 27 08:48:10 finland kernel: [35515.639801] IN=wlan0 OUT= MAC= SRC=192.168.0.4 DST=224.0.0.251 LEN=68 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=48
 Apr 27 08:48:27 finland kernel: [35532.729455] IN=wlan0 OUT= MAC=01:00:5e:00:00:fb:00:30:18:a4:6e:1d:08:00 SRC=192.168.0.3 DST=224.0.0.251 LEN=68 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=48
WpaSupplicantLog:

dmi.bios.date: 12/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0UY141
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/11/2008:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D830
dmi.sys.vendor: Dell Inc.

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi all,

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Please, can you tell us whether this is still an issue for you? If not, please, consider update this bug as 'Fix Released', else, can you please, fill a little form, with questions contained in this wiki? https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume

It will definitely help developers to find the fix or help you to detect that you don't really have real bug. Please, pay special attention to the "Encrypted Home-Swap" issue and the flashing caps-lock.

Information below, will also help you

https://wiki.ubuntu.com/UnderstandingSuspend

I'd also encourage you to try this tests https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting to gather more information to developers.

We also remember you that every bug needs to be tested with latest stable kernel version before being triaged. So, please, can you include some test with latest Lucid version?

Thank you in advance.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]