I think filtering these messages would be possible using e.g. the syslog-ng logging daemon. But just filtering the log is no clean solution, as this would spend lots of CPU cycles on generating and filtering syslog messages.
As the upstream bug I filed (http://bugzilla.kernel.org/show_bug.cgi?id=6833) was fixed by just adding one line with the device's ID into the drivers/bluetooth/hci_usb.c source file, you could add the fix for your device and recompile the module.
As there seem to be lots of different devices affected, upstream/ubuntu/whoever could maintain an ever-growing list of IDs in the C source file, or upstream/ubuntu/whoever could maybe provide some means to extend such a blacklist without the need for recompilation of the module, e.g. by a /etc/modprobe.d/ or /sys/module/usbcore/ config file.
I think filtering these messages would be possible using e.g. the syslog-ng logging daemon. But just filtering the log is no clean solution, as this would spend lots of CPU cycles on generating and filtering syslog messages.
As the upstream bug I filed (http:// bugzilla. kernel. org/show_ bug.cgi? id=6833) was fixed by just adding one line with the device's ID into the drivers/ bluetooth/ hci_usb. c source file, you could add the fix for your device and recompile the module.
As there seem to be lots of different devices affected, upstream/ ubuntu/ whoever could maintain an ever-growing list of IDs in the C source file, or upstream/ ubuntu/ whoever could maybe provide some means to extend such a blacklist without the need for recompilation of the module, e.g. by a /etc/modprobe.d/ or /sys/module/ usbcore/ config file.