RE: xhci data toggle out of sync

Hi  HPS,
 
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

Thanks,
Mahesh


Juniper Business Use Only

-----Original Message-----
From: Mahesh Vardhamanaiah
Sent: Wednesday, April 20, 2022 5:37 PM
To: Hans Petter Selasky <hps@selasky.org>; Kamal Prasad <krprasad@juniper.net>; freebsd-usb@freebsd.org
Cc: Steve Kiernan <stevek@juniper.net>; Justin Hibbits <jhibbits@juniper.net>; Kumara N Babu <bkumara@juniper.net>; Kristof Provost <kp@FreeBSD.org>; Bjoern A. Zeeb <bz@FreeBSD.org>
Subject: RE: xhci data toggle out of sync

Hi HPS,

Please find the patch used and kernel booted.

root@:RE:0% uname -a
FreeBSD  JNPR-12.1-20220420.074305_mahes FreeBSD JNPR-12.1-20220420.074305_maheshmv_stable_12 #4 r356482+ba50dcb8643(stable/12)-dirty: Wed Apr 20 00:47:17 PDT 2022     maheshmv@svl-bsdx-02:/b/maheshmv/usb_issue/obj/arm64/juniper/kernels/JNPR-ARM64-WIT/kernel  arm64

root@:RE:0% grep -a MMV ./packages/db/os-kernel-wit-arm64-64-20220420.074305_maheshmv_stable_12/boot/kernel
MMV Could not drop endpoint %u at slot %u err %u.
MMV Could not configure endpoint %u at slot %u err %u.
MMV Could not drop endpoint %u at slot %u err %u.
MMV Could not configure endpoint %u at slot %u err %u.

Is the fix like we get error for the Data transaction and report the error. Later we detect that EP is error and we reconfigured it ?

Thanks,
Mahesh


Juniper Business Use Only

-----Original Message-----
From: Hans Petter Selasky <hps@selasky.org>
Sent: Wednesday, April 20, 2022 5:20 PM
To: Mahesh Vardhamanaiah <maheshmv@juniper.net>; Kamal Prasad <krprasad@juniper.net>; freebsd-usb@freebsd.org
Cc: Steve Kiernan <stevek@juniper.net>; Justin Hibbits <jhibbits@juniper.net>; Kumara N Babu <bkumara@juniper.net>; Kristof Provost <kp@FreeBSD.org>; Bjoern A. Zeeb <bz@FreeBSD.org>
Subject: Re: xhci data toggle out of sync

[External Email. Be cautious of content]


On 4/20/22 12:59, Mahesh Vardhamanaiah wrote:
> Hi HPS,
>
> Still no luck. I had added device_prints if the configure EP gets invoked and I don’t see them either during the error.
>
> login: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 aa f2 68 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
>
>
> Thanks,
> Mahesh

Hi Mahesh,

Can you send me back the full patch you are using for FreeBSD-12?

You are sure the code actually got built and installed?

I don't expect the "READ(10) error to go away", but it should recover more quikly, if I'm not mistaken, just to be clear.

--HPS