WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()

Bug #460789 reported by JohnMitchell
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

no idea, I get this red box saying something about a crash.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: johnm 1306 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 22'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,103c2a36,00100101'
   Controls : 37
   Simple ctrls : 20
Date: Sat Oct 24 09:59:01 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=26cc562a-7a50-40b2-bb05-99a4c58243ca
MachineType: HP-Pavilion RP829AV-ABA d4790y
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=/dev/sdc3 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:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
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: 03/30/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.08
dmi.board.name: Basswood2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.05
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.08:bd03/30/2007:svnHP-Pavilion:pnRP829AV-ABAd4790y:pvr:rvnASUSTekComputerINC.:rnBasswood2:rvr1.05:cvnHewlett-Packard:ct3:cvr1111:
dmi.product.name: RP829AV-ABA d4790y
dmi.sys.vendor: HP-Pavilion

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

Hi JohnMitchell,

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 11.250 seconds. I'm setting this to traiged for further investigation. Thanks!

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

tags: added: suspend-test-finish
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
JohnMitchell (johnlmitchell) wrote : Re: [Bug 460789] Re: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()

Hi Leann,

That explanation makes perfect sense. I have an external hard drive
(ST3750640AS) which can be slow to come up -- several seconds. In
addition, I suspend my computer at night.

If I can provide more information, please let me know. I'm a
programmer so you can speak geek if that helps :)

thanks so much!
- john

On Mon, Oct 26, 2009 at 5:18 PM, Leann Ogasawara
<email address hidden> wrote:
> Hi JohnMitchell,
>
> 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 11.250 seconds.  I'm setting this
> to traiged for further investigation.  Thanks!
>
> [This is an automated message.  Apologies if it has reached you
> inappropriately.]
>
> ** Tags added: suspend-test-finish
>
> ** Changed in: linux (Ubuntu)
>       Status: New => Triaged
>
> ** Changed in: linux (Ubuntu)
>   Importance: Undecided => Medium
>
> --
> WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x7c/0x80()
> https://bugs.launchpad.net/bugs/460789
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it 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.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
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.