BUG: soft lockup - CPU#0 stuck for 61s! [bluetoothd:10637]

[C de-Avillez]

probable dup, but I would rather check. Happened after activating bluetooth; /usr/sbin/bluetooth was in a hard spin loop, 100% of one core, could not be stopped. Eventually I powered the system down & rebooted.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Mon May 11 21:27:52 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=76b93618-ec1b-4f53-9e63-4c5350d12a99
MachineType: Dell Inc. Inspiron 1721
Package: linux-image-2.6.30-4-generic 2.6.30-4.5
ProcCmdLine: root=/dev/mapper/sys-root ro acpi_osi=Linux crashkernel=384M-2G:64M@16M,2G-:128M@16M single
ProcVersionSignature: Ubuntu 2.6.30-4.5-generic
RelatedPackageVersions:

SourcePackage: linux
Tags: kernel-oops
Title: BUG: soft lockup - CPU#0 stuck for 61s! [bluetoothd:10637]

[borrell (borrell)]

I have just had the same issue, happened when I turned the bluetooth device on my laptop (MSI Wind U100) off.

Attached is a syslog extract. I was unable to kill bluetoothd with kill or killall, I needed to hard power off and reboot

[Jeremy Foshee (jeremyfoshee)]

Hi Carlos,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 375244

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[C de-Avillez (hggdh2)]

I have not had any new instances of this bug. As far as I am concerned, it can be closed.