WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90()

Bug #399114 reported by kfolka
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Ran update and rebooted

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
DistroRelease: Ubuntu 9.04
Failure: oops
HibernationDevice: RESUME=UUID=00128a37-7902-44f9-8186-ea401e94a89f
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c51b Logitech, Inc.
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
NonfreeKernelModules: nvidia wl
Package: linux-image-2.6.28-13-generic 2.6.28-13.45
ProcCmdLine: root=UUID=689ab6e9-c79e-4c28-82af-cdff687781ce ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-13.45-generic
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x80/0x90()

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

Hi kfolka,

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. Typically you'll see something similar to "PM: resume devices took 8.664 seconds" in your dmesg output when this happens. 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
Leann Ogasawara (leannogasawara) wrote :

Hi kfolka,

I'm going to mark this as a duplicate to bug 464552 as a patch is going to be applied to increase the barrier from 5sec to 10sec. Please continue to track this issue at that report. Thanks.

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.