On Tue, 31 Mar 2009, Ludovico Cavedon wrote:
When I try to play some audio on the my bluetooth headset, my syslog
is flooded with messages like
btusb_send_frame: hci0 urb ffff8800624bd800 submission failed
Same thing happen here, too:
btusb_send_frame: hci0 urb d093f200 submission failed
btusb_send_frame: hci0 urb d093f400 submission failed
btusb_send_frame: hci0 urb d093fa00 submission failed
...
btusb_send_frame: hci0 urb d093fc00 submission failed
btusb_send_frame: hci0 urb d093fe00 submission failed
btusb_send_frame: hci0 urb d7271e00 submission failed
btusb_send_frame: hci0 urb d7271400 submission failed
Seems to be related to the new btusb kernel module, because it didn't used
to happen with hci_usb kmod. Since the address keeps changing, syslog
rate-limiting can't remove them as dups . Maybe one out of the flurry of
patches we see on this list will address this soon.
Actually I noticed I only get a burst of ~350 at the beginning of the
connection, all with the same number, then no more.
Is it normal?
Not sure. Maybe we have two seperate, but related in some way, issues.
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
