From owner-freebsd-scsi Sun Aug 29 12:24:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6586A150E8 for ; Sun, 29 Aug 1999 12:24:19 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-120.dialup.HiWAAY.net [216.180.14.120]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id OAA01268; Sun, 29 Aug 1999 14:24:16 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id OAA94336; Sun, 29 Aug 1999 14:06:12 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908291906.OAA94336@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: groudier@club-internet.fr (Gerard Roudier), freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Seagate vs Quantum.. opinions? In-reply-to: Message from "Kenneth D. Merry" of "Sat, 28 Aug 1999 01:37:39 MDT." <199908280737.BAA94296@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Aug 1999 14:06:12 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > In any case, David, I'd say try the following things, in light of what > Gerard said: > > - first, try using the -v switch, -f phys (instead of block format, since > only Quantum disks seem to support it, and the SCSI-2 spec says: "NOTE 110 The use of the block format is not recommended. There is no universal > model that sensibly defines the meaning of the logical block address of > a defect. In the usual case, a defect that has been reassigned no longer > has a logical block address.") and -PG. > > - If that doesn't work, try increasing the dlist_length parameter in > readdefects() in src/sbin/camcontrol/camcontrol.c to 65536. Interesting. Believe this was at least part of the problem. I don't know that I believe the answer but it did make a difference: # ./camcontrol defects -v -PG -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 1d 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # ./camcontrol defects -v -G -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 d 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # ./camcontrol defects -v -P -f phys (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 15 0 0 0 0 0 0 0 (pass2:ncr0:0:0:0): error code 0 Got 0 defects. # camcontrol defects -v -P -f phys error reading defect list: Input/output error CAM status is 0 # which camcontrol /sbin/camcontrol # pwd /home/obj/usr/src/sbin/camcontrol # So it appears the new camcontrol helps. And that I found the correct one after rebuilding it. Seems back in RELENG_22 if one simply typed "make" in a directory the obj files didn't get moved elsewhere. > It would also be helpful to see what happens on an Adaptec controller, as > this could be the result of a bug in the NCR driver. I'll see what I can do. At the moment I don't have access to SGI machines like I used to, but I've never seen a grood drive report a null factory bad block list. Mostly the reason to read my bad block list is that I believe it is growing. The drive is supposed to be auto-reassigning and I wanted to find out if it is: (da0:ncr0:0:0:0): READ(10). CDB: 28 0 1 9 b6 2 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:109b603 asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f (da0:ncr0:0:0:0): READ(10). CDB: 28 0 0 6a f2 6a 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:6af26b asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f (da0:ncr0:0:0:0): READ(10). CDB: 28 0 0 6a f2 6a 0 0 2 0 (da0:ncr0:0:0:0): MEDIUM ERROR info:6af26b asc:11,b (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f Of the above, I don't really know what block(s) are the problems. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 29 12:29:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 17FC1150B8 for ; Sun, 29 Aug 1999 12:29:23 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-120.dialup.HiWAAY.net [216.180.14.120]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id OAA03416; Sun, 29 Aug 1999 14:28:28 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id OAA94885; Sun, 29 Aug 1999 14:28:13 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199908291928.OAA94885@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" , groudier@club-internet.fr (Gerard Roudier), freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Seagate vs Quantum.. opinions? In-reply-to: Message from David Kelly of "Sun, 29 Aug 1999 14:06:12 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Aug 1999 14:28:13 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (replying to myself) David Kelly writes: > # ./camcontrol defects -v -P -f phys > (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 15 0 0 0 0 0 0 0 > (pass2:ncr0:0:0:0): error code 0 > Got 0 defects. [...] > So it appears the new camcontrol helps. And that I found the correct > one after rebuilding it. Seems back in RELENG_22 if one simply typed > "make" in a directory the obj files didn't get moved elsewhere. Replied too quickly. Reading further down the list where it was observed 65536 was too big to fit in 16 bits I tried it again at 65535 and am back to the old problem again. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 29 22:32:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 7E49E1520A for ; Sun, 29 Aug 1999 22:32:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA08575; Sun, 29 Aug 1999 23:30:57 -0600 (MDT) (envelope-from ken) Message-Id: <199908300530.XAA08575@panzer.kdm.org> Subject: Re: Seagate vs Quantum.. opinions? In-Reply-To: <199908291928.OAA94885@nospam.hiwaay.net> from David Kelly at "Aug 29, 1999 02:28:13 pm" To: dkelly@hiwaay.net (David Kelly) Date: Sun, 29 Aug 1999 23:30:57 -0600 (MDT) Cc: groudier@club-internet.fr, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Kelly wrote... > (replying to myself) David Kelly writes: > > # ./camcontrol defects -v -P -f phys > > (pass2:ncr0:0:0:0): READ DEFECT DATA(10). CDB: 37 0 15 0 0 0 0 0 0 0 > > (pass2:ncr0:0:0:0): error code 0 > > Got 0 defects. > [...] > > So it appears the new camcontrol helps. And that I found the correct > > one after rebuilding it. Seems back in RELENG_22 if one simply typed > > "make" in a directory the obj files didn't get moved elsewhere. > > Replied too quickly. Reading further down the list where it was > observed 65536 was too big to fit in 16 bits I tried it again at 65535 > and am back to the old problem again. Yep. As I said in response to your PR, and earlier on the list, I think this may be an NCR driver issue. My guess is that once you try things with your Adaptec controller at work, you'll find things work okay. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 30 2:15:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 3A11514F69; Mon, 30 Aug 1999 02:15:11 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id TAA12542; Mon, 30 Aug 1999 19:12:42 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma012532; Mon, 30 Aug 99 19:12:17 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA08240; Mon, 30 Aug 1999 19:12:17 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA26119; Mon, 30 Aug 1999 19:12:16 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA00547; Mon, 30 Aug 1999 19:12:15 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908300912.TAA00547@nymph.detir.qld.gov.au> To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: SCSI surprise! (was: Softupdates reliability?) Date: Mon, 30 Aug 1999 19:12:15 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [I'm trying my first crosspost experiment here. Please follow up to -scsi.] A week ago I posted my strange crash and subsequent doubts about the proper functioning of softupdates. This is more of the story. I examined the lost+found directory more closely and of the few files that I traced, they were all temporary files or newly created directories (ports actually) created in the CTM update process. So, maybe I didn't really lose anything. Maybe fsck just doesn't recognise one of the safe-but-crashed modes you get when using softupdates. But unfortunately, I needed a CVS tree urgently and restored a backup. To make up for this, I promise to do serious destruction testing of softupdates soon. But, I had another crash almost as soon as I started using the machine again. Again, the Exabyte was being used (but only rewinding at the time), but the obvious trigger this time was intense disk activity (from "rm"). The active file system was not using softupdates, and had a number of fsck -p correctable errors on reboot. Conclusions: 1) The Exabyte was not to blame for the crash 2) The crash wasn't a "scribble junk" crash (first one probably wasn't either) 3) Regular mounts are still safer than softupdates I took the lid off anyway hoping to find anything at all weird and noticed something I had forgotten. I was using a Seagate ST51080N 1GB disk earlier for some experimenting and had disconnected the POWER, but not the SCSI CABLE. (It's a really noisy drive!) When I also unplugged the SCSI cable, all crashes stopped. I've now used the machine intensively for several days (copying over 20GB of small and big files, and read and written several tapes) without incident. Conclusions: 4) My stepping of K6-2/300 is just fine 5) My Exabyte really is ok :-) 6) It is NOT safe to have a powered down SCSI device attached to a SCSI chain 7) The world really is a wonderful place ;-) So, apart from being happy at having stable hardware again, I am intensely curious about this. Why is a powered down SCSI device so nasty? For example, the first crash locked up my SCSI card so that reset didn't fix it, and the second crash hung one of my disks so that it had to be powered down to even be recognised! Is there a standard for this stuff? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 30 4:42:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mailgw3a.lmco.com (mailgw3a.lmco.com [192.35.35.24]) by hub.freebsd.org (Postfix) with ESMTP id CB70914C0E for ; Mon, 30 Aug 1999 04:42:55 -0700 (PDT) (envelope-from michael.e.remski@lmco.com) Received: from emss04g01.ems.lmco.com ([166.17.13.122]) by mailgw3a.lmco.com (8.8.8/8.8.8) with ESMTP id HAA01081 for ; Mon, 30 Aug 1999 07:41:22 -0400 (EDT) Received: from CONVERSION-DAEMON by lmco.com (PMDF V5.2-32 #38890) id <0FHA00C010GYSE@lmco.com> for freebsd-scsi@freebsd.org; Mon, 30 Aug 1999 07:41:22 -0400 (EDT) Received: from lmco.com ([129.86.163.80]) by lmco.com (PMDF V5.2-32 #38890) with ESMTP id <0FHA006KW0GVD2@lmco.com> for freebsd-scsi@freebsd.org; Mon, 30 Aug 1999 07:41:20 -0400 (EDT) Date: Mon, 30 Aug 1999 07:29:34 -0400 From: Michael Remski Subject: Re: SCSI Suprise To: freebsd-scsi@freebsd.org Reply-To: michael.e.remski@lmco.com Message-id: <37CA6B1E.C26168D6@lmco.com> Organization: Sanders A Lockheed Martin Company MIME-version: 1.0 X-Mailer: Mozilla 4.5 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How was the termination set on the "attached, but unpowered" drive? Most drives I've run across have a "get termination power from the bus" option; I was wondering what would happen if this drive happened to be in the middle of the chain. m -- "To keep in silence our designs, my friends would think I was a nut" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 30 8:29:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 840EE14CEC; Mon, 30 Aug 1999 08:29:37 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA12053; Mon, 30 Aug 1999 17:12:27 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id OAA01384; Mon, 30 Aug 1999 14:53:13 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908301253.OAA01384@yedi.iaf.nl> Subject: Re: SCSI surprise! (was: Softupdates reliability?) In-Reply-To: <199908300912.TAA00547@nymph.detir.qld.gov.au> from Stephen McKay at "Aug 30, 1999 7:12:15 pm" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Mon, 30 Aug 1999 14:53:12 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Stephen McKay wrote ... > I took the lid off anyway hoping to find anything at all weird and noticed > something I had forgotten. I was using a Seagate ST51080N 1GB disk earlier > for some experimenting and had disconnected the POWER, but not the SCSI CABLE. > (It's a really noisy drive!) When I also unplugged the SCSI cable, all crashes > stopped. I've now used the machine intensively for several days (copying over > 20GB of small and big files, and read and written several tapes) without > incident. Conclusions: > > 4) My stepping of K6-2/300 is just fine > 5) My Exabyte really is ok :-) > 6) It is NOT safe to have a powered down SCSI device attached to a SCSI chain > 7) The world really is a wonderful place ;-) > > So, apart from being happy at having stable hardware again, I am intensely > curious about this. Why is a powered down SCSI device so nasty? For example, It is normally not so nasty. Did this particular device have the SCSI terminator? If so, the terminator needs +5V (terminator power aka TERMPWR) to function correctly. Some devices can be setup to take terminator power from the bus (generally supplied by the host adapter) or from the device they are installed on. I've run things with power-ed down devices without any ill effects. But always with external terminators, so not with the terminator on the device itself but on the bus cable. > the first crash locked up my SCSI card so that reset didn't fix it, and the > second crash hung one of my disks so that it had to be powered down to even > be recognised! Is there a standard for this stuff? Yes, the ANSI SCSI standard. www.t10.org (.com??) Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 30 8:59:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from east.isi.edu (east.isi.edu [38.245.76.2]) by hub.freebsd.org (Postfix) with ESMTP id 9C47F150ED for ; Mon, 30 Aug 1999 08:59:36 -0700 (PDT) (envelope-from aakesson@EAST.ISI.EDU) Received: from ale by east.isi.edu (8.8.5/5.61+local-24) id ; Mon, 30 Aug 1999 15:58:42 GMT Date: Mon, 30 Aug 1999 11:58:42 -0400 (EDT) From: Alec Aakesson To: freebsd-scsi@freebsd.org Cc: Alec Aakesson Subject: ahc0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have an ahc0 (aha 2940w/2940uw), and when I try to install any large files on to a scsi disk I get this message: sd0(ahc0:0:0) SCB 0x0 -timed out in dataout phase, SCSISIGI == 0xe6 SEQADDR = 0x129 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 sd0(ahc0:0:0): abort message in buffer sd0(ahc0:0:0) SCB 0x1 -timed out in dataout phase, SCSISIGI == 0xf6 SEQADDR = 0x129 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 sd0(ahc0:0:0): no logner in timeout ahc0: Issued Channel A Bus Reset. 2 SCBs aborted I have tried throttling the scsi controller back to 10Mbs and disabling the wide scsi negotiation. Effectively, this gave a throughput of 5Mbs but this still did not work. Thanks, Alec ________________________________________________________________________ Alexander S. Aakesson aakesson@isi.edu USC/ISI 703.812.3724 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 30 9:15:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0035214DFD for ; Mon, 30 Aug 1999 09:15:17 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA11381; Mon, 30 Aug 1999 10:14:48 -0600 (MDT) (envelope-from ken) Message-Id: <199908301614.KAA11381@panzer.kdm.org> Subject: Re: ahc0 In-Reply-To: from Alec Aakesson at "Aug 30, 1999 11:58:42 am" To: aakesson@EAST.ISI.EDU (Alec Aakesson) Date: Mon, 30 Aug 1999 10:14:48 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alec Aakesson wrote... > Hi, > I have an ahc0 (aha 2940w/2940uw), and when I try to install any large > files on to a scsi disk I get this message: > > sd0(ahc0:0:0) SCB 0x0 -timed out in dataout phase, SCSISIGI == 0xe6 > SEQADDR = 0x129 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 > sd0(ahc0:0:0): abort message in buffer > sd0(ahc0:0:0) SCB 0x1 -timed out in dataout phase, SCSISIGI == 0xf6 > SEQADDR = 0x129 SCSISEQ = 0x12 SSTAT0 = 0x2 SSTAT1 = 0x13 > sd0(ahc0:0:0): no logner in timeout > ahc0: Issued Channel A Bus Reset. 2 SCBs aborted > > I have tried throttling the scsi controller back to 10Mbs and disabling > the wide scsi negotiation. Effectively, this gave a throughput of 5Mbs but > this still did not work. The 'timed out in dataout' phase errors generally indicate a cabling or termination problem, so throttling the bus speed back won't necessarily fix the problem. So, check your cables, and make sure everything is terminated properly. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 2:56:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id BAF8614EEB for ; Tue, 31 Aug 1999 02:56:10 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id TAA10907; Tue, 31 Aug 1999 19:53:10 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma010886; Tue, 31 Aug 99 19:52:58 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA22904; Tue, 31 Aug 1999 19:52:57 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id TAA26632; Tue, 31 Aug 1999 19:52:57 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id TAA18445; Tue, 31 Aug 1999 19:52:56 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199908310952.TAA18445@nymph.detir.qld.gov.au> To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: SCSI surprise! (was: Softupdates reliability?) References: <199908301253.OAA01384@yedi.iaf.nl> In-Reply-To: <199908301253.OAA01384@yedi.iaf.nl> from Wilko Bulte at "Mon, 30 Aug 1999 14:53:12 +0200" Date: Tue, 31 Aug 1999 19:52:55 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 30th August 1999, Wilko Bulte wrote: >As Stephen McKay wrote ... > >> So, apart from being happy at having stable hardware again, I am intensely >> curious about this. Why is a powered down SCSI device so nasty? For example, > >It is normally not so nasty. Did this particular device have the SCSI >terminator? If so, the terminator needs +5V (terminator power aka TERMPWR) >to function correctly. Some devices can be setup to take terminator power >from the bus (generally supplied by the host adapter) or from the device >they are installed on. > >I've run things with power-ed down devices without any ill effects. But >always with external terminators, so not with the terminator on the device >itself but on the bus cable. Just to be more clear about this: The SCSI cable has an active terminator on the end, so no devices are terminated. The problem drive is not terminated and functions just fine when powered up. It is in the middle of the chain. I've had other powered-down-but-connected SCSI devices without trouble in the past. I'll check the drive more carefully tonight for "power terminator from BUS" stuff to see if there is any possible silly stuff there. But I think the fact is that sometimes it's not safe to just pull the power plug. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 8:28: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id E884115977 for ; Tue, 31 Aug 1999 08:27:56 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id RAA25219 for ; Tue, 31 Aug 1999 17:27:47 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id RAA02514 for scsi@FreeBSD.ORG; Tue, 31 Aug 1999 17:10:05 +0200 (CEST) (envelope-from andreas) Date: Tue, 31 Aug 1999 17:10:05 +0200 From: Andreas Klemm To: scsi@FreeBSD.ORG Subject: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e Message-ID: <19990831171005.A2252@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Operating-System: FreeBSD 3.2-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What might cause this ? (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e (da0:ahc0:0:0:0): BDR message in message buffer (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10d (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 10 SCBs aborted Andreas /// FreeBSD titan.klemm.gtn.com 3.2-STABLE FreeBSD 3.2-STABLE #0: Wed Aug 18 21:32:29 CEST 1999 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN i386 Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #0: Wed Aug 18 21:32:29 CEST 1999 root@titan.klemm.gtn.com:/usr/src/sys/compile/TITAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 159383552 (155648K bytes) avail memory = 151597056 (148044K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02ef000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0x01 int a irq 255 on pci0.10.0 xl0: <3Com 3c900-COMBO Etherlink XL> rev 0x00 int a irq 19 on pci0.11.0 xl0: Ethernet address: 00:60:97:aa:3a:db xl0: selecting 10baseT transceiver, half duplex ahc0: rev 0x00 int a irq 17 on pci0.13.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 16 on pci0.14.0 ahc1: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:5a:98:2a, type WD8013EPC (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry ccd0-3: Concatenated disk drivers DUMMYNET initialized (990504) Waiting 8 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 4.807MB/s transfers (4.807MHz, offset 8) cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: cd present [215086 x 2048 byte records] cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15) da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da3 at ahc1 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 20.000MB/s transfers (20.000MHz, offset 15) da3: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15) da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Connection attempt to UDP 127.0.0.1:1025 from 127.0.0.1:53 xl0: promiscuous mode enabled (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e (da0:ahc0:0:0:0): BDR message in message buffer (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10d (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 10 SCBs aborted -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Latest song from our band: http://www.freebsd.org/~andreas/64bits/schaukel.mp3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 8:34:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A92C714F39 for ; Tue, 31 Aug 1999 08:32:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA17530; Tue, 31 Aug 1999 17:30:46 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA53070; Tue, 31 Aug 1999 17:24:41 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199908311524.RAA53070@yedi.iaf.nl> Subject: Re: SCSI surprise! (was: Softupdates reliability?) In-Reply-To: <199908310952.TAA18445@nymph.detir.qld.gov.au> from Stephen McKay at "Aug 31, 1999 7:52:55 pm" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Tue, 31 Aug 1999 17:24:41 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Stephen McKay wrote ... > On Monday, 30th August 1999, Wilko Bulte wrote: > >As Stephen McKay wrote ... > > > >> So, apart from being happy at having stable hardware again, I am intensely > >> curious about this. Why is a powered down SCSI device so nasty? For example, > > > >It is normally not so nasty. Did this particular device have the SCSI > >terminator? If so, the terminator needs +5V (terminator power aka TERMPWR) > >to function correctly. Some devices can be setup to take terminator power > >from the bus (generally supplied by the host adapter) or from the device > >they are installed on. > > > >I've run things with power-ed down devices without any ill effects. But > >always with external terminators, so not with the terminator on the device > >itself but on the bus cable. > > Just to be more clear about this: The SCSI cable has an active terminator > on the end, so no devices are terminated. The problem drive is not terminated > and functions just fine when powered up. It is in the middle of the chain. > I've had other powered-down-but-connected SCSI devices without trouble in > the past. Right. That is what I expect of a SCSI device ;-) > I'll check the drive more carefully tonight for "power terminator from BUS" > stuff to see if there is any possible silly stuff there. But I think the > fact is that sometimes it's not safe to just pull the power plug. Maybe there is something really weird about your particular drive. I can only repeat my experience which is different :/ -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 8:38:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1431114E5D for ; Tue, 31 Aug 1999 08:38:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA17906; Tue, 31 Aug 1999 09:37:27 -0600 (MDT) (envelope-from ken) Message-Id: <199908311537.JAA17906@panzer.kdm.org> Subject: Re: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e In-Reply-To: <19990831171005.A2252@titan.klemm.gtn.com> from Andreas Klemm at "Aug 31, 1999 05:10:05 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 31 Aug 1999 09:37:27 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas Klemm wrote... > What might cause this ? > > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e > (da0:ahc0:0:0:0): BDR message in message buffer > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10d > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 10 SCBs aborted It usually indicates a cabling or termination problem. If the message is "timed out in {datain,dataout,command} phase", the cause is often the same -- cabling or termination. If you see a "timed out while idle" message, that often points to buggy drive firmware, but in some rare cases it can just mean that there's a timeout set too short. In any case, check your cabling and termination. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 10:18:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from moebius2.Space.Net (moebius2.Space.Net [195.30.1.100]) by hub.freebsd.org (Postfix) with SMTP id 6A31614E64 for ; Tue, 31 Aug 1999 10:18:28 -0700 (PDT) (envelope-from maex@Space.Net) Received: (qmail 26917 invoked by uid 1013); 31 Aug 1999 17:18:27 -0000 Message-ID: <19990831191827.F21474@space.net> Date: Tue, 31 Aug 1999 19:18:27 +0200 From: Markus Stumpf To: scsi@FreeBSD.ORG Subject: Re: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e References: <19990831171005.A2252@titan.klemm.gtn.com> <199908311537.JAA17906@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199908311537.JAA17906@panzer.kdm.org>; from Kenneth D. Merry on Tue, Aug 31, 1999 at 09:37:27AM -0600 Organization: SpaceNet GmbH, Muenchen, Germany Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 31, 1999 at 09:37:27AM -0600, Kenneth D. Merry wrote: > It usually indicates a cabling or termination problem. If the message is > "timed out in {datain,dataout,command} phase", the cause is often the same > -- cabling or termination. I have a box I want to use as a web cache (squid2). FreeBSD zuse.space.net 3.2-RELEASE FreeBSD 3.2-RELEASE #1: Mon Aug 23 18:13:42 CEST 1999 root@zuse.space.net:/usr/src/sys/compile/ZUSEN i386 CPU: Pentium III (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping=2 Features=0x383f9ff,> real memory = 536870912 (524288K bytes) avail memory = 520019968 (507832K bytes) Preloaded elf kernel "kernel" at 0xc02af000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 It has two controllers: ahc0: rev 0x00 int a irq 10 on pci0.9.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.10.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Each controller has two Fixed Direct Access SCSI-3 device 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) and one Fixed Direct Access SCSI-3 device 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) connected. da3 at ahc1 bus 0 target 0 lun 0 da3: Fixed Direct Access SCSI-3 device da5 at ahc1 bus 0 target 2 lun 0 da5: Fixed Direct Access SCSI-3 device da4 at ahc1 bus 0 target 1 lun 0 da4: Fixed Direct Access SCSI-3 device da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device Root device is da0s1a. Cabelling and termination checked and ok (AFAIK). No other SCSI devices present (CD rom is on isa) When doing stress tests (simulating 300 parallel clients to the squid cache) I also get from time to time messages like these: Aug 31 18:16:28 zuse /kernel: (da1:ahc0:0:1:0): SCB 0x6d - timed out in dataout phase, SEQADDR == 0x5d Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): BDR message in message buffer Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): SCB 0x1c - timed out in dataout phase, SEQADDR == 0x5d Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 34b Aug 31 18:16:35 zuse /kernel: ahc0: Issued Channel A Bus Reset. 65 SCBs aborted It happens on both controllers and with all disks used for the cache (high IO rates). Any help welcome! \Maex (P.S. I think there are currently only "dataout phase" problems, as with the stress tests I am also migrating data from the old cache to the new one, so the hit ratio is zero, as all data has to be fetched from the parent (the old cache) and is stored on disk. -- SpaceNet GmbH | http://www.Space.Net/ | Yeah, yo mama dresses Research & Development | mailto:maex-sig@Space.Net | you funny and you need Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0 | a mouse to delete files D-80807 Muenchen | Fax: +49 (89) 32356-299 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 11:56:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2E0CE14C35 for ; Tue, 31 Aug 1999 11:56:17 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA19242; Tue, 31 Aug 1999 12:53:30 -0600 (MDT) (envelope-from ken) Message-Id: <199908311853.MAA19242@panzer.kdm.org> Subject: Re: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e In-Reply-To: <19990831191827.F21474@space.net> from Markus Stumpf at "Aug 31, 1999 07:18:27 pm" To: maex-lists-freebsd-scsi@Space.Net (Markus Stumpf) Date: Tue, 31 Aug 1999 12:53:30 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Markus Stumpf wrote... > On Tue, Aug 31, 1999 at 09:37:27AM -0600, Kenneth D. Merry wrote: > > It usually indicates a cabling or termination problem. If the message is > > "timed out in {datain,dataout,command} phase", the cause is often the same > > -- cabling or termination. > > I have a box I want to use as a web cache (squid2). > [ ... ] > Each controller has two > Fixed Direct Access SCSI-3 device > 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > and one > Fixed Direct Access SCSI-3 device > 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > connected. [ ... ] > Cabelling and termination checked and ok (AFAIK). > No other SCSI devices present (CD rom is on isa) > > When doing stress tests (simulating 300 parallel clients to the squid > cache) I also get from time to time messages like these: > > Aug 31 18:16:28 zuse /kernel: (da1:ahc0:0:1:0): SCB 0x6d - timed out in dataout phase, SEQADDR == 0x5d > Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): BDR message in message buffer > Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): SCB 0x1c - timed out in dataout phase, SEQADDR == 0x5d > Aug 31 18:16:35 zuse /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 34b > Aug 31 18:16:35 zuse /kernel: ahc0: Issued Channel A Bus Reset. 65 SCBs aborted > > It happens on both controllers and with all disks used for the cache > (high IO rates). > > Any help welcome! > > \Maex > > (P.S. I think there are currently only "dataout phase" problems, as with > the stress tests I am also migrating data from the old cache to the new one, > so the hit ratio is zero, as all data has to be fetched from the parent > (the old cache) and is stored on disk. There are several things to point out here. You're probably aware of some of them, but they often catch people off guard: - When running drives at LVD speeds, you need to have one of the "twisty" LVD SCSI cables. - LVD drives don't have terminators, so you have to use a twisty cable with a terminator block on the end. (All the twisty cables I've seen have terminators.) - Justin has had problems before with bent pins on LVD cables. They seem to be a bit fragile sometimes. A bent pin can easily cause problems like the one above. - You can run into trouble sometimes at LVD data rates if your SCSI cables go too close to a power supply. You should make sure your cables are routed away from your power supply. Anyway, those are the most common causes of timeouts. The power supply interference problem seems to crop up more often at LVD speeds than with lower speed busses. And timeout problems like the one above are more likely to occur under high load. (Of course with some cabling/termination problems, they'll show up under any load. But "timed out in {datain,dataout,command} phase" problems are more likely to show up when the bus is loaded more.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 13:17:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 25EBE14C0C for ; Tue, 31 Aug 1999 13:17:11 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id WAA03963; Tue, 31 Aug 1999 22:16:24 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id WAA11634; Tue, 31 Aug 1999 22:04:32 +0200 (CEST) (envelope-from andreas) Date: Tue, 31 Aug 1999 22:04:32 +0200 From: Andreas Klemm To: "Kenneth D. Merry" Cc: Andreas Klemm , scsi@FreeBSD.ORG Subject: Re: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e Message-ID: <19990831220432.B10873@titan.klemm.gtn.com> References: <19990831171005.A2252@titan.klemm.gtn.com> <199908311537.JAA17906@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908311537.JAA17906@panzer.kdm.org>; from Kenneth D. Merry on Tue, Aug 31, 1999 at 09:37:27AM -0600 X-Operating-System: FreeBSD 3.2-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 31, 1999 at 09:37:27AM -0600, Kenneth D. Merry wrote: > Andreas Klemm wrote... > > What might cause this ? > > > > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e > > (da0:ahc0:0:0:0): BDR message in message buffer > > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10d > > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 10 SCBs aborted > > It usually indicates a cabling or termination problem. If the message is > "timed out in {datain,dataout,command} phase", the cause is often the same > -- cabling or termination. > > If you see a "timed out while idle" message, that often points to buggy > drive firmware, but in some rare cases it can just mean that there's a > timeout set too short. > > In any case, check your cabling and termination. Thanks. Will have to check this. 2 controller. One holds the three ccd disks. The boot drive is connected to another 2940 with the other devices like cdrom, burner, 2nd boot disk and streamer. Will have to check, if the terminating device has proper termination and if it gets power from itself or the bus. I think power from itself is preferred over getting term power from the bus right ? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Latest song from our band: http://www.freebsd.org/~andreas/64bits/schaukel.mp3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 31 16:47:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 547A81503D for ; Tue, 31 Aug 1999 16:47:10 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA20813; Tue, 31 Aug 1999 17:47:04 -0600 (MDT) (envelope-from ken) Message-Id: <199908312347.RAA20813@panzer.kdm.org> Subject: Re: 3.2-STABLE: SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e In-Reply-To: <19990831220432.B10873@titan.klemm.gtn.com> from Andreas Klemm at "Aug 31, 1999 10:04:32 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Tue, 31 Aug 1999 17:47:04 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas Klemm wrote... > On Tue, Aug 31, 1999 at 09:37:27AM -0600, Kenneth D. Merry wrote: > > Andreas Klemm wrote... > > > What might cause this ? > > > > > > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10e > > > (da0:ahc0:0:0:0): BDR message in message buffer > > > (da0:ahc0:0:0:0): SCB 0x7 - timed out in datain phase, SEQADDR == 0x10d > > > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > > ahc0: Issued Channel A Bus Reset. 10 SCBs aborted > > > > It usually indicates a cabling or termination problem. If the message is > > "timed out in {datain,dataout,command} phase", the cause is often the same > > -- cabling or termination. > > > > If you see a "timed out while idle" message, that often points to buggy > > drive firmware, but in some rare cases it can just mean that there's a > > timeout set too short. > > > > In any case, check your cabling and termination. > > Thanks. Will have to check this. > 2 controller. One holds the three ccd disks. > The boot drive is connected to another 2940 with the other > devices like cdrom, burner, 2nd boot disk and streamer. > Will have to check, if the terminating device has proper > termination and if it gets power from itself or the bus. > > I think power from itself is preferred over getting term power > from the bus right ? Yeah, I think so. (Someone else may have a more definite answer.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 1 16:41: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id A8221154AD for ; Wed, 1 Sep 1999 16:41:04 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id BAA07963 for ; Thu, 2 Sep 1999 01:40:52 +0200 (CEST) Message-Id: <199909012340.BAA07963@gw0.boostworks.com> Date: Thu, 2 Sep 1999 01:40:49 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: command delay offset To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry to bother you with a so simple question, but.... what is the 'command delay offset' (aka offset) role ? What values can be set via camcontrol negotiate -O ? TIA. RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 1 16:57:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id A2C4714D9D for ; Wed, 1 Sep 1999 16:57:27 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA03250; Wed, 1 Sep 1999 17:55:09 -0600 (MDT) (envelope-from ken) Message-Id: <199909012355.RAA03250@panzer.kdm.org> Subject: Re: command delay offset In-Reply-To: <199909012340.BAA07963@gw0.boostworks.com> from Remy Nonnenmacher at "Sep 2, 1999 01:40:49 am" To: remy@synx.com Date: Wed, 1 Sep 1999 17:55:09 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Remy Nonnenmacher wrote... > Sorry to bother you with a so simple question, but.... > > what is the 'command delay offset' (aka offset) role ? What values can > be set via camcontrol negotiate -O ? It allows you to specify the SCSI REQ/ACK offset. The REQ/ACK offset is, along with the period/sync rate, part of synchronous data transfer negotiation. Here's a quote from the SCSI-2 spec: "The REQ/ACK offset specifies the maximum number of REQ pulses that can be sent by the target in advance of the number of ACK pulses received from the initiator, establishing a pacing mechanism. If the number of REQ pulses exceeds the number of ACK pulses by the REQ/ACK offset, the target shall not assert the REQ signal until after the leading edge of the next ACK pulse is received. For successful completion of the data phase is that the number of ACK and REQ pulses shall be equal." In networking terms, it's the window size. Keep in mind that 'camcontrol negotiate' is only supported for a few boards, and some support it better than others. In general, if you set the offset to 0, you will end up disabling synchronous negotiation for that device. If you set the offset to a non-zero value, generally the controller will attempt to negotiate the given offset with the device. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 1 21: 3:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id D93CF14E29 for ; Wed, 1 Sep 1999 21:03:35 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id OAA24521; Thu, 2 Sep 1999 14:00:03 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (3.2) id xma024436; Thu, 2 Sep 99 13:59:46 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id NAA07461; Thu, 2 Sep 1999 13:59:39 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id NAA09920; Thu, 2 Sep 1999 13:59:34 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id NAA11043; Thu, 2 Sep 1999 13:59:33 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199909020359.NAA11043@nymph.detir.qld.gov.au> To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: SCSI surprise! (was: Softupdates reliability?) References: <199908311524.RAA53070@yedi.iaf.nl> In-Reply-To: <199908311524.RAA53070@yedi.iaf.nl> from Wilko Bulte at "Tue, 31 Aug 1999 17:24:41 +0200" Date: Thu, 02 Sep 1999 13:59:32 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tuesday, 31st August 1999, Wilko Bulte wrote: >As Stephen McKay wrote ... >> I'll check the drive more carefully tonight for "power terminator from BUS" >> stuff to see if there is any possible silly stuff there. But I think the >> fact is that sometimes it's not safe to just pull the power plug. > >Maybe there is something really weird about your particular drive. I can >only repeat my experience which is different :/ I checked the problem drive last night. The drive was set to power its own terminator, but the terminator is definitely off. It can also power the SCSI bus, but that's off too. So, all looks normal. I'll just assume this is a rogue drive until I see another one. I still don't understand how it's possible though. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 6: 6:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dot.crosswinds.net (dot.crosswinds.net [204.50.152.131]) by hub.freebsd.org (Postfix) with ESMTP id 2796C14E5A for ; Thu, 2 Sep 1999 06:06:02 -0700 (PDT) (envelope-from tony@crosswinds.net) Received: from fong.crosswinds.net (fong.crosswinds.net [204.50.152.67]) by dot.crosswinds.net (8.9.3/8.9.3) with ESMTP id JAA33497 for ; Thu, 2 Sep 1999 09:12:54 -0400 (EDT) (envelope-from tony@crosswinds.net) Received: (from tony@localhost) by fong.crosswinds.net (8.8.7/8.8.7) id JAA17771; Thu, 2 Sep 1999 09:01:11 -0400 (EDT) (envelope-from tony) Message-ID: <19990902090111.A17707@crosswinds.net> Date: Thu, 2 Sep 1999 09:01:11 -0400 From: Tony Holmes To: scsi@freebsd.org Subject: Binding host channels Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am currently in the process of upgrading a set of servers here and, after a lot of reading and thought, have decided upon a CMD SCSI controller system. I require huge volumes of disk with moderately decent throughput, so a CMD 5500 controller with 4 host and 5 SCSI disk channels was selected. The four host channels are connected to the host via 2 Adaptec 3950 (dual U2W) controllers, each on it's own PCI bus. So I have: 4 * U2W 5 * U2W |-----------| CMD |----------| FreeBSD |-----------| 5500 |----------| Lot's O Disk Server |-----------| |----------| |-----------| |----------| |----------| My question is this: Is it possible to "bind" the four host channels together to make the system appear to have one, very fast host channel connected to one very large disk (ala the CMD)? Or do I have to result to partitioning the disks into 4 logical units on the controller? The application (massive web space, with no limits per account) pushes for a single volume that can grow over time. It has been indicated to me that future version of the CMD controller will support volume expansion at the controller, thus I wish to take advantage of this (reduces my admin headaches massively). The other solution I do have is to utilize Vinum, but growing the partitions is a big more hairy. I am quite familiar with FreeBSD and it's resources, but this question has bent my brain in a new direction. Thanks in advance for your ideas and answers. -- Tony Holmes Senior Systems Architect Crosswinds Internet Communications Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 7:53:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id 4A67814D14 for ; Thu, 2 Sep 1999 07:53:33 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id QAA11609; Thu, 2 Sep 1999 16:52:10 +0200 (CEST) Message-Id: <199909021452.QAA11609@gw0.boostworks.com> Date: Thu, 2 Sep 1999 16:52:07 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: command delay offset To: ken@kdm.org Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199909012355.RAA03250@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Sep, Kenneth D. Merry wrote: > Remy Nonnenmacher wrote... >> .. >> what is the 'command delay offset' (aka offset) role ? What values can >> be set via camcontrol negotiate -O ? > >... > In networking terms, it's the window size. >... Can I expect more performance by using a greater value ? (Context is 3250U2W with LVD disks). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 8:10:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 60A6F15B61 for ; Thu, 2 Sep 1999 08:10:24 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA07293; Thu, 2 Sep 1999 09:09:36 -0600 (MDT) (envelope-from ken) Message-Id: <199909021509.JAA07293@panzer.kdm.org> Subject: Re: command delay offset In-Reply-To: <199909021452.QAA11609@gw0.boostworks.com> from Remy Nonnenmacher at "Sep 2, 1999 04:52:07 pm" To: remy@synx.com Date: Thu, 2 Sep 1999 09:09:36 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Remy Nonnenmacher wrote... > On 1 Sep, Kenneth D. Merry wrote: > > Remy Nonnenmacher wrote... > >> .. > >> what is the 'command delay offset' (aka offset) role ? What values can > >> be set via camcontrol negotiate -O ? > > > >... > > In networking terms, it's the window size. > >... > > Can I expect more performance by using a greater value ? It is probably already negotiated to be as high as it can go. You can try setting it higher (if possible), and see whether your performance improves. > (Context is 3250U2W with LVD disks). Don't you mean a 3950? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 8:48:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1896715BCF for ; Thu, 2 Sep 1999 08:48:07 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA22696; Thu, 2 Sep 1999 17:36:48 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id KAA19915; Thu, 2 Sep 1999 10:53:42 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909020853.KAA19915@yedi.iaf.nl> Subject: Re: SCSI surprise! (was: Softupdates reliability?) In-Reply-To: <199909020359.NAA11043@nymph.detir.qld.gov.au> from Stephen McKay at "Sep 2, 1999 1:59:32 pm" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Thu, 2 Sep 1999 10:53:42 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Stephen McKay wrote ... > On Tuesday, 31st August 1999, Wilko Bulte wrote: > > >As Stephen McKay wrote ... > >Maybe there is something really weird about your particular drive. I can > >only repeat my experience which is different :/ > > I checked the problem drive last night. The drive was set to power its own > terminator, but the terminator is definitely off. It can also power the > SCSI bus, but that's off too. So, all looks normal. > > I'll just assume this is a rogue drive until I see another one. I still > don't understand how it's possible though. The only theory I have is that the chips[s] that drive the SCSI bus are somehow scr* things for you. W/ -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 9: 6:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id AA8D114C8D for ; Thu, 2 Sep 1999 09:06:51 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id JAA72708; Thu, 2 Sep 1999 09:54:40 -0600 (MDT) Date: Thu, 2 Sep 1999 09:54:40 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199909021554.JAA72708@narnia.plutotech.com> To: Tony Holmes Cc: scsi@FreeBSD.org Subject: Re: Binding host channels X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19990902090111.A17707@crosswinds.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990902090111.A17707@crosswinds.net> you wrote: > I am currently in the process of upgrading a set of servers here and, > after a lot of reading and thought, have decided upon a CMD SCSI > controller system. I require huge volumes of disk with moderately > decent throughput, so a CMD 5500 controller with 4 host and 5 SCSI > disk channels was selected. CMD controllers have been known to deal poorly with resource shortages when attached to multiple hosts. Perhaps they have addressed this issue, but I haven't heard any reports that they have. The CMD also has a fairly low transaction capability (32?), so I wouldn't recommend them for data sets comprised of lots of small files (e.g. news). > 4 * U2W 5 * U2W > |-----------| CMD |----------| > FreeBSD |-----------| 5500 |----------| Lot's O Disk > Server |-----------| |----------| > |-----------| |----------| > |----------| > > My question is this: Is it possible to "bind" the four host channels > together to make the system appear to have one, very fast host channel > connected to one very large disk (ala the CMD)? Or do I have to result > to partitioning the disks into 4 logical units on the controller? What you want is multi-pathing to a single device and no, it isn't currently supported. I am interested in supporting it, but have limited free time right now. I might be able to free up contracting time to do the work if it is really important to you. > The application (massive web space, with no limits per account) pushes for > a single volume that can grow over time. Our FFS can't be grown dynamically. It could be modified to allow this, but you'd need to contract an FS guru to do the work. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 2 14: 6:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id 3817914ECD for ; Thu, 2 Sep 1999 14:06:03 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (root@rn.synx.com [192.1.1.241]) by gw0.boostworks.com (8.9.1/8.9.1) with ESMTP id XAA12981 for ; Thu, 2 Sep 1999 23:05:46 +0200 (CEST) Message-Id: <199909022105.XAA12981@gw0.boostworks.com> Date: Thu, 2 Sep 1999 23:05:43 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: ccd peak performance To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I ran in a strange 60MB/s barrier somewhere and would like to have some highlight about it : I use a machine with 3 PCI buses, each bus with 3 U2W-LVD SCSI channels. All disks deliver a little more than 20MB/s (Quantum 18.2). Whatever CCD configuration I try, I get a 60MB/s peak read performance per CCD. I tried 4,5 and 6 disks, on various channels, on various PCI busses, etc...: Can't get more than 60MB/s. Using two CCD on same controller pull up perf to 72MB/s (which is near the channel bandwidth). Using 3 CCD's on different channels takes me to a little more than 160MB/s (and 2 CCD's on different channels give me about 120MB/s. Peak perf with all disks active (direct read) is 175MB/s). Any guess where does that 60MB/s/CCD limit comes from ? (Performance numbers with vinum also welcome). Additional Infos: 3.2-STABLE, Intel C440GX+ SMP Bi-Xeon 500, 2x3950U2W (channel A used) + Internal 7896 controller. TIA. RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 9: 5: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5B52014C87 for ; Fri, 3 Sep 1999 09:04:56 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA14523; Fri, 3 Sep 1999 10:04:20 -0600 (MDT) (envelope-from ken) Message-Id: <199909031604.KAA14523@panzer.kdm.org> Subject: Re: ccd peak performance In-Reply-To: <199909022105.XAA12981@gw0.boostworks.com> from Remy Nonnenmacher at "Sep 2, 1999 11:05:43 pm" To: remy@synx.com Date: Fri, 3 Sep 1999 10:04:20 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Remy Nonnenmacher wrote... > > I ran in a strange 60MB/s barrier somewhere and would like to have some > highlight about it : > > I use a machine with 3 PCI buses, each bus with 3 U2W-LVD SCSI channels. > > All disks deliver a little more than 20MB/s (Quantum 18.2). > > Whatever CCD configuration I try, I get a 60MB/s peak read performance > per CCD. I tried 4,5 and 6 disks, on various channels, on various PCI > busses, etc...: Can't get more than 60MB/s. > > Using two CCD on same controller pull up perf to 72MB/s (which is near > the channel bandwidth). Using 3 CCD's on different channels takes me to > a little more than 160MB/s (and 2 CCD's on different channels give me > about 120MB/s. Peak perf with all disks active (direct read) is > 175MB/s). > > Any guess where does that 60MB/s/CCD limit comes from ? > > (Performance numbers with vinum also welcome). > > Additional Infos: > 3.2-STABLE, Intel C440GX+ SMP Bi-Xeon 500, 2x3950U2W (channel A used) + > Internal 7896 controller. If you have a C440GX, I think you've only got two PCI busses, not three. From Intel's specs, it looks like it has an onboard 7896, and then one 33MHz bus with 4 slots and one 66MHz bus with 2 slots. They don't indicate which bus the 7896 is on, but my guess is that it's on the 33MHz bus. (The chip can't do 66MHz.) The fact that you can get 175MB/sec out of all the disks simultaneously, without CCD, indicates that it is unlikely that you have a hardware problem. What sort of interleave factor are you using with CCD? You'll want to set the interleave large enough that the transactions are still reasonably sized once they hit the disk. When you're doing I/O benchmarks, you can try looking at the output of 'iostat -d 1'. iostat(8) will give you the average transaction size, and may help you debug your problem. My guess is that changing the interleave factor around might fix things. Also, what are you using to benchmark? I often use iozone for sequential I/O benchmarks... Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 10:28: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ivory.lm.com (ivory.telerama.com [205.201.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 34D2E156B8 for ; Fri, 3 Sep 1999 10:27:49 -0700 (PDT) (envelope-from ncrawler@telerama.com) Received: from gauntlet.telerama.com (ncrawler@gauntlet.telerama.com [205.201.1.214]) by ivory.lm.com (8.8.5/8.6.12) with SMTP id NAA04681; Fri, 3 Sep 1999 13:27:03 -0400 (EDT) Date: Fri, 3 Sep 1999 13:27:02 -0400 (EDT) From: Chris Tracy Reply-To: Chris Tracy To: "Justin T. Gibbs" Cc: scsi@freebsd.org Subject: Re: weird SCSI problems with BT-958 Buslogic card... In-Reply-To: <199908232002.OAA58981@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin, Hiya! I am still having the problem with the 5.06I FW on that BT-958 host adapter. Just thought I'd throw you some more comments.. I thought you might be interested in this, because I have no problems with the 2.2.x BT-958 driver in 3 other machines with nearly the exact same hardware configuration. I was reading throught the archives from awhile back and saw a few threads dealing with this.. in particular...: http://www.freebsd.org/cgi/getmsg.cgi?fetch=677678+680896+/usr/local/www/db/text/1999/freebsd-bugs/19990627.freebsd-bugs http://www.freebsd.org/cgi/getmsg.cgi?fetch=634678+637538+/usr/local/www/db/text/1999/freebsd-questions/19990207.freebsd-questions I was wondering about the second one -- that fix in cam_xpt.c... I tried adding these quirk entries for my seagate drives, which happen to be exactly the same drive as Chuck O'Donnell was using -- the ST34572W and ST34573W, 4GB seagate barracudas. The quirk entries didn't help me.. I also tried adjusting the tagged queueing options and max CCBs in bt.c (i.e., turning off tagged queueing completely / lowering the CCBs to like 32 when it was on,) neither of which helped. So anyways, like I was saying I have 4 machines here -- all of which have nearly the exact same hardware config, that is, a BT-958, and either 1 or 2 4GB seagate barracudas. Three of the machines are running 2.2.x releases (2.2.6/2.2.7) and none have had ANY SCSI problems for over a year or so. Then, I decided I wanted to upgrade just one of these machines to 3.2-STABLE. I wiped the disks and planned to do a clean install of 3.2.. I immediately started having the timeout problems as soon as I booted up with the boot floppies. Eventually I was able to work around this and get the OS installed by putting in a new SCSI disk (another 4GB seagate barracuda actually.) Once the OS was installed, all of our software was setup (just amanda and named.) The machine worked for a while before flaking out like it did, that is, for at least a week or so. I really wish I could take one of the other machine's BT-958 cards and try it in this machine that is flaking, but those servers are all still in production, and it would be bad to take them off-line. So, all of this COULD be because of a faulty SCSI card on my end--I am working to try and get it replaced with an Adaptec 2940UW pro. See ya, -Chris On Mon, 23 Aug 1999, Justin T. Gibbs wrote: > In article you wrote: > > > bt0: rev 0x08 int a irq 11 on > > pci0.11.0 > > bt0: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 > > CCBs > > Try dropping down to the 5.06I FW. You can pick it up from > ftp://ftp.mylex.com/pub/flashbios/wpflash.exe > > The author of the Linux driver reported problems with 5.07B some time > back and 5.06I seems to be a stable release. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 11:35:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dagda.sunflower.com (dagda.sunflower.com [24.124.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A4B7515C06 for ; Fri, 3 Sep 1999 11:35:37 -0700 (PDT) (envelope-from admin@sunflower.com) Received: from sunflower.com (dv099s4.lawrence.ks.us [24.124.4.99]) by dagda.sunflower.com (8.9.1a/8.9.1) with ESMTP id OAA16353 for ; Fri, 3 Sep 1999 14:35:14 -0400 (CDT) Message-ID: <37D01543.14AD6B15@sunflower.com> Date: Fri, 03 Sep 1999 13:36:51 -0500 From: Erik Lindsley X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Question about SCSI error messages.... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I apologize for the newbie-type question, but I have recently "inherited" a BSD system and lately I have been seeing some unexpected errors in the system log files that seem to imply that something in my SCSI disk sysystem is starting to fail. I have attached a copy of the errors to the end of this email. Gradually I have been seeing more and more of these messages, and so I was wondering if this is something to worry about, or if this is within normal operating parameters. The system is running a news server, so disk usage is quite high, but this is the only thing on the box. I am running FreeBSD 2.2-980705-SNAP Any help or suggestions would be greatly appreciated. Sincerely, Erik Lindsley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 11:44: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dagda.sunflower.com (dagda.sunflower.com [24.124.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 336251510D for ; Fri, 3 Sep 1999 11:44:05 -0700 (PDT) (envelope-from admin@sunflower.com) Received: from sunflower.com (dv099s4.lawrence.ks.us [24.124.4.99]) by dagda.sunflower.com (8.9.1a/8.9.1) with ESMTP id OAA17427 for ; Fri, 3 Sep 1999 14:41:59 -0400 (CDT) Message-ID: <37D016D9.218DFF2@sunflower.com> Date: Fri, 03 Sep 1999 13:43:37 -0500 From: Erik Lindsley X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Question about SCSI error messages.... (The error messages) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > (da3:ahc0:0:3:0): SCB 0xb - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR == 0x10d > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): BDR message in message buffer > (da3:ahc0:0:3:0): SCB 0xb - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR == 0x10e > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 135 SCBs aborted > (da3:ahc0:0:3:0): SCB 0x7d - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR == 0x10e > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): BDR message in message buffer > (da3:ahc0:0:3:0): SCB 0x7d - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR == 0x10d > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 3 SCBs aborted > (da3:ahc0:0:3:0): SCB 0x18 - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR == 0x10d > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): BDR message in message buffer > (da3:ahc0:0:3:0): SCB 0x18 - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR == 0x10e > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > (da3:ahc0:0:3:0): SCB 0x1a - timed out in datain phase, SCSISIGI == 0x44 > (da3:ahc0:0:3:0): SCB 0x1a - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR == 0x10e > SSTAT1 == 0x2 > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 12 SCBs aborted > (da3:ahc0:0:3:0): SCB 0x1e - timed out in datain phase, SCSISIGI == 0x44 > (da3:ahc0:0:3:0): BDR message in message buffer > (da3:ahc0:0:3:0): SCB 0x1e - timed out in datain phase, SCSISIGI == 0x54 > SEQADDR == 0x10e > SSTAT1 == 0x2 > ahc0: Issued Channel A Bus Reset. 26 SCBs aborted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 12:46:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id DC91D151F9 for ; Fri, 3 Sep 1999 12:46:38 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA16170; Fri, 3 Sep 1999 13:45:56 -0600 (MDT) (envelope-from ken) Message-Id: <199909031945.NAA16170@panzer.kdm.org> Subject: Re: Question about SCSI error messages.... (The error messages) In-Reply-To: <37D016D9.218DFF2@sunflower.com> from Erik Lindsley at "Sep 3, 1999 01:43:37 pm" To: admin@sunflower.com (Erik Lindsley) Date: Fri, 3 Sep 1999 13:45:56 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Erik Lindsley wrote... > > (da3:ahc0:0:3:0): SCB 0xb - timed out in datain phase, SCSISIGI == 0x44 > > SEQADDR == 0x10d > > SSTAT1 == 0x2 > > (da3:ahc0:0:3:0): BDR message in message buffer > > (da3:ahc0:0:3:0): SCB 0xb - timed out in datain phase, SCSISIGI == 0x54 > > SEQADDR == 0x10e > > SSTAT1 == 0x2 > > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 135 SCBs aborted > > (da3:ahc0:0:3:0): SCB 0x7d - timed out in datain phase, SCSISIGI == 0x44 > > SEQADDR == 0x10e > > SSTAT1 == 0x2 > > (da3:ahc0:0:3:0): BDR message in message buffer > > (da3:ahc0:0:3:0): SCB 0x7d - timed out in datain phase, SCSISIGI == 0x54 > > SEQADDR == 0x10d > > SSTAT1 == 0x2 > > (da3:ahc0:0:3:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 3 SCBs aborted > > (da3:ahc0:0:3:0): SCB 0x18 - timed out in datain phase, SCSISIGI == 0x44 > > SEQADDR == 0x10d > > SSTAT1 == 0x2 You've most likely got a cabling or termination problem. So, check your cables and termination. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 13:56:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id C7EB8150E8 for ; Fri, 3 Sep 1999 13:55:43 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA64716; Fri, 3 Sep 1999 13:53:48 -0700 (PDT) Date: Fri, 3 Sep 1999 13:54:53 -0700 (PDT) From: Julian Elischer To: Erik Lindsley Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Question about SCSI error messages.... In-Reply-To: <37D01543.14AD6B15@sunflower.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You say you are running 2.2 but you have 'da' devices.. hmm anyhow it does sound like a disk (da3 seems the likely candidate) goues out to lunch occasionally. I presume you've checked all the terminators etc? disks are cheap these days.. replace it also wait for a comment from Ken or Justin, as this is their baby :-) On Fri, 3 Sep 1999, Erik Lindsley wrote: > Greetings, > I apologize for the newbie-type question, but I have recently > "inherited" a BSD system and lately I have been seeing some unexpected > errors in the system log files that seem to imply that something in my > SCSI disk sysystem is starting to fail. I have attached a copy of the > errors to the end of this email. Gradually I have been seeing more and > more of these messages, and so I was wondering if this is something to > worry about, or if this is within normal operating parameters. > > The system is running a news server, so disk usage is quite high, but > this is the only thing on the box. I am running FreeBSD 2.2-980705-SNAP > > Any help or suggestions would be greatly appreciated. > > Sincerely, > Erik Lindsley > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 14:16: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 013DF14C96 for ; Fri, 3 Sep 1999 14:15:57 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com for ; Fri, 3 Sep 1999 14:15:52 -0700 From: "David Schwartz" To: Subject: Probably ahc hardware problem. Date: Fri, 3 Sep 1999 14:15:52 -0700 Message-ID: <000001bef651$80ba7600$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I havee 3.2-STABLE as of about a day ago. With a 2940U controller: ahc0: rev 0x01 int a irq 11 on pci0.16.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs And I'm seeing this, along with some data corruption: (da0:ahc0:0:0:0): SCB 0x11 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 31 SCBs aborted (da0:ahc0:0:0:0): SCB 0x15 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 31 SCBs aborted Does this sound like a controller/motherboard problem or a drive problem? Please CC me as I'm not subscribed to the list. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 14:58:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id BCB4314CC1 for ; Fri, 3 Sep 1999 14:58:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA16972; Fri, 3 Sep 1999 15:58:50 -0600 (MDT) (envelope-from ken) Message-Id: <199909032158.PAA16972@panzer.kdm.org> Subject: Re: Probably ahc hardware problem. In-Reply-To: <000001bef651$80ba7600$021d85d1@youwant.to> from David Schwartz at "Sep 3, 1999 02:15:52 pm" To: davids@webmaster.com (David Schwartz) Date: Fri, 3 Sep 1999 15:58:50 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Schwartz wrote... > > I havee 3.2-STABLE as of about a day ago. With a 2940U controller: > > ahc0: rev 0x01 int a irq 11 on pci0.16.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > And I'm seeing this, along with some data corruption: > > (da0:ahc0:0:0:0): SCB 0x11 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > 0xc > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset on A:0. 31 SCBs aborted > (da0:ahc0:0:0:0): SCB 0x15 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > 0x9 > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Bus Device Reset on A:0. 31 SCBs aborted > > Does this sound like a controller/motherboard problem or a drive problem? > Please CC me as I'm not subscribed to the list. You omitted one critical piece of information. What kind of drive is it? This is likely a drive firmware problem. This commonly happens with Quantum Atlas I and II drives, and can generally be fixed by upgrading the firmware. It's also possible, of course, for it to happen on other types of drives as well. What the "timed out while idle" message means is that a command from the da driver timed out, and there was nothing else going on at the time. This generally means the drive has gone "out to lunch" and hasn't come back. The timeout for the da driver is 60 seconds, so it's highly unlikely that your drive just wasn't able to respond in time. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 15: 2:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E9A6014BF5 for ; Fri, 3 Sep 1999 15:02:18 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA17010; Fri, 3 Sep 1999 16:01:39 -0600 (MDT) (envelope-from ken) Message-Id: <199909032201.QAA17010@panzer.kdm.org> Subject: Re: Question about SCSI error messages.... In-Reply-To: from Julian Elischer at "Sep 3, 1999 01:54:53 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 3 Sep 1999 16:01:39 -0600 (MDT) Cc: admin@sunflower.com (Erik Lindsley), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote... > You say you are running 2.2 but you have 'da' devices.. > > hmm It is possible for him to be running a 2.2 release with CAM in it. We released a number of sets of CAM patches against the 2.2 tree before 3.0 came out last year. > anyhow it does sound like a disk (da3 seems the likely candidate) goues > out to lunch occasionally. I presume you've checked all the terminators > etc? I think in this case it's cabling or termination. (Timed out in {datain,dataout,command} phase errors generally indicate cabling or termination problems. Timed out while idle problems are most frequently drive firmware problems, but can just indicate that a timeout is set too short, or that there's some other problem.) > On Fri, 3 Sep 1999, Erik Lindsley wrote: > > > Greetings, > > I apologize for the newbie-type question, but I have recently > > "inherited" a BSD system and lately I have been seeing some unexpected > > errors in the system log files that seem to imply that something in my > > SCSI disk sysystem is starting to fail. I have attached a copy of the > > errors to the end of this email. Gradually I have been seeing more and > > more of these messages, and so I was wondering if this is something to > > worry about, or if this is within normal operating parameters. > > > > The system is running a news server, so disk usage is quite high, but > > this is the only thing on the box. I am running FreeBSD 2.2-980705-SNAP > > > > Any help or suggestions would be greatly appreciated. > > > > Sincerely, > > Erik Lindsley > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 15: 9:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id EB89B151F2 for ; Fri, 3 Sep 1999 15:09:51 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id QAA23271; Fri, 3 Sep 1999 16:07:36 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909032207.QAA23271@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Tracy Cc: "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: weird SCSI problems with BT-958 Buslogic card... In-reply-to: Your message of "Fri, 03 Sep 1999 13:27:02 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Sep 1999 16:07:36 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Justin, > > Hiya! I am still having the problem with the 5.06I FW on that >BT-958 host adapter. Just thought I'd throw you some more comments.. I >thought you might be interested in this, because I have no problems with >the 2.2.x BT-958 driver in 3 other machines with nearly the exact same >hardware configuration. There are several differences between the old and new driver above and beyond the tagged queuing stuff. For instance, we use a different command opcode than the old driver. Unfortunately I only have a BT-946C to test with and it is not as fast or feature rich as either the 948 or 958 cards. Its hard to debug things like this without being able to reproduce them. If you do end up replacing the card with something else, do you think you could loan it to me for a week or so? I'm sure that I could isolate the bug quickly once I can reproduce it. Here's my shipping address: Justin T. Gibbs C/O Pluto Technologies International Inc. 2511 55th. St. Boulder, CO 80301 -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 3 15:16:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 82262156DD for ; Fri, 3 Sep 1999 15:16:15 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA17118; Fri, 3 Sep 1999 16:15:50 -0600 (MDT) (envelope-from ken) Message-Id: <199909032215.QAA17118@panzer.kdm.org> Subject: Re: Probably ahc hardware problem. In-Reply-To: <000001bef658$695f97e0$021d85d1@youwant.to> from David Schwartz at "Sep 3, 1999 03:05:19 pm" To: davids@webmaster.com (David Schwartz) Date: Fri, 3 Sep 1999 16:15:49 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ CCing my reply to the -scsi list, I hope you don't mind, but I think other folks might be interested in this ] David Schwartz wrote... > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 4096MB (8388608 512 byte sectors: 255H 63S/T 522C) > > It's also known as the ST14207N. > > Do you think I need a firmware upgrade? Maybe it's a heat problem? Or power > supply stability causing the drive to zonk out? I've seen other Conner drives that have problems doing tagged queueing. (The Conner CFP 2107 is quirked in the transport layer.) A firmware lockup is possible if they don't handle tagged queueing properly. Here's a quick way to figure out whether that's the problem: camcontrol negotiate da0 -T disable -v -a That should disable tagged queueing for that drive. Then try pounding the drive again, and see if the problem returns. If not, you can then try re-enabling tagged queueing (by changing the 'disable' in the above command to 'enable') and using the 'camcontrol tags' command to adjust the number of tags allowed for that device. Some drives only reliably handle a few concurrent transactions, and some don't handle tagged queueing well at all. It may be that your drive will handle only a few, and you may be able to determine what the maximum number is through experimentation. It also may be that tagged queueing doesn't work well at all for that drive, and so should be disabled. In any case, try the above experiment and see what happens. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 4 11: 6:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id E94C9155E8; Sat, 4 Sep 1999 11:06:13 -0700 (PDT) (envelope-from rene@canyon.demon.nl) Received: from [212.238.15.212] (helo=canyon.demon.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11NKCM-0001hi-00; Sat, 4 Sep 1999 18:05:59 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id UAA01156; Sat, 4 Sep 1999 20:05:01 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199909041805.UAA01156@canyon.demon.nl> Subject: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic To: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Date: Sat, 4 Sep 1999 20:05:01 +0200 (CEST) Cc: wilko@yedi.iaf.nl (Wilko Bulte) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Today I bought a Umax 1220S scanner and tried to connect this to my FreeBSD Stable (3.3RC) system. I added a NCR810 specially for the scanner (I don't want such a device on the same bus as my root disk which is on an aic7890). The kernel boots perfectly with both scsi adapters configured (as expected ;-), but as soon as the scanner is connected to the NCR810 the kernel panics. The scanner is the only device on that bus and termination is ok. The message is: "cam_periph_error: scsi status of CHECK COND returned but no sense information is availible. Controller should have returned CAM_AUTOSENSE_FAILED" (line 1441 of cam_periph.c). As far as understand the comments there, this means that the ncr810 driver did something cam did not expect. (This all happens during booting, at the time when the devices are probed.) For now I've connected the scanner to my other PC running W95 where its seems to work as expected. I hope someone can help me finding what the problem is and how to fix it. Thanks, Rene -- Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 4 11:12:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id BE39315807; Sat, 4 Sep 1999 11:12:27 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (599 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 4 Sep 1999 11:11:27 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 4 Sep 1999 11:11:27 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Rene de Vries Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic References: <199909041805.UAA01156@canyon.demon.nl> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Today I bought a Umax 1220S scanner so did i. it did not even work on win95. after rmaing it twice, i told them to keep the piece of and went out and got a better product. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 4 16:53:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4F9B815232; Sat, 4 Sep 1999 16:53:31 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA27822; Sat, 4 Sep 1999 17:52:47 -0600 (MDT) (envelope-from ken) Message-Id: <199909042352.RAA27822@panzer.kdm.org> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909041805.UAA01156@canyon.demon.nl> from Rene de Vries at "Sep 4, 1999 08:05:01 pm" To: rene@canyon.demon.nl (Rene de Vries) Date: Sat, 4 Sep 1999 17:52:47 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, wilko@yedi.iaf.nl (Wilko Bulte) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rene de Vries wrote... > Hi, > > Today I bought a Umax 1220S scanner and tried to connect this to my FreeBSD > Stable (3.3RC) system. I added a NCR810 specially for the scanner (I don't > want such a device on the same bus as my root disk which is on an aic7890). > The kernel boots perfectly with both scsi adapters configured > (as expected ;-), but as soon as the scanner is connected to the NCR810 > the kernel panics. > The scanner is the only device on that bus and termination is ok. > The message is: "cam_periph_error: scsi status of CHECK COND returned but no > sense information is availible. Controller should have returned > CAM_AUTOSENSE_FAILED" (line 1441 of cam_periph.c). As far as understand the > comments there, this means that the ncr810 driver did something cam did not > expect. (This all happens during booting, at the time when the devices are > probed.) > For now I've connected the scanner to my other PC running W95 where its > seems to work as expected. > I hope someone can help me finding what the problem is and how to fix it. It sounds like there may be a couple of things going on. First, your scanner may not be returning sense information properly. Second, the NCR driver may be doing something wrong. It would be helpful if you could hook this up to your 7890 controller and see what happens. In general, the Adaptec driver behaves a little better than the NCR driver. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 4 22:43: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 8371714EF7 for ; Sat, 4 Sep 1999 22:43:02 -0700 (PDT) (envelope-from clash@tasam.com) Received: from bug (hc6526b25.dhcp.vt.edu [198.82.107.37]) by tasam.com (8.9.3/8.9.3) with SMTP id BAA68827 for ; Sun, 5 Sep 1999 01:42:41 -0400 (EDT) (envelope-from clash@tasam.com) Message-ID: <00f801bef761$7985e8e0$256b52c6@tasam.com> From: "Joe Gleason" To: Subject: Infortrend IFT-2101U2x support? Date: Sun, 5 Sep 1999 01:42:30 -0400 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know is the Infortrend IFT-2101U2A or IFT-2101U2B is supported under -STABLE or -CURRENT? I don't see it on the hardware list for 3.2-R and I couldn't find any mention in any of the lists. I figured I should ask. http://www.infortrend.com/2101u2.htm For people who don't want to open a browser, this is a PCI-SCSI adapter. It does RAID and Ultra2 Wide. Does anyone know a good place to buy infortrend products? I will probably be suggesting either the above card or one of their SCSI-SCSI raid products to a client. Joe Gleason Tasam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message