WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()

Bug #298541 reported by Dmytro Korzhevin
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Ubuntu 8.10
kerneloops Version: 0.10-2ubuntu1

Crash right after install kerneloops.

Maby it is possible to backport new version of kerneloops program (0.12)?

http://www.kerneloops.org/

ProblemType: KernelOops
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: linux-image-2.6.27-8-generic 2.6.27-8.17
ProcCmdLine: User Name=UUID=9550e1b3-7d98-43e2-b530-e03f9f7e351b ro quiet splash
ProcVersionSignature: Ubuntu 2.6.27-8.17-generic
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()

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

The message you are seeing is usually related to suspend/resume. Primarily that it took longer than expected to bring up your devices. So I don't believe this is an issue with kerneloops itself as it did what it should which is flagged that you got this error.

Had you attempted a suspend/resume when you got this? If so, were you able to successfully resume?

Changed in linux:
status: New → Incomplete
Revision history for this message
Jonas Petersson (catellie) wrote :

I didn't report this, but I have the same problem. I see these message after I resume from suspend to ram (from the gnome-power-manager battery icon). Most of the time, it works anyway, but I see two annoying signs if things being somewhat broken:

* My battery is listed multiple times in the power manager menu (seems to increase - I had 4 a few days ago, now I have 5).

* Similarly, the NetworkManger Applet (as well as nm-tool) lists my network deviced multiple times - at the moment I have 4 eth0, 5 wlan0 and finally another eth0.

All of the above list correct information and seemingly work (although the network sometimes seems trip in itself, so a manual select is needed for it to get back on track).

It is annoying and I never experienced this on Hardy (which needed a few module hacks for my system, but not much). I'm using Intrepid on a MacBookPro 4,1 with just the Rydberg bits added: http://web.comhem.se/rydberg/Bits/

Revision history for this message
sam tygier (samtygier) wrote :

probable dupe of Bug #286672 and Bug #287453

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

I'm marking this as a duplicate of bug 286672. Please continue to track this issue with 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.