Re: xhci data toggle out of sync

Hi Mahesh,

I don't see any "Could not XXX" messages, so then the XHCI part should 
be fine, and if you verify using Beagle, I expect there to be no more 
data toggle mismatches, but I may be wrong.

--HPS

On 4/20/22 19:48, Mahesh Vardhamanaiah wrote:
> Please find the few of the debug logs added in around the time problem is seen.
> 
> 
> Tue Apr 19 23:37status = 0x6, xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1 status = 0x6, xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1
> 
> FreeBSD/arm (Amnesiac) (ttyu0)
> 
> login: err = 0x12
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1 err = 0x12 xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1 err = 0x12 xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> 
> (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 d7 79 a8 00 00 80 00
> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain
> xhci_configure_reset_endpoint() called epno = 2, ep state = 3, drop = 1
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1 status = 0x6, xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 0
> xhci_configure_reset_endpoint() called epno = 3, ep state = 3, drop = 1