This is the same as bug 467412. (No way to add to that bug as far as I can find. So I'm reporting it as new.)

Bug #472124 reported by Tom W
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a continuation of bug 467412. -- System reports this error
when coming out of hibernation. I am told the system is supposed to
start within 5 seconds and my system is taking over 7 seconds to
restart. I believe this might be correct. I do have a weather applet
running on the panel, and the system does take a few seconds to
re-connect to the LAN. Perhaps patch to allow, maybe, 10 seconds??

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tom 2220 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfeaf4000 irq 22'
   Mixer name : 'Intel G45 DEVELK'
   Components : 'HDA:10ec0662,10280283,00100101 HDA:80862803,80860101,00100000'
   Controls : 28
   Simple ctrls : 15
Date: Mon Nov 2 22:36:05 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=1114794e-6661-4201-9d81-34d72976afc7
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Vostro 220 Series
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=78fed102-9bad-47a0-aaa7-2fbb4e563db6 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
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 06/26/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 0P301D
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/26/2009:svnDellInc.:pnVostro220Series:pvr:rvnDellInc.:rn0P301D:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 220 Series
dmi.sys.vendor: Dell Inc.

Revision history for this message
Tom W (tom-weslowski) 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:

  [31053.851245] PM: resume devices took 8.112 seconds

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

iEYEARECAAYFAkrxrUkACgkQ7kQoFRG3d6/toACfYpBUq7eRpQ3c1991ftPKKcA3
Z8IAoKGyLYXgIUlFH+jU5p+/0pp03aUB
=EJDK
-----END PGP SIGNATURE-----

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

Hi Tom,

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 8.112 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.