Operating systeam crashes when wakeup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I close my notebook (The operating system is asleep) while I am running my program and I open (operating system wakes up and asks me the password) I get a kernel error that is the attachment.
My notebook is a Packard Bell.
My English is not very good.
I hope to help.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No existe el fichero ó directorio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2700000 irq 22'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,
Controls : 17
Simple ctrls : 11
Date: Wed Dec 16 17:15:07 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: PACKARD BELL BV EasyNote MH36
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
1: phy1: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 03/12/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: PBPE2L0N.P08
dmi.board.name: PE2L
dmi.board.vendor: PACKARD BELL BV
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: PACKARD BELL BV
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: EasyNote MH36
dmi.product.
dmi.sys.vendor: PACKARD BELL BV
Hi Ezequiel,
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.260 seconds. 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.]