keyboard stopped responding - looks like computer went to sleep

[Stuart Johnson]

I left my computer idle for about 5 minutes and when I came back, the mouse was working - X would respond to button clicks, etc, but the keyboard wasn't. I had virtualbox running fullscreen at the time and could only get out of it after using the GUI.

The screen then showed garbage - like corrupted video memory - then back. The power button light was flashing as if the machine had gone to sleep. I pressed that and it came back up.

Everything seemed ok at that point except for the notification that said I'd had a serious (severe?) crash and would I like to report it. I did, and here's the result.

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: stuart 2524 F.... pulseaudio
 /dev/snd/pcmC0D0p: stuart 2524 F...m pulseaudio
 /dev/snd/pcmC0D0c: stuart 2524 F...m pulseaudio
 /dev/snd/controlC1: stuart 2524 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 20'
   Mixer name : 'Nvidia MCP78 HDMI'
   Components : 'HDA:10ec0888,104382fe,00100101 HDA:10de0002,10de0101,00100000'
   Controls : 44
   Simple ctrls : 23
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8b5'/'USB Device 0x46d:0x8b5 at usb-0000:00:02.1-2.4, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08b5'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 3
   Mono: Capture 0 [0%] [30.00dB] [on]
Date: Fri Oct 9 17:14:51 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=50a93268-e8fc-43ff-a2f3-a70338a479ef
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-13-generic 2.6.31-13.42
ProcCmdLine: root=UUID=3f05b846-6811-4873-84b5-09728ec6c1f7 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
RelatedPackageVersions: linux-firmware 1.21
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-13-generic i686
WpaSupplicantLog:

dmi.bios.date: 09/14/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0704
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3N78-EM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd09/14/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Leann Ogasawara (leannogasawara)]

Hi Stuart,

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 9.852 seconds. I'm setting this to traiged for further investigation. Thanks!

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

[Brian Murray (brian-murray)]

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.