"Serious Kernel Error" on Thinkpad T43, usually after hibernation/suspension wakeup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Running Ubuntu 9.10 Beta on Thinkpad T43 with 2g Ram, ATI x300 GPU, 2.0 GHz Pentium M CPU.
The oops is usually triggered after wakueup from hibernation or suspension, even the automatic one triggered when the lid id closd. Sometimes it will re-suspend after the lid is open and the error report comes up.
It was also triggered while I was surfing Facebook on firefox. It told me to restart after I sent bug reports in all cases, although the computer functions perfectly normally if I do not.
None of the suggested commands below printed an output.
On a side note, the computer sees a floppy drive that is not here.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
Mixer name : 'Analog Devices AD1981B'
Components : 'AC97a:41445374'
Controls : 26
Simple ctrls : 18
Date: Sun Oct 18 18:35:21 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: IBM 2668WMY
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 02/20/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1YET61WW (1.26 )
dmi.board.name: 2668WMY
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.
dmi.modalias: dmi:bvnIBM:
dmi.product.name: 2668WMY
dmi.product.
dmi.sys.vendor: IBM
Hi Patrick,
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 5.008 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]