So there were no help from new kernel in Hardy. I found a suitable fix
for this: In vanilla kernel source changing instance in file
drivers/bluetooth/hci_usb.c does the trick.
Under comment
/* RTX Telecom based adapters with buggy SCO support */
A new line is added:
{ USB_DEVICE
** Attachment added: "version.log"
http://launchpadlibrarian.net/10899358/version.log
--
USB bluetooth device floods errors to syslog
https://bugs.launchpad.net/bugs/152689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/10899351/uname-a.log
--
USB bluetooth device floods errors to syslog
https://bugs.launchpad.net/bugs/152689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/10899350/lspci-vvnn.log
--
USB bluetooth device floods errors to syslog
https://bugs.launchpad.net/bugs/152689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/10899349/dmesg.log
--
USB bluetooth device floods errors to syslog
https://bugs.launchpad.net/bugs/152689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
Sorry I am a newbie with this bug reporting system. I try to provide all
required information. dmesg.0 is generated by cat /var/log/dmesg.0
because original dmesg has its boot procedure overwritten because of
errors from bluetooth dongle.
** Attachment added: "dmesg.0.log"
http://launchpadlibra
** Attachment added: "dmesg"
http://launchpadlibrarian.net/10894336/dmesg
--
USB bluetooth device floods errors to syslog
https://bugs.launchpad.net/bugs/152689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
Public bug reported:
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
