Kernel became unstable-Ubuntu 9.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
sorry, I'm a noob and have no clue what to say. My computer had been on for 4-5 days and then apport(?)
said there was a problem and I might have to re-start. It didn't restart and seems to be ok. This is a week old
clean install, dual booting with Windows 7 Ultimate. I have not done ANY updates as of yet. The update manager
is pestering me, but I have reluctant to update as it seemed like almost everytime I updated 9.04, something
went wrong. Programs stopped working after updates, and huge hang times with processors maxed out.
When I used the 'ubuntu-bug -p linux' command in terminal, the kernel error re-occured.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: ICE1724 [ICEnsemble ICE1724], device 0: ICE1724 [ICE1724]
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 'ICE1724'
Mixer name : 'ICEnsemble VT1616i'
Components : 'AC97a:49434552'
Controls : 54
Simple ctrls : 35
Date: Tue Nov 17 08:19:45 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: [173737.440126] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 09/08/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: P4i65G
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P4i65G
dmi.product.
Hi Sonkei,
After examining your attached OopsText.txt file, the warning reported there 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. It's only a warning and there should be no other ill effects as a result. A patch to prevent this warning has been applied via bug 464552. So if you went ahead and apply your updates, this should go away. For now, I'm marking this as a duplicate to bug 464552. Thanks!