Date: Thu, 2 Feb 2006 10:51:13 -0800 (PST) From: Matthew Jacob <mj@feral.com> To: Nate Lawson <nate@root.org> Cc: "Kenneth D. Merry" <ken@freebsd.org>, freebsd-scsi@freebsd.org, Matthew Jacob <mj@feral.com>, Florent Thoumie <flz@xbsd.org> Subject: Re: cvs commit: src/sys/cam/scsi scsi_da.c src/sys/dev/usb umass.c usbdevs Message-ID: <20060202104606.W98511@ns1.feral.com> In-Reply-To: <43E252EC.1050803@root.org> References: <20060130202806.DCC7916A4CA@hub.freebsd.org> <43DEF43A.6090804@root.org> <20060130213338.H79194@ns1.feral.com> <200601311239.10248.flz@xbsd.org> <43E06B06.80405@root.org> <20060202175041.GA92109@nargothrond.kdm.org> <20060202095828.D97756@ns1.feral.com> <43E252EC.1050803@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > There are 3 kinds of devices: > > * SYNC CACHE works > * SYNC CACHE reports an error, but continues working > * SYNC CACHE just hangs, no error > * SYNC CACHE reports and error correctly, but then all subsequent commands > time out > > We're talking about the 4th case and some versions with the 3rd case, if it > was possible to detect them without hanging (i.e. mode sense works and WCE > properly reported). The problem is that we have a significant SYNC CACHE > quirk proliferation problem. > > A few years ago, we had a 6-byte command quirk proliferation problem, until I > modified USB and Firewire SIMs to report "not 6-byte capable". I then was > able to remove dozens of quirks and we seem to have solved that problem. I'm > recommending we do the same thing with SYNC CACHE now. > Ah- I'm all for that as a reasonable solution as long as the default doesn't cause WCE off in a regular disk drive to be interpreted as "does not support".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060202104606.W98511>