Ubuntu
linux package

Kernel became unstable-Ubuntu 9.10

Bug #484455 reported by Sonkei on 2009-11-17

This bug report is a duplicate of: Bug #464552: suspend_test_finish warning triggers too easily, increase timeout to match mainline times. Edit Remove

This bug affects 1 person

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/controlC0: sonkei 5680 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'ICE1724'/'ICEnsemble ICE1724 at 0xbc00, irq 23'
   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=UUID=0f2af373-6fa5-449e-9430-c746250b033a
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: fglrx
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=431b1e97-c890-4c8d-8136-82ff1a622736 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
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:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/08/2006:svn:pnP4i65G:pvr1.00:rvn:rnP4i65G:rvr1.00:
dmi.product.name: P4i65G
dmi.product.version: 1.00

Tags:

Revision history for this message

Sonkei (piece-of-your-action) wrote on 2009-11-17:

AlsaDevices.txt Edit (463 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (283 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (37.5 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (7.6 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.txt Edit (630 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (18.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (722 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (10.5 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (511 bytes, text/plain; charset="utf-8")
OopsText.txt Edit (1.9 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (755 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.3 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (112 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (84.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (182.2 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (44.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2009-11-22:

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!