Re: Bluetooth HID devices not getting properly removed

[David Woodhouse]

On Wed, 2009-06-24 at 13:11 +0200, Thomas BÃchler wrote:
> 
> KERNEL[1245834012.631443] remove 
> /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:11 
> (bluetooth)
> KERNEL[1245834012.632668] remove   /hci0:11/input12/mouse2 (input)
> KERNEL[1245834012.641797] remove   /hci0:11/input12/event8 (input)
> KERNEL[1245834012.655447] remove   /hci0:11/input12 (input)
> KERNEL[1245834012.655502] remove   /hci0:11/0005:046D:B002.0004 (hid)
> 
> See how the device path of the removed input devices is truncated? When 
> I do the same with a USB mouse, a full device path is returned each time.
> 
> All of this results in hal not removing its logical input device, which 
> means the number of (non-existent) mice in the hal device tree increases 
> whenever I disable and re-enable my mouse.
> 
> So where do I put this bug? Linux? Bluez? Udev? Hal? My guess is Linux, 
> as these device paths come from Linux originally and are in fact 
> inconsistent. This is all tested on 2.6.30, I have no idea if it was the 
> case on older kernels.

It's in the BlueZ HID code. I pointed it out to Marcel a few months ago
-- it happens when the ACL connection is killed (orphaning the HID
device in sysfs), and the HID device is only killed _later_, so the path
on the removal is wrong.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@xxxxxxxxx                              Intel Corporation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/