Error popped up after resumption from standby.

Bug #459900 reported by FromCrimsonToWool
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Error did not seem to affect normal activity.

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: crimson 1755 F.... pulseaudio
 /dev/snd/pcmC0D0p: crimson 1755 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8235'/'VIA 8235 with ALC650F at 0x8800, irq 22'
   Mixer name : 'Realtek ALC650F'
   Components : 'AC97a:414c4723'
   Controls : 57
   Simple ctrls : 36
Card1.Amixer.info:
 Card hw:1 'modem'/'VIA 82XX modem at 0x8c00, irq 22'
   Mixer name : 'Silicon Laboratory Si3036,8 rev 2'
   Components : 'AC97m:53494c22'
   Controls : 3
   Simple ctrls : 3
Card1.Codecs.codec97.0.mc97.1.1:
 1-1/0: Silicon Laboratory Si3036,8 rev 2

 Extended modem ID: codec=1 LIN1
 Modem status : GPIO MREF ADC1 DAC1 PRE(ADC2) PRF(DAC2) PRG(HADC) PRH(HDAC)
 Line1 rate : 8000Hz
Date: Sat Oct 24 13:00:03 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=cd912c0a-ac63-4741-8556-63dfacd21459
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 002: ID 0ac8:301b Z-Star Microelectronics Corp. ZC0301 Webcam
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Midern sag168168 K8T800
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=1e2cb7bf-fe53-4ec3-89f9-4bab678ddf18 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:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
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: 06/04/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: 4.06CJ15
dmi.board.name: K8T800
dmi.board.vendor: VIA
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd06/04/2005:svnMidernsag168168:pnK8T800:pvrVT8204B:rvnVIA:rnK8T800:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: K8T800
dmi.product.version: VT8204B
dmi.sys.vendor: Midern sag168168

Revision history for this message
FromCrimsonToWool (fromcrimsontowool+launchpad) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi FromCrimsonToWool,

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. Based on your dmesg output I see PM: resume devices took 6.868 seconds. 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
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 417842, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Confirmed
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.