WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
i don't know what this bug is but i think this info may help the developers
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
Cannot stat file /proc/1978/fd/22: Permission denied
/dev/snd/
/dev/snd/pcmC0D0p: mshtawythug 1652 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd2500000 irq 22'
Mixer name : 'Conexant CX20551 (Waikiki)'
Components : 'HDA:14f15047,
Controls : 18
Simple ctrls : 11
Date: Mon Nov 2 15:33:21 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: TOSHIBA Satellite P100
NonfreeKernelMo
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: 09/04/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.40
dmi.board.name: Satellite P100
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite P100
dmi.product.
dmi.sys.vendor: TOSHIBA
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.