Date: Wed, 4 Oct 2000 09:10:02 -0700 (PDT) From: Justin Gibbs <gibbs@plutotech.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/21752: Infortrend IFT-3102 doesn't like SCSI Cache Sync Message-ID: <200010041610.JAA04682@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/21752; it has been noted by GNATS. From: Justin Gibbs <gibbs@plutotech.com> To: nickc@corp.firstindustrial.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/21752: Infortrend IFT-3102 doesn't like SCSI Cache Sync Date: Wed, 4 Oct 2000 10:03:18 -0600 (MDT) > >Synopsis: Infortrend IFT-3102 doesn't like SCSI Cache Sync > FreeBSD 3.x and 4.x are setup to send SCSI CACHE_SYNC commands > to SCSI disk drives unless they are listed in the scsi_da.c quirk > table as not supporting this. The IFT-3102 doesn't accept this > command and as a result a kernel error message is seen at shutdown. > I haven't yet experienced a operational problem under 4.1-STABLE > and greater as a result. But this problem did cause 3.5-RELEASE > to crash during the post install reboot. I don't know why 3.5R would crash because the command failed, but so long as the device does not die due to the sync cache command, I would rather not place an entry into the quirk table. Unfortunately, there are several entries (perhaps all but those for MO devices) in the quirk table that shouldn't need to be there. I am still confused as to why the system prints any error at all. The code in both dashutdown and daclose is supposed to prevent the error from being reported if the device does not support the command. Perhaps you could spend some time instrumenting the "error avoidance" code to determine exactly why it doesn't work. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010041610.JAA04682>