From owner-freebsd-scsi Fri Jan 3 7:20: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 3128837B401 for ; Fri, 3 Jan 2003 07:20:42 -0800 (PST) Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F4D943EDC for ; Fri, 3 Jan 2003 07:20: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 h03FIaMj035438; Fri, 3 Jan 2003 08:18:36 -0700 (MST) (envelope-from gibbs@scsiguy.com) Date: Fri, 03 Jan 2003 08:18:36 -0700 From: "Justin T. Gibbs" To: Chuck McCrobie , Nate Lawson Cc: freebsd-scsi@freebsd.org Subject: Re: SCSI Problems with sym and Western Digital on FreeBSD 4.7-stable Message-ID: <602540816.1041607116@aslan.scsiguy.com> In-Reply-To: <20021230225607.51427.qmail@web14806.mail.yahoo.com> References: <20021230225607.51427.qmail@web14806.mail.yahoo.com> 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 >> > 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 > > What would I see on a SCSI bus analyzer in terms of > "issue an ignore wide residue" message? Maybe I'll > have to break out the SCSI spec. and the bus > analyzer... What you will likely see is that FreeBSD requests an odd length transfer size for the inquiry, but at the end of the data phase, the target transfers one more byte than expected because an ignore wide residue message is not sent on the phase following data-in. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jan 3 10:46:30 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 CD8CA37B401 for ; Fri, 3 Jan 2003 10:46:28 -0800 (PST) Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9963843EDC for ; Fri, 3 Jan 2003 10:46:27 -0800 (PST) (envelope-from kenm@icarz.com) Received: from kenxp (netb-236.icarz.com [209.123.219.236] (may be forged)) by hercules.icarz.com (8.11.6/8.10.1) with SMTP id h03IkQr24707 for ; Fri, 3 Jan 2003 13:46:26 -0500 (EST) Message-ID: <001401c2b358$97a7dd90$ecdb7bd1@kenxp> From: "Ken Menzel" To: Subject: Adaptec 3200 on FreeBSD current Date: Fri, 3 Jan 2003 13:47:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 Hi, I have this controller on on DELL 2400 Dual PIII: asr0: mem 0xf0000000-0xf7ffffff irq 11 at device 8.1 on pci3 asr0: major=154 asr0: ADAPTEC 3200S FW Rev. 370F, 2 channel, 256 CCBs, Protocol I2O FreeBSD 5 RC2 sees the controller just like above. It is running FReeBSD 4.7 but on FreeBSD 5 RC2 (or RC1) The install CD says I have no drive to install to! Does anyone have any ideas on what I should look at to make the devices visible to FBSD 5 or debug this problem? Am I doing something wrong on FBSD5? I can boot the fixit disk on FBSD5 and dmesg shows sa0 and ch0 but NOT da0 This is the device list from 4.7: sa0 at asr0 bus 1 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device pass1 at asr0 bus 0 target 6 lun 0 pass1: Fixed Processor SCSI-2 device da0 at asr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 210021MB (430123008 512 byte sectors: 255H 63S/T 26773C) ch0 at asr0 bus 1 target 6 lun 1 ch0: Removable Changer SCSI-2 device ch0: 8 slots, 1 drive, 1 picker, 0 portals Mounting root from ufs:/dev/da0s1a Thanks Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 4 3:46: 8 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 77C5337B401 for ; Sat, 4 Jan 2003 03:46:06 -0800 (PST) Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id C895F43ED8 for ; Sat, 4 Jan 2003 03:46:05 -0800 (PST) (envelope-from groudier@free.fr) Received: from [192.168.1.129] (212.232.2.200) by mail.libertysurf.net (6.5.026) id 3DEB48900096601F; Sat, 4 Jan 2003 12:45:51 +0100 Date: Sat, 4 Jan 2003 13:45:29 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: groudier@localhost.my.domain To: "Justin T. Gibbs" Cc: Nate Lawson , Chuck McCrobie , Subject: Re: SCSI Problems with sym and Western Digital on FreeBSD 4.7-stable In-Reply-To: <87850000.1041286441@aslan.btc.adaptec.com> Message-ID: <20030104124808.C5252-100000@localhost.my.domain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE 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 Mon, 30 Dec 2002, Justin T. Gibbs wrote: > > 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) fo= r 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. Let this suggestion be suggestion #1. :) Another way (suggestion #2) could be to return success from SIM with a negative residual (-1 in this case) and leave upper layer handle the situation as it wants. As seen from the sym driver there is no semantic difference as it would be just a different way to report the problem. Is this an acceptable behaviour as expected by CAM? But what about situation where there is more than 1 extra byte returned or when a single extra-byte is returned in 8 bit mode, for example ? IMO, the CAM_DATA_RUN_ERR status may well be the way to go here. (Btw, for now, the sym driver returns CAM status CAM_DATA_RUN_ERR but the residual value returned is already -1). Note that if the IO buffer for inquiry is rounded up to an even size (suggestion #1), the upper layer can also catch the situation from the residual (will be zero when expected to be at least 1). There is no information loss here too (additionnaly, there is no needed change in sym). As suggestion #3, we might consider that CAM status CAM_DATA_RUN_ERR refers to data overrun conditions detected as caused by real hardware errors. Then, when a device returns more data than expected without real hardware error having been detected, SIM will just return CAM_REQ_CMP but supply a negative residual for the IO. No information less in the report here too. For my part, I do prefer #1 or #3 over #2. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 4 16:43:30 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 245DE37B401 for ; Sat, 4 Jan 2003 16:43:30 -0800 (PST) Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6038543EA9 for ; Sat, 4 Jan 2003 16:43:29 -0800 (PST) (envelope-from gary@outloud.org) Received: from ancient-iw4w1dr.outloud.org (wv-mrtnbrg-cmts1a-a-21.shphwv.adelphia.net [68.67.224.21]) by mail.webjockey.net (8.12.6/8.12.6) with ESMTP id h050hQ4u073892 for ; Sat, 4 Jan 2003 19:43:27 -0500 (EST) (envelope-from gary@outloud.org) Message-Id: <5.2.0.9.2.20030104194341.024452b8@208.141.46.254> X-Sender: ancient@208.141.46.3 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Sat, 04 Jan 2003 19:44:04 -0500 To: freebsd-scsi@freebsd.org From: Gary Stanley Subject: Segate or Maxtor? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 We currently deploy/use Segate Cheetah 10K.6 on some of our database/webservers for customers. However, the failure rate for new drives that we get in, is extremely high. (Out of every 10 drives, at least 4 of the drives are bad.) I was curious to know if there is another alt. to Seagate, or maybe someone else has a recommendation. Perhaps even a URL to a supplier that does burn in tests on the drives to make sure they are, in fair shape. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 4 17:19:27 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 57C0437B405 for ; Sat, 4 Jan 2003 17:19:26 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 0826D43EC2 for ; Sat, 4 Jan 2003 17:19:21 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 5764 invoked by uid 1000); 5 Jan 2003 01:19:22 -0000 Date: Sat, 4 Jan 2003 17:19:22 -0800 (PST) From: Nate Lawson To: Gary Stanley Cc: freebsd-scsi@freebsd.org Subject: Re: Segate or Maxtor? In-Reply-To: <5.2.0.9.2.20030104194341.024452b8@208.141.46.254> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Sat, 4 Jan 2003, Gary Stanley wrote: > We currently deploy/use Segate Cheetah 10K.6 on some of our > database/webservers for customers. However, the failure rate for new drives > that we get in, is extremely high. (Out of every 10 drives, at least 4 of > the drives are bad.) I've done well with the Maxtor (used to be Quantum) Atlas 10k3 and 15k drives for both SCSI and FC. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message