Kernel failure after suspend/resume

[Eric Bartels]

I installed the kerneloops package to test suspend/resume and am getting a failure report:

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

Suspend and resume seem to be working for the most part, the only problem I've noticed is the wired network device refuses to work after resuming. I'm not sure if the network problem is related to the kernel oops or a separate problem altogether.

Description: Ubuntu jaunty (development branch)
Release: 9.04
Uname: Linux 2.6.28-11-generic i686

The network card uses the r8169 module, and is reported as:
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

This was created with the automated bug report tool, so let me know if you need me to provide any more information.
Thanks!

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
DistroRelease: Ubuntu 9.04
Failure: oops
MachineType: Hewlett-Packard HP Pavilion dv5 Notebook PC
NonfreeKernelModules: fglrx
Package: linux-image-2.6.28-11-generic 2.6.28-11.40
ProcCmdLine: root=UUID=1e3741e5-a280-438f-ad2d-440127d7643d ro quiet splash i8042.reset
ProcVersionSignature: Ubuntu 2.6.28-11.40-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()

[Tormod Volden (tormodvolden)]

Thanks for your report. Do you have a syslog or dmesg output where the warning is present? (And not just the call trace like in OopsText above.)

[Eric Bartels (ebartels)]

Thanks. Attached dmesg output with the warning.

[Eric Bartels (ebartels)]

Also, this seems unrelated to problems with the r8169 module, as adding it to SUSPEND_MODULES in /etc/pm/config.d fixes issues with network availability after resume, but the kernel warning still occurs in either case.

[kernel-janitor (kernel-janitor)]

Hi Eric,

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

[Leann Ogasawara (leannogasawara)]

Hi Eric,

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.