Laptop crashes on 'wake up' after lid has been closed instead of >log out>shut down.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Laptop crashes on 'wake up' after lid has been closed instead of >log out>shut down from the menu.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xf2680000 irq 21'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 11
Simple ctrls : 8
Date: Sun Oct 4 07:24:57 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5520
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.20
RfKill:
0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-11-generic x86_64
dmi.bios.date: 12/12/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.20
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5520
dmi.product.
dmi.sys.vendor: Acer
Hi Prosiedem,
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 11.080 seconds. I'm setting this to traiged for further investigation. Thanks!
[This is an automated message. Apologies if it has reached you inappropriately.]