From owner-freebsd-scsi Tue Jan 14 5:48:43 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DECF37B401 for ; Tue, 14 Jan 2003 05:48:42 -0800 (PST) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA14D43F65 for ; Tue, 14 Jan 2003 05:48:41 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by aslan.scsiguy.com (8.12.6/8.12.5) with ESMTP id h0EDmbps008145; Tue, 14 Jan 2003 06:48:37 -0700 (MST) (envelope-from gibbs@scsiguy.com) Date: Tue, 14 Jan 2003 06:48:37 -0700 From: "Justin T. Gibbs" To: Joerg Wunsch Cc: freebsd-scsi@freebsd.org Subject: Re: quirk candidate: SEAGATE ST52160N Message-ID: <808290000.1042552117@aslan.scsiguy.com> In-Reply-To: <20030114143505.A12331@uriah.heep.sax.de> References: <20030113220055.D50550@uriah.heep.sax.de> <147830000.1042501904@aslan.btc.adaptec.com> <20030114074853.A71485@uriah.heep.sax.de> <774150000.1042549034@aslan.scsiguy.com> <20030114143505.A12331@uriah.heep.sax.de> X-Mailer: Mulberry/3.0.0b10 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > As Justin T. Gibbs wrote: > >> >> It would be interesting to know the full content of the sense data. >> > >> > uncle# camcontrol cmd da1 -v -c '35 0 0 0 0 0 0 0 0 0' >> > camcontrol: error sending command >> > (pass1:ahc0:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 >> > (pass1:ahc0:0:3:0): CAM Status: SCSI Status Error >> > (pass1:ahc0:0:3:0): SCSI Status: Check Condition >> > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:20,0 >> > (pass1:ahc0:0:3:0): Invalid command operation code: Command byte 0 is >> > invalid >> >> So your disk doesn't always butcher byte zero of the sense data? > > Isn't byte 0 the `35' for the command? I. e., it is complaining > that it doesn't understand the SYNCHRONIZE CACHE cmd at all. Byte 0 of the sense data. In your first emails, the kernel was complaining about funny sense error codes which is why it never even looked at the ASC/ASCQ. The strange thing is that the bogus error code varied. I wonder if we are somehow corrupting the sense data. > SYNCHRONIZE CACHE is marked optional in the standard, > i thought we'd automatically detect the non-support of this > command by a target, and silently ignore it? If your device is returning proper sense data for this ILLEGAL REQUEST, then it should be silently filtered by scsi_da.c. The quirks in there *shouldn't be needed*, but for some reason the filter doesn't always work. It would be nice to know why it doesn't work. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message