From nobody Mon Apr 18 19:01:40 2022 X-Original-To: freebsd-usb@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0F9AE11D288A for ; Mon, 18 Apr 2022 19:01:43 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Khx9y2JRvz3vSf for ; Mon, 18 Apr 2022 19:01:42 +0000 (UTC) (envelope-from hps@selasky.org) Received: from [10.36.2.165] (unknown [176.74.213.87]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 27CF5260509; Mon, 18 Apr 2022 21:01:41 +0200 (CEST) Message-ID: <61bc4594-f2d3-17c4-42b5-0297ffd78fa3@selasky.org> Date: Mon, 18 Apr 2022 21:01:40 +0200 List-Id: FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-usb List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: xhci data toggle out of sync Content-Language: en-US To: Mahesh Vardhamanaiah , "freebsd-usb@freebsd.org" Cc: Steve Kiernan , Justin Hibbits , Kumara N Babu , Kamal Prasad References: From: Hans Petter Selasky In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Khx9y2JRvz3vSf X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of hps@selasky.org designates 88.99.82.50 as permitted sender) smtp.mailfrom=hps@selasky.org X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net:c]; MID_RHS_MATCH_FROM(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.70)[-0.700]; MLMMJ_DEST(0.00)[freebsd-usb]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.99.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 4/18/22 18:44, Mahesh Vardhamanaiah wrote: > Hi all, > > > Need your help regarding an urgent issue where we are observing an issue with Freebsd stable/12. The data toggles for BOT endpoint > (DATA0/DATA1) are out of sync with respect to EP and the system experiences the READ(10) errors. The READ(10) error recovers within > couple of retries most of the times but few cases we have observed that the read retries gets exhausted and system moves to unusable state > (continuous g_vfs_done() errors) . We are using Junos but the xhci driver etc.. are all pristine stable 12 drivers no Juniper specific changes. > This issue was never observed with Linux kernel 5.4.2 on the same HW suspecting if it's a xhci driver error recovery issue. > > Errors Seen on console > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 28 cf 28 00 00 40 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 > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 28 cf 28 00 00 40 00 > > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > > (da0:umass-sim0:0:0:0): Retrying command, 2 more tries remain > > FreeBSD/arm (Amnesiac) (ttyu0) > > login: > > > Please let us know is there a place holder to upload the traces and provide a link here ? > Thanks, > Mahesh Hi Mahesh, Do you have wire recording using Ellisys or the Beagle, showing which side is at fault of the data toggle error? Is this issue reproducible using the EHCI HC driver? Is the device connected at USB 3.x or USB 2.0 speed? --HPS