Re: Flood of "urb ... submission failed" with bluetooth headset

[Ludovico Cavedon <ludovico.cavedon@gmail.com>]

On Mon, Mar 30, 2009 at 3:31 AM, jayjwa <jayjwa@atr2.ath.cx> wrote:
> On Sun, 29 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?

Thanks,
Ludovico