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) |
New
|
Undecided
|
Unassigned |
Bug Description
Mine came after an apparently correct suspend.
In particular my Fujitsu Lifebook always starts with none of the ACPI power devices recognized (e.g. the desktop battery icon thing doesn't recognize the AC adapter or the battery and the laptop is in extreme power save mode).
If I suspend the laptop and wake it up, all the power management stuff is fully recognized (and indeed the suspend works and wake works fully) but there is a kernel crash registered for aport.
This is a slightly different scenerio than listed in the similar bug reports so I figure it was worth its own ticket.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd0180000 irq 25'
Mixer name : 'Realtek ALC260'
Components : 'HDA:10ec0260,
Controls : 23
Simple ctrls : 15
Date: Sat Oct 31 19:04:13 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: FUJITSU N3410
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=/dev/
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 09/14/2005
dmi.bios.vendor: FUJITSU/Insyde
dmi.bios.version: Version 1.02
dmi.board.name: TOP03
dmi.board.vendor: FUJITSU
dmi.board.version: 0
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: AJ50N1A909000010
dmi.chassis.
dmi.modalias: dmi:bvnFUJITSU/
dmi.product.name: N3410
dmi.product.
dmi.sys.vendor: FUJITSU
:-/ Yes this seems to be happening to me as well. When ever I suspend and wake it up again it reports a Kernel Crash Report. I guess it will be fixed through updates. There is nothing wrong with anything but it reports that for some reason. I suggest this bug be taken seriously.