[pulseaudio-discuss] [bluez + ofono+ pulseaudio] WARN Event TRB for slot 3 ep 5 with no TDs queued?

[Georg Chini]

On 29.11.2016 14:27, Tanu Kaskinen wrote:
> On Mon, 2016-11-28 at 19:01 +0530, mohammed rilwan wrote:
>> Hi,
>>
>> I am on ubuntu 16.04.
>> playing audio over sco link from android device to ubuntu. PC as headset.
>> Everything works as expected.I can hear the audio through PC speakers.
>> Unfortunately i get below error sometimes and not able to hear the audio.
>> Not sure why and when i get this error. couldnot confirm the reproduction
>> path. Anyone ahs seen this issue and solved this ? Any help much
>> appreciated.
>>
>> version-
>> coex at coex:~$ /usr/local/bin/pulseaudio --version
>> pulseaudio 9.0-113-g058f
>> coex at coex:~$ pacmd --version
>> pacmd 9.0-113-g058f
>> Compiled with libpulse 9.0.0
>> Linked with libpulse 8.0.0
>>
>>
>> error-
>> <good logs until  ofono creates AG, and succesful conenction>
>> <started audio play in android device--some sco conenction whitenoise
>> started, just before the real audio i get this error>
>> ......
>> Nov 28 18:51:56 coex kernel: [10831.352267] xhci_hcd 0000:00:14.0: WARN
>> Event TRB for slot 3 ep 5 with no TDs queued?
>> Nov 28 18:51:56 coex kernel: [10831.353261] xhci_hcd 0000:00:14.0: WARN
>> Event TRB for slot 3 ep 5 with no TDs queued?
>> Nov 28 18:51:56 coex kernel: [10831.354269] xhci_hcd 0000:00:14.0: WARN
>> Event TRB for slot 3 ep 5 with no TDs queued?
>> Nov 28 18:51:56 coex kernel: [10831.355270] xhci_hcd 0000:00:14.0: ERROR
>> Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1
>> Nov 28 18:51:56 coex kernel: [10831.355273] xhci_hcd 0000:00:14.0: Looking
>> for event-dma 000000002acfd0e0 trb-start 000000002acfd060 trb-end
>> 000000002acfd060 seg-start 000000002acfd000 seg-end 000000002acfdff0
>> Nov 28 18:51:56 coex kernel: [10831.356269] xhci_hcd 0000:00:14.0: ERROR
>> Transfer event TRB DMA
> I'm not familiar with these kernel errors. The linux-bluetooth mailing
> list would probably be a better place for this question:
> http://vger.kernel.org/vger-lists.html#linux-bluetooth
>
This looks even further down the stack - the messages are from the USB
3.0 driver. It is probably a 2.0 device so you should better use a 2.0 port
(and the ehci_hcd driver).

I observed issues with 2.0 devices on 3.0 ports.