Package: bluez-utils Version: 3.36-1 Severity: normal I have a Logitech Bluetooth WirelessHub, which I use with the Cordless Elite Keyboard and MX900 Mouse [it came as a set]
$ lsusb Bus 002 Device 020: ID 046d:c707 Logitech, Inc. Bluetooth wireless hub Bus 002 Device 015: ID 046d:c703 Logitech, Inc. Elite Keyboard Y-RP20 + Mouse MX900 (Bluetooth) It will work quite happily as a bluetooth HID setup: $ hidd --list 00:07:61:xx:yy:zz Logitech Bluetooth Keyboard [046d:b301] connected 00:07:61:xx:yy:zz Logitech Bluetooth Mouse [046d:b001] connected Occasionally though, the whole lot will reset itself - the hub drops out of HCI mode back into "legacy" HID mode, and presents itself instead as a normal USB HID keyboard, and I lose connection to the mouse. Since I still have the keyboard, I can simply type $ sudo hid2hci and all gets recovered again. dmesg has this to say at the time: usb 2-2.2: USB disconnect, address 17 usb 3-5: reset high speed USB device using ehci_hcd and address 3 usb 2-2.2: new full speed USB device using ohci_hcd and address 18 usb 2-2.2: configuration #1 chosen from 1 choice input: Logitech Bluetooth Mouse as /class/input/input435 input: Logitech Bluetooth Keyboard as /class/input/input436 usb 2-2.2: USB disconnect, address 18 usb 2-2.2: new full speed USB device using ohci_hcd and address 19 usb 2-2.2: configuration #1 chosen from 1 choice input: Logitech Bluetooth Mouse as /class/input/input437 input: Logitech Bluetooth Keyboard as /class/input/input438 usb 2-2.2: USB disconnect, address 19 usb 2-2.2: new full speed USB device using ohci_hcd and address 20 usb 2-2.2: configuration #1 chosen from 1 choice input: Logitech Bluetooth Mouse as /class/input/input439 input: Logitech Bluetooth Keyboard as /class/input/input440 It seems to be slightly uptime-related. This machine's uptime currently sits at $ uptime 15:57:55 up 59 days, 7:56, 7 users, load average: 0.51, 0.29, 0.26 On bootup, it runs quite stably for a few weeks. It's now dropped about 10 times in the last 4 days. I don't quite know whether to blame bluez, my kernel, or even my hardware. Can anyone suggest something I could do to debug this one some more? -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25.nim Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bluez-utils depends on: ii dbus 1.2.1-3 simple interprocess messaging syst ii libbluetooth2 3.36-1 Library to use the BlueZ Linux Blu ii libc6 2.7-13 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-3 simple interprocess messaging syst ii libglib2.0-0 2.16.4-2 The GLib library of C routines ii libusb-0.1-4 2:0.1.12-12 userspace USB programming library ii lsb-base 3.2-19 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-88 creates device files in /dev ii module-init-tools 3.4-1 tools for managing Linux kernel mo ii udev 0.125-5 /dev/ and hotplug management daemo Versions of packages bluez-utils recommends: pn bluez-audio <none> (no description available) pn obex-data-server <none> (no description available) Versions of packages bluez-utils suggests: pn bluez-firmware <none> (no description available) pn bluez-gnome | kdebluetooth <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
