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
The command I tried are:
aplay -D plug:headset /usr/share/sounds/card_shuffle.wav
->The headset activates, but I do not hear the audio and the syslog
keep being flooded until I kill aplay
mplayer -ao alsa:device=headset /usr/share/sounds/card_shuffle.wav
->works with low quality, but the syslog still gets flooded for the
duration of the wav file
Linux distribution: Ubuntu jaunty beta
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.
If you use rsyslog, *I think* this line, placed near the top of rsyslog.conf
file will keep them out of the log at least:
:msg, contains, "hci0 urb" ~
--
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
