Bug#690767: [wheezy] blueteeth adaptor cause kernel crash
Hi Jonathan,
On Wed, Oct 17, 2012 at 12:36:54PM -0700, Jonathan Nieder wrote:
> Hi Fermat,
>
> fermat wrote:
>
> > 1. plug in the bluetooth adaptor
> > 2. start to connect my phone to computer throw bluetooth
> [...]
> > The kernel crashs.
>
> Is this reproducible? How hard is the crash --- do the caps lock and
> magic sysrq keys work? does ctrl-alt-delete reboot? can you access
> the machine remotely, e.g. using ssh?
>
Yes, it can be easily reproduced, and I just prduced it two times.
It is ok to plug in the adaptor, but when I send files to my phone
through bluetooth, the screen frozes. capslock, magic sysrq and
ctrl-alt-delete all don't works. What's more, several seconds later, the
power of the keyboard get down, and then several seconds later, the
power of the mouse get down again.
> Is this a regression? Have you tried any other kernel versions, and
> if so, how did they behave?
>
I tried kernel 2.6.32-5-amd64, that kernel didn't break down, and I can
send file from computer to my phone, but sending files from phone to
computer failed.
> Do you have a log of the crash? A serial console[1] or netconsole[2]
> can be a good way to get one if nothing survives on-disk or on-screen
> (a photograph is fine).
>
I tried to get the log. When I plug off the bluetooth adaptor and then
plug in it, three messages appear on dmesg(1) output. these are the
corresponding messages in /var/log/messages
Oct 18 08:54:28 debian kernel: [ 473.567217] usb 2-1.5: new full-speed
USB device number 4 using ehci_hcd
Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device
found, idVendor=0a12, idProduct=0001
Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
After the crash, I rebooted my computer and run
# cd /var/log; grep 473.66 -R .
then I got
# cd /var/log; grep 473.66 -R .
./kern.log:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New
USB device found, idVendor=0a12, idProduct=0001
./kern.log:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
./syslog:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New
USB device found, idVendor=0a12, idProduct=0001
./syslog:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
./messages:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New
USB device found, idVendor=0a12, idProduct=0001
./messages:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New
USB device strings: Mfr=0, Product=0, SerialNumber=0
I checked these three files, and only "syslog" contains messages that
are after my pluging in the adaptor and before the reboot.
## related messages in /var/log/syslog
Oct 18 08:54:28 debian kernel: [ 473.567217] usb 2-1.5: new full-speed
USB device number 4 using ehci_hcd
Oct 18 08:54:28 debian bluetoothd[2614]: HCI dev 0 registered
Oct 18 08:54:28 debian bluetoothd[2614]: Listening for HCI events on
hci0
Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device
found, idVendor=0a12, idProduct=0001
Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Oct 18 08:54:28 debian bluetoothd[2614]: HCI dev 0 up
Oct 18 08:54:28 debian bluetoothd[2614]: Proximity GATT Reporter Driver:
Operation not permitted (1)
Oct 18 08:54:28 debian bluetoothd[2614]: input-headset driver probe
failed for device 54:F3:DE:69:66:01
Oct 18 08:54:28 debian bluetoothd[2614]: input-headset driver probe
failed for device D8:71:57:64:5D:FD
Oct 18 08:54:28 debian bluetoothd[2614]: Unable to load keys to
adapter_ops: Function not implemented (38)
Oct 18 08:54:28 debian bluetoothd[2614]: Adapter /org/bluez/2614/hci0
has been enabled
Oct 18 08:55:01 debian /USR/SBIN/CRON[5217]: (root) CMD
(/etc/init.d/apf-firewall stop >> /dev/null 2>&1)
Oct 18 08:55:01 debian /USR/SBIN/CRON[5218]: (fermat) CMD
(/usr/bin/notify-send foo bar)
Oct 18 08:55:17 debian obex-data-server: sdp_extract_seqtype: Unexpected
end of packet
Oct 18 09:01:02 debian kernel: imklog 5.8.11, log source = /proc/kmsg
started.
Oct 18 09:01:02 debian rsyslogd: [origin software="rsyslogd"
swVersion="5.8.11" x-pid="2273" x-info="http://www.rsyslog.com";] start
Oct 18 09:01:02 debian kernel: [ 0.000000] Initializing cgroup subsys
cpuset
## messages end
The former times kernel crashes, I have ever been able to see kernel
messages on the screen, the these two times the screen just freeze, no
messages appear.
> Thanks and hope that helps,
> Jonathan
>
> [1] http://www.kernel.org/doc/Documentation/serial-console.txt
> [2] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
Reply to: