Hi, I am new to this list and hopefully someone can help me with my problem:On my Debian system with kernel 2.6.30 and extra USB-verbosity activated I have 3 Bluetooth-USB-adapters (CSR class 1) each connected to a ProPlantronics-Headset over Pulseaudio 0.9.19 and bluez 4.59. Because my computer only has 3 USB-slots and I also have an USB-soundcard, an USB-GSM-module (I phone with all 3 bt-headsets at once) and an USB-keyboard, I use 1 or 2 USB-hubs (I tried a 4-port and 2 7-port hubs all from D-Link). My problem is that the Bluetooth-USB-adapters sometimes out of nowhere disconnect and reconnect again (of course the bt-headset looses the connection and has to be connected again). I attached 3 logs of the USB-disconnects (usb1.log is the one happening most of the time, usb3.log I just saw once). The disconnects occur sometimes once or twince in an hour, sometimes just once in a day (I ran tests over the holidays with my computer running the whole time and build an app that reconnects the headsets after something like thins happens). Just one adapter disconnects at a time, but it occurs on all of them (I also exchanged all of the adapters). I also tried the same system-image on 2 other computers, so I don't think this is a hardware problem. After seaching the web I found out that some people had similar problems with USB-"streaming"-devices (like webcams, soundcards, datacards, etc.) when they used them with an USB-hub. So I tried it out and connected 2 bt-adapters directly to my computer and just one to the USB-hub and the USB-disconnects got significantly fewer (roughly one every 3 days - this would be OK, but still the USB-disconnect sometimes occured just shortly after startup and then not anymore for a few days, sometimes it occured after 2 days, so it seems to be completely random). Another disadvantage is that this is limiting the positioning of the bt-adapters so that I have bt-quality-issues. Another issue is that there is another form of disconnect occuring on the headsets (I call it BT-disconnects): there are no unusual messages in the syslog before the disconnect, the first entry is from bluetoothd: "Audio connection got disconnected" (my app also reconnects the headsets after this). I also looked at the hcidump from bluetooth and when this disconnect occurs it always says "Reason: Connection Timeout", but when an USB-disconnect happens it says something like "Device down" or "Device removed" (I forgot to save a log from this, will add it if wished). I think the BT-disconnects are related to interferences from the adapters disturbing each other or some WLANs around (when I turn off mine it gets less). But there are also a few analogies: There is roughly the same amount of BT-disconnects like USB-disconnects and after most of the BT-disconnects several minutes or hours later there is an USB-disconnect on the same adapter the headset with the BT-disconnect was connected (and reconnected) to. Does anyone have any ideas that could help me or at least improve the situation?
Thanks a lot and best regards, Peter
Attachment:
usb1.log
Description: Binary data
Attachment:
usb2.log
Description: Binary data
Attachment:
usb3.log
Description: Binary data
