Bug#531976: marked as done (bluez: Occasionally the kernel freezes while connecting bluetooth mouse)
Your message dated Tue, 1 Sep 2009 19:29:22 +0200
with message-id <20090901172922.GA22894@galadriel.inutil.org>
and subject line Re: bluez: Occasionally the kernel freezes while connecting bluetooth mouse
has caused the Debian Bug report #531976,
regarding bluez: Occasionally the kernel freezes while connecting bluetooth mouse
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact email@example.com
Debian Bug Tracking System
Contact firstname.lastname@example.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <email@example.com>
- Subject: bluez: Occasionally the kernel freezes while connecting bluetooth mouse
- From: George Kiagiadakis <firstname.lastname@example.org>
- Date: Fri, 05 Jun 2009 14:53:04 +0300
- Message-id: <20090605115304.17674.83961.reportbug@localhost>
Justification: breaks the whole system
I have a logitech bluetooth mouse which I connect using hidd --connect $MAC_ADDRESS.
Before I upgrade to bluez 4.40 in unstable, it had always been working fine.
Since I upgraded to bluez 4.40, I am experiencing strange behavior and
occasional kernel freezes.
My usage scenario is this:
First I turn on the mouse and then I run a script on a console, which runs
"sudo hidd --connect $MAC_ADDRESS", to connect the mouse.
When I want to disconnect it, I simply turn off the mouse.
Before the bluez 4.40 upgrade I had no problems with that. Since 4.40 though,
every time I run this script, I first get an error message saying "No route to host"
and then I have to try once again and the mouse connects fine. Sometimes though,
the second time it does not succeed either, and hidd does not return.
After a few seconds, the kernel freezes completely. Keyboard/screen are dead
and I can't ping the machine. Only alt+sysrq+b works, which reboots the machine.
This has happened to me twice, one time with a custom 2.6.27 kernel and the second
time with debian's 2.6.29-2 kernel. The logs don't write anything about it.
Ask me if you need any further information.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bluez depends on:
ii dbus 1.2.14-2 simple interprocess messaging syst
ii libbluetooth3 4.40-2 Library to use the BlueZ Linux Blu
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.14-2 simple interprocess messaging syst
ii libglib2.0-0 2.20.3-1 The GLib library of C routines
ii libnl1 1.1-5 library for dealing with netlink s
ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
ii makedev 2.3.1-88 creates device files in /dev
ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo
ii udev 0.141-1 /dev/ and hotplug management daemo
bluez recommends no packages.
Versions of packages bluez suggests:
ii python-dbus 0.83.0-1 simple interprocess messaging syst
ii python-gobject 2.16.1-1 Python bindings for the GObject li
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: George Kiagiadakis <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: bluez: Occasionally the kernel freezes while connecting bluetooth mouse
- From: Moritz Muehlenhoff <email@example.com>
- Date: Tue, 1 Sep 2009 19:29:22 +0200
- Message-id: <20090901172922.GA22894@galadriel.inutil.org>
- In-reply-to: <firstname.lastname@example.org>
- References: <20090605115304.17674.83961.reportbug@localhost> <email@example.com>
On Sun, Jun 14, 2009 at 02:26:59PM +0300, George Kiagiadakis wrote:
> On Friday 05 of June 2009 14:53:04 George Kiagiadakis wrote:
> > This has happened to me twice, one time with a custom 2.6.27 kernel and the
> > second time with debian's 2.6.29-2 kernel. The logs don't write anything
> > about it. Ask me if you need any further information.
> It seems I was wrong about that. I didn't remember well the situation about
> the 2.6.27 kernel. In fact the freezes started to occur after I upgraded to
> I discovered this by doing some tests during the past week:
> bluez 4.40 + linux 2.6.29 -> freezes
> bluez 3.36 + linux 2.6.29 -> freezes
> bluez 4.40 + linux 2.6.27 -> ok
> bluez 3.36 + linux 2.6.27 -> ok
> bluez 4.40 + linux 2.6.30 -> ok
> I am now running the last combination, a custom 2.6.30 kernel and bluez 4.40
> and I have no other problems except that the mouse doesn't connect
> automatically with the first invocation of hidd (or with bluetooth-applet), but
> I can work this around for now.
> So, I am reassigning this bug to linux-image-2.6.29-2-amd64 (which is the
> kernel that freezes), as this seems to be a kernel bug and will be fixed in
> debian when the kernel packagers package linux 2.6.30 or later.
Marking as fixed in 2.6.30, which is now in unstable and testing.
--- End Message ---