kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #178419
[Bug 513642] Re: Kernel panic when a Motorola S305 Stereo headset requests connection
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/513642
Title:
Kernel panic when a Motorola S305 Stereo headset requests connection
Status in bluez package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio-module-bluetooth
Recently we found an almost 100% reproducible issue when using
Motorola S305 stereo headset and Ubuntu 9.10. The Ubuntu system has
auto-update turned on and keeps up with the latest stable release. See the package list at appendix #1 at the end.
The procedure to reproduce the issue is:
1. Pair the S305 headset from Ubuntu using the bluetooth icon in the
task bar, "Set up new device..."
2. In the "Bluetooth Preferences" screen, hit "Remove" button to
remove the paired S305.
3. Power off and then power on S305.
4. The S305 will try to connect and get a negative link key reply.
You'll see the PIN input dialog flash away quickly because after the
negative reply, the LMP link is detached.
5. After step 4, the S305 willl request again and this time you'll be
given the dialog to input the PIN. Put '0000' and you'll see the
desktop frozen. Keyboard, mouse, network ... everything is down.
With step 5, I don't expect the audio is correctly setup as there
should be a couple of more configuration to do. However, the
unexpected thing is that the system hang up. I've reported the issue
in linux-bluetooth mail list and would like to see if the issue can be
caused by some process crash in user space. I managed to find the log
of Appendix #2. My system still has so the panic backtrace is not
available , however I attached a picture taken by my mobile.
For those who are interested, I have the hcidump log and my initial
analysis here:
http://marc.info/?l=linux-bluetooth&m=126415557115779&w=2
--------------------------------------------
Appendix #1
lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10
uname -a
Linux njred148 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 16:20:31 UTC 2009 i686 GNU/Linux
> ii pulseaudio-module-bluetooth 1:0.9.19-0ubuntu4
> Bluetooth module for PulseAudio sound server
> ii bluez 4.51-0ubuntu2
> Bluetooth tools and daemons
> ii bluez-alsa 4.51-0ubuntu2
> Bluetooth audio support
> ii bluez-compat 4.51-0ubuntu2
> BlueZ 3.x compatibility binaries
> ii bluez-cups 4.51-0ubuntu2
> Bluetooth printer driver for CUPS
> rc bluez-gnome 1.8-0ubuntu5
> Bluetooth utilities for GNOME
> ii bluez-gstreamer 4.51-0ubuntu2
> Bluetooth GStreamer support
> ii bluez-hcidump 1.42-1build1
> Analyses Bluetooth HCI packets
> ii bluez-utils 4.51-0ubuntu2
> Transitional package
>
--------------------------------------------
Appendix 2
Jan 28 07:35:05 njred148 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="881" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'.
Jan 28 11:32:18 njred148 pulseaudio[22235]: pid.c: Stale PID file, overwriting.
Jan 28 11:33:58 njred148 pulseaudio[22235]: module-bluetooth-device.c:
Default profile not connected, selecting off profile
Jan 28 11:40:33 njred148 pulseaudio[22219]: module-bluetooth-device.c:
Default profile not connected, selecting off profile
Jan 28 12:30:40 njred148 Cleanup, done. Exitting...
Jan 28 12:31:51 njred148 pulseaudio[23458]: pid.c: Stale PID file, overwriting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/513642/+subscriptions