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

Bug #368090 reported by Carl Karsten on 2009-04-27
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

added a new video card. no display, sshed in from a 2nd box, sudo halt. checked cables, powered on, got crash report.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
DistroRelease: Ubuntu 9.04
Failure: oops
HibernationDevice: RESUME=UUID=12028010-a84f-4614-bf6d-43c44ba39cd3
 Bus 002 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
 Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway GT5032
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=c6030fcd-7844-4d65-bb31-4a13009080bd ro vga=6
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.28/kernel/power/main.c:177 suspend_test_finish+0x7c/0x80()

Carl Karsten (carlfk) wrote :
paraiko (paraiko) wrote :

Form me this is a kernel oops that I get after a reboot from a hard lockup of the system.

Hi Carl,

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

Hi Carl,

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  Edit
Everyone can see this information.

Other bug subscribers