Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25779 - [linux] Kernel Panic when using bluetooth

Attached to Project: Arch Linux
Opened by Thiago Silva (thisab) - Friday, 26 August 2011, 21:47 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 23 May 2012, 13:45 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

When I start the bluetoothd service, run blueman and try to configure a bluetooth device the screen blanks (sometimes the screen corrupts) . No answer in the terminal. Sometimes I can use the SysRq, sometimes Caps+Scroll blinks and its completely dead.

Some times it can jump to console, but a message in dmesg asks to reboot the system.

I'm attaching the messages from the log below, along with my config_x86_64


Additional info:
kernel 3.0.3
extra/bluez 4.96-1
extra/gnome-bluetooth 3.0.1-1
community/blueman 1.21-7
extra/nvidia 280.13

Steps to reproduce:

Put a usb bluetooth dongle
start the bluetoothd service (blueman starts)
configure a bluetooth device
it will create a random pin
click next

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 23 May 2012, 13:45 GMT
Reason for closing:  No response
Comment by Thiago Silva (thisab) - Friday, 26 August 2011, 22:38 GMT
I was also able to reproduce the problem with another computer (Vostro 1400) with different hardware, but one thing in common: nvidia card using the binary blob

I'm also re-attaching the files.
   config.x86_64 (81.1 KiB)
   noconsole.log (51.7 KiB)
   rebootNeeded.log (41.8 KiB)
Comment by Thiago Silva (thisab) - Saturday, 27 August 2011, 14:20 GMT
I've removed the nvidia, ath5k and other modules to be sure they are not interfering. And they were not.

I'm attaching yet another log, but this time the error without those modules.
   mandar.log (38.5 KiB)
Comment by Thiago Silva (thisab) - Wednesday, 02 November 2011, 03:03 GMT
The problem still persists with linux 3.0.7 and blueman 1.2.3
Comment by Juan Donadio (LoKi) - Thursday, 17 November 2011, 01:14 GMT
I have the same (or similar) problem. I plug my bluetooth usb adapter,turn on the service with "/etc/rc.d/bluetooth start", then I run "hcitool cc XX:XX:XX:XX:XX:XX" (where XX are the MAC address of my cellphone bluetooth device) and the X window systems collapse and the entire machine freezes. Same thing happens with bluedevil from the KDE GUI: I found my device, I click on next and entire machine freezes. I did not found any kind of data in the kernel.log.
I have linux 3.1.1-1, bluedevil 1.2.2-1 and bluez 4.96-1 on a AMD64 machine. Thanks for help and excuse my poor english.
Comment by Tobias Powalowski (tpowa) - Wednesday, 22 February 2012, 16:20 GMT
Any update on this? This is most likely an upstream issue.
Comment by Evangelos Foutras (foutrelis) - Thursday, 08 March 2012, 17:12 GMT
I agree that it's most likely an upstream issue.

I received a USB bluetooth adapter yesterday and I almost always get kernel panics when it's plugged in for a few minutes.

Happens on both i686 and x86_64, but it works fine on Ubuntu 10.04.4 (Linux 2.6.32) and Windows 7.
Comment by Tobias Powalowski (tpowa) - Saturday, 28 April 2012, 08:19 GMT
status on 3.3 kernel?

Loading...