almost always a crash report after a night not using computer (but not turning it off)

Bug #480614 reported by eppye.bots
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

at first it looked like a suspend-error, but today I had the same error while it was not suspended.
so either my computer tried to suspend, or there is an error in the crash reporting tool....

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: hje 1772 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe1280000 irq 16'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1458c603,00100002'
   Controls : 40
   Simple ctrls : 22
Date: Wed Nov 4 11:20:50 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=36a47caf-7896-4dc3-b440-52e4b268ff72
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=3c257ba8-48db-4fa8-ab39-f6a61af1e20d 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:

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: 08/20/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: G31M-ES2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/20/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
eppye.bots (hjebbers) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi eppye.bots,

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. A patch to prevent this warning has been applied via bug 464552. As a result I'm marking this as a duplicate to bug 464552. Please continue to track this issue at that report. Thanks!

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

tags: added: suspend-test-finish
Revision history for this message
eppye.bots (hjebbers) wrote : Re: [Bug 480614] Re: almost always a crash report after a night not using computer (but not turning it off)

Hi Leann,

thanks for the feedback!!

kind regards,
henk-jan

Leann Ogasawara wrote:
> *** This bug is a duplicate of bug 464552 ***
> https://bugs.launchpad.net/bugs/464552
>
> Hi eppye.bots,
>
> 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. A patch to prevent this warning has
> been applied via bug 464552. As a result I'm marking this as a
> duplicate to bug 464552. Please continue to track this issue at that
> report. Thanks!
>
> [This is an automated message. Apologies if it has reached you
> inappropriately.]
>
> ** Tags added: suspend-test-finish
>
> ** This bug has been marked a duplicate of bug 464552
> suspend_test_finish warning triggers too easily, increase timeout to match mainline times
>
>

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.