Crash report after resuming

Bug #472282 reported by nostra
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

The crash happens every time i recover from suspend mode.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: cer 2545 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdb320000 irq 17'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30e7,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 22
   Simple ctrls : 14
Date: Tue Nov 3 08:26:45 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=1856b328-d3e3-4235-9869-4a49b6f5e52d
MachineType: Hewlett-Packard HP EliteBook 8530w
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   product info: "RICOH", "Bay8Controller", "", ""
   manfid: 0x0000, 0x0000
   function: 254 (unknown)
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=4bf4bdd2-2e13-43a3-a30d-3e78a6e80aa4 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PDV Ver. F.0E
dmi.board.name: 30E7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 90.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDVVer.F.0E:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.0E:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8530w
dmi.product.version: F.0E
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
nostra (nostra) wrote :
Revision history for this message
Andy Whitcroft (apw) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is a false positive trigger as the resume was a little slower than we might have liked. Nothing serious occured. Upstream has upped the limit recently and we will now be following suit. This is a duplicate of the bug #464552:

  [12804.556444] PM: resume devices took 5.410 seconds
[84467.476437] PM: resume devices took 5.290 seconds

 duplicate 464552
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEUEARECAAYFAkrxrSIACgkQ7kQoFRG3d6/iKQCXfJi0/8nlUQoaEjX0dyIq46ln
+ACfRwSMbUokdy1XkTDsjJfO1OSVPdQ=
=Xcbk
-----END PGP SIGNATURE-----

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi nostra,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Based on your dmesg output I see PM: resume devices took 5.410 seconds. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

tags: added: suspend-test-finish
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.