USB bluetooth device floods errors to syslog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
My cheap noname bluetooth device floods syslog following data:
[185563.188120] hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
[185563.188124] hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
[185563.188126] hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
[185563.188129] hci_scodata_packet: hci0 SCO packet for unknown connection handle 92
Data goes very rapidly and fills hdd in a few days. Bluetooth itself works perfectly. This same bug was around with Dapper (no.39414) and was fixed then (I suppose, the stick works perfectly in my Dapper machine).
lsusb:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 005: ID 0e5e:6622
Bus 003 Device 001: ID 0000:0000
Same bug is with other instance of this same bluetooth device (I brought two of them) and it is in my other gutsy machine too w/ 0e5e:6622.
Changed in linux: | |
milestone: | none → hardy-alpha-4 |
status: | Triaged → Fix Committed |
Changed in linux-source-2.6.22: | |
status: | Incomplete → Won't Fix |
Can you attach your entire dmesg output after you see the syslog getting flodded with messages? Thanks.