[K8M890] ubuntu crashes after laptop unplug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I was simply testing out the program "cheese" when I decided to go out into my living room. I unplugged my laptop and got ready to go when all of a sudden.
I just hope this does not happen again.
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'V8237'/'VIA 8237 with ALC655 at 0xf000, irq 22'
Mixer name : 'Realtek ALC655 rev 1'
Components : 'AC97a:414c4761'
Controls : 48
Simple ctrls : 29
Date: Wed Nov 4 23:27:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/
Failure: suspend/resume
HibernationDevice: RESUME=
InterpreterPath: /usr/bin/python2.6
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Equus Computer Systems Nobilis
Package: linux-image-
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: resume suspend
Title: [Equus Computer Systems Nobilis] suspend/resume failure
Uname: Linux 2.6.31-14-generic i686
UserGroups:
WpaSupplicantLog:
dmi.bios.date: 08/30/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 641W1P24
dmi.board.name: K8M890-8237
dmi.board.vendor: Winfast
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Nobilis
dmi.sys.vendor: Equus Computer Systems
Hi Fernando,
So this has happened only the one time? Have you tried to reproduce at all? I do see the following in your CurrentDmesg.txt file:
[ 102.400352] powernow-k8: Hardware error - pending bit very stuck - no further pstate changes possible
[ 102.400359] powernow-k8: transition frequency failed
[ 102.540014] powernow-k8: failing targ, change pending bit set
I'd be curious to know if there are any other errors that may have been captured in /var/log/kern.log.0 after this happened.