When sttarting system, i looked message from X "Критиченская ошибка в Ядре"

Bug #473468 reported by Rasamasan
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

When sttarting system, i looked message from X "Критиченская ошибка в Ядре" (russian)

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: romeo 1570 F.... pulseaudio
 /dev/snd/pcmC0D0p: romeo 1570 F...m pulseaudio
 /dev/snd/controlC1: romeo 1570 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with AD1985 at irq 17'
   Mixer name : 'Analog Devices AD1985'
   Components : 'AC97a:41445375'
   Controls : 50
   Simple ctrls : 35
Card1.Amixer.info:
 Card hw:1 'SAA7134'/'saa7134[0] at 0xfeaff400 irq 21'
   Mixer name : 'SAA7134 Mixer'
   Components : ''
   Controls : 6
   Simple ctrls : 3
Date: Tue Nov 3 20:43:46 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=04d37420-5071-43fa-967f-017fb744098b
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 ppp0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
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=13660e3a-9cb4-42f2-8fc3-15204c88413d 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+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 08/20/2003
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080009
dmi.board.name: P4P800
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080009:bd08/20/2003:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4P800:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Rasamasan (rasamasan-deactivatedaccount) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Rasamasan,

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