Date: Tue, 12 Apr 2022 15:56:12 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: mahesh mv <maheshm_v@yahoo.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@FreeBSD.org> Subject: Re: xhci USB transaction error and subsequent recovery mechanism on Freebsd stable/12 Message-ID: <202204122256.23CMuCrQ078746@gndrsh.dnsmgr.net> In-Reply-To: <202204122147.23CLlYjE014614@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> -------- > mahesh mv writes: > > > READ(10) errors. The READ(10) error recovers with in couple of retries most > > of the times but few cases we have observed that the read retries gets exhausted and [...] > ... [ large amount of good information removed ] ... > Poul-Henning > > PS: "completed with an error" without any details about the error is not very helpful for debugging... One of the very reasons that I keep my "disk drive debugging" work all on a 5.4p8 system is that when things transitioned to CAM most of the useful low level error messages disappeared as the CAM layer doesn't output them. IIRC we no longer get the LBA when a read defect is reported, or we get it, but it is in the cryptic form of a dumped CCB. It would be wonderful to get that "funtionality" back. > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202204122256.23CMuCrQ078746>