From owner-freebsd-scsi Mon Dec 30 14:14:45 2002 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 520B637B401 for ; Mon, 30 Dec 2002 14:14:44 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB4E43E4A for ; Mon, 30 Dec 2002 14:14:43 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id gBUME9j07084; Mon, 30 Dec 2002 14:14:09 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id OAA13529; Mon, 30 Dec 2002 14:14:03 -0800 (PST) Received: from [10.100.253.70] (aslan [10.100.253.70]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id PAA06635; Mon, 30 Dec 2002 15:13:59 -0700 (MST) Date: Mon, 30 Dec 2002 15:14:01 -0700 From: "Justin T. Gibbs" Reply-To: "Justin T. Gibbs" To: Nate Lawson , Chuck McCrobie Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI Problems with sym and Western Digital on FreeBSD 4.7-stable Message-ID: <87850000.1041286441@aslan.btc.adaptec.com> In-Reply-To: References: X-Mailer: Mulberry/3.0.0b9 (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 > On Fri, 27 Dec 2002, Chuck McCrobie wrote: >> I am having SCSI problems with the sym driver and a >> Western Digital hard disk. Under the -stable kernel >> built on 'Dec 1', the drive show up fine with 16-bit >> wide transfers at 40 MHz. Under the most recent >> -stable kernel built on 'Dec 17', the Western Digital >> gets some type of very weird error message. The >> Western Digital is "da1". > >> (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. >> (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). >> (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. >> (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). >> (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. >> (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). >> (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. >> (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). >> (probe2:sym0:0:2:0): ODD transfer in DATA IN phase. >> (probe2:sym0:0:2:0): COMMAND FAILED (87 0 10). > > These appear to be the problem. Since nothing has changed in sym(4) for a > long time, this has to be elsewhere, perhaps in dma system. My guess is that the WD guys didn't set their additional inquiry length correctly and/or the length is correct, but they fail to issue an ignore wide residue for the last transfer. The problem only shows up now because we properly calculate the extra inquiry length. Perhaps we should do what Gerard suggested and round up to an even transfer size. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message