BUG: scheduling while atomic: sirq-tasklet/0/10/0x00000002, CPU#0

[vikarama]

I get this error often on my notebook running Jaunty 64-bit, over a period of time then Jaunty freezes.

My notebook is a Compaq V6211AU model having AMD - Turion64 processors.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
CurrentDmesg:
 [ 54.380691] eth2: no link during initialization.
 [ 54.381570] ADDRCONF(NETDEV_UP): eth2: link is not ready
 [ 56.031007] eth3: no IPv6 routers present
DistroRelease: Ubuntu 9.04
Failure: oops
HibernationDevice: RESUME=UUID=95944e22-8a05-47f2-b8fd-d44b8fe481a2
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
MachineType: Hewlett-Packard Presario V6000 (RL773PA#ACJ)
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=af0b2374-9cf2-4440-a7ed-1ea621977d31 ro quiet splash noapic
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux
Tags: kernel-oops
Title: BUG: scheduling while atomic: sirq-tasklet/0/10/0x00000002, CPU#0

[mateolan (mateolan)]

I get the same error with Jaunty on AMD64 on Acer Ferrari 1004WTMi

[ShPioN (islom)]

Got the same error after updating from 9.04 to 9.10. Attaching my dmesg, I hope that it will help.

[^_Pepe_^ (jose-angel-fernandez-freire)]

Hi all,

Please, can you try again with last kernel version 2.6.32 placed : http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32/

Thanks in advance

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]