Error icon appeared right after booting without visible reason.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 9.10 booted fine from power off state. But still the error icon appeared to top toolbar without any visible raeson to it. In previous run I used sleep to ram, which always after waking makes error icon appear. After this previous run's icon appeared I clicked it off without actually reading it (by not entering password). So could this error come as a ghost from that previous error.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
Card0.Amixer.info:
Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
Mixer name : '20K1'
Components : ''
Controls : 29
Simple ctrls : 10
Card1.Amixer.info:
Card hw:1 'Intel'/'HDA Intel at 0xfdff8000 irq 22'
Mixer name : 'Realtek ALC882'
Components : 'HDA:10ec0882,
Controls : 39
Simple ctrls : 21
CurrentDmesg:
[ 15.669438] usplash:374 freeing invalid memtype fffffffff900000
[ 21.640112] eth0: no IPv6 routers present
Date: Sat Nov 7 19:10:34 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 09/04/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: Infinity P965(-S)
dmi.board.vendor: DFI Inc.
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
affects: | ubuntu → linux (Ubuntu) |
Hi citizen,
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. Typically you'll see something similar to "PM: resume devices took 8.664 seconds" in your dmesg output when this happens. 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.]