From owner-freebsd-scsi Mon Jan 24 3: 1:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 2E12914A2E for ; Mon, 24 Jan 2000 03:01:34 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id KAA01238 for ; Mon, 24 Jan 2000 10:36:49 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 24 Jan 2000 10:36:48 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD SCSI Mailing List Subject: bug in cam_periph.c 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 the following diff code does not make sense to me. first check for a retry count larger than zero and return EIO when it is. I guess that this piee of code has not been exercised very much, because changing it did not make a difference for the SCSI devices I have here. } else if (ccb->ccb_h.retry_count > 0) { /* * XXX KDM shouldn't there be a better * argument to return?? */ error = EIO; } else { /* decrement the number of retries */ retry = ccb->ccb_h.retry_count > 0; if (retry) ccb->ccb_h.retry_count--; /* * If it was aborted with no * clue as to the reason, just * retry it again. */ error = ERESTART; } Patch below: --- cam_periph.c.orig Mon Jan 24 10:34:23 2000 +++ cam_periph.c Mon Jan 24 10:34:27 2000 @@ -1439,7 +1439,7 @@ "CAM_AUTOSENSE_FAILED"); /* NOTREACHED */ error = EIO; - } else if (ccb->ccb_h.retry_count > 0) { + } else if (ccb->ccb_h.retry_count == 0) { /* * XXX KDM shouldn't there be a better * argument to return?? -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 6:29: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1AC6614BFE for ; Mon, 24 Jan 2000 06:29:02 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id GAA23104; Mon, 24 Jan 2000 06:28:54 -0800 Date: Mon, 24 Jan 2000 06:28:52 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: bug in cam_periph.c In-Reply-To: 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're right that the existing code makes no sense. This is actually an area which needs some serious work, but hasn't been excercised much because we don't have HBA's that don't do some form of autosense or self-autosense. In my opinion, you're patch is logically right, but the whole block is not quite right- if auto sense failed, the midlayer should run a SENSE command, else the command should, I guess, be retried if retries are left. On Mon, 24 Jan 2000, Nick Hibma wrote: > > the following diff code does not make sense to me. first check for a > retry count larger than zero and return EIO when it is. I guess that > this piee of code has not been exercised very much, because changing it > did not make a difference for the SCSI devices I have here. > > > } else if (ccb->ccb_h.retry_count > 0) { > /* > * XXX KDM shouldn't there be a better > * argument to return?? > */ > error = EIO; > } else { > /* decrement the number of retries */ > retry = ccb->ccb_h.retry_count > 0; > if (retry) > ccb->ccb_h.retry_count--; > /* > * If it was aborted with no > * clue as to the reason, just > * retry it again. > */ > error = ERESTART; > } > > > > > Patch below: > > --- cam_periph.c.orig Mon Jan 24 10:34:23 2000 > +++ cam_periph.c Mon Jan 24 10:34:27 2000 > @@ -1439,7 +1439,7 @@ > "CAM_AUTOSENSE_FAILED"); > /* NOTREACHED */ > error = EIO; > - } else if (ccb->ccb_h.retry_count > 0) { > + } else if (ccb->ccb_h.retry_count == 0) { > /* > * XXX KDM shouldn't there be a better > * argument to return?? > > -- > n_hibma@webweaving.org > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > > > 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 Mon Jan 24 7: 5: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 637FE14F16 for ; Mon, 24 Jan 2000 07:05:00 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.155]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA24EB for ; Mon, 24 Jan 2000 16:04:57 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id QAA04164 for scsi@freebsd.org; Mon, 24 Jan 2000 16:04:34 +0100 (CET) (envelope-from asmodai) Date: Mon, 24 Jan 2000 16:04:34 +0100 From: Jeroen Ruigrok/Asmodai To: scsi@freebsd.org Subject: Need some real good advice to track this problem down Message-ID: <20000124160434.D691@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth (and probably Matthew or Justin) might remember, I had some trouble with unexpected busfrees about a year ago. I have been having them every once in a while since I wasn't that clued on SCSI, I have now been doing some reading up on the subject and present some information on which I need some expert help. This is an `old' system, back from 1996. The mainboard is a Diamond Flow, Inc. (DFI) board G185IPV - rev C+, which has 96 MB in SIMMs, a Pentium 200MMX (which is not overclocked). Two NICs (ep0 and fxp0), a Tseng vidcard, an AWE-32 and that's it basically. The host controller is an AHC2940UW from 1996. The BIOS version was 1.23, and I flashed it (successfully) to 2.20 last night. This is not an OEM card, but a real original Adaptec card. I have had the problems with both versions of the BIOS. The SCSI layout is as fllows: | The length of this cable is 1.35 meters and has 6 connectors |--------|-------|-------|-------|------| (Narrow (50-pins) bus) | 39 cm 24 24 24 24 AHC| | 50 cm 20 |------------------|-------------------| (Wide (68-pins) bus) | The length of this one is 70 cm and has three connectors On the narrow bus we have: [from card to outer device] AHC----disk1----disk2-----cdrom----empty------term AHC = AHC2940UW disk1 = 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: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) Verified that no jumpers are set to termination. disk2 = da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 6149MB (12594960 512 byte sectors: 255H 63S/T 784C) Verified that no jumpers are set to termination. The cdrom = cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Verified that no jumpers are set to termination. It does have a jumper on allow/prevent (which I still don't know what it is) and Parity (which I believe is necessary). Then one empty connector and then followed by an _active_ terminator. (Which I bought on Kenneth's advice I think after he mentioned that cdrom drives sometimes suck with their termination.) On the wide bus we have: [from card to outer device] AHC---------disk3-------disk4 AHC=the same as above disk3 = da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) This drive has absolutely _no_ jumpers set. disk4 = da3 at ahc0 bus 0 target 4 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 2047MB (4194057 512 byte sectors: 255H 63S/T 261C) This drive has Term Enable, Term From Drive and Term To Bus set. I was getting these messages randomly over time: Jan 14 11:37:44 daemon /kernel: Unexpected busfree. LASTPHASE == 0x40 Jan 14 11:37:44 daemon /kernel: SEQADDR == 0x110 Jan 14 11:38:12 daemon /kernel: Unexpected busfree. LASTPHASE == 0x40 Jan 14 11:38:13 daemon /kernel: SEQADDR == 0x110 Jan 22 13:42:55 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:42:55 daemon /kernel: SEQADDR == 0x112 Jan 22 13:43:23 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:43:23 daemon /kernel: SEQADDR == 0x112 Jan 22 13:45:04 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:45:04 daemon /kernel: SEQADDR == 0x112 Jan 23 19:33:24 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:33:25 daemon /kernel: SEQADDR == 0x113 Jan 23 19:34:11 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:34:11 daemon /kernel: SEQADDR == 0x112 Jan 23 19:34:49 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:34:50 daemon /kernel: SEQADDR == 0x112 Jan 23 19:35:47 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:35:47 daemon /kernel: SEQADDR == 0x113 Jan 23 19:36:15 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:36:16 daemon /kernel: SEQADDR == 0x112 Jan 23 19:46:55 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:46:56 daemon /kernel: SEQADDR == 0x112 Jan 23 19:47:25 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:47:25 daemon /kernel: SEQADDR == 0x112 Jan 23 19:47:57 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:47:57 daemon /kernel: SEQADDR == 0x113 Jan 23 19:48:46 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:48:47 daemon /kernel: SEQADDR == 0x113 Jan 23 19:49:23 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:49:24 daemon /kernel: SEQADDR == 0x79 Jan 23 19:49:52 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:49:52 daemon /kernel: SEQADDR == 0x113 I then wanted to test the new BIOS v2.20 and decided on rawio on da3 which is empty, so I did a rawio -a /dev/da3: Jan 24 15:07:37 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:07:38 daemon /kernel: SEQADDR == 0x112 Jan 24 15:07:50 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:07:50 daemon /kernel: SEQADDR == 0x112 Jan 24 15:08:01 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:02 daemon /kernel: SEQADDR == 0x113 Jan 24 15:08:02 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack Jan 24 15:08:13 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:13 daemon /kernel: SEQADDR == 0x112 Jan 24 15:08:24 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:25 daemon /kernel: SEQADDR == 0x113 Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Synchronize cache failed, status == 0x4a, scsi status == 0x0 I also tried changing the AHC2940UW with a spare AHC2940U2W, but I get the same problems. I hope this is enough information, please let me know if I need to test other things. I really want to know what on earth I am doing wrong here. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project I accept that some things will never change, I've let your tiny minds magnify my agony... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 7:35:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 8840615A62 for ; Mon, 24 Jan 2000 07:35:49 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id PAA01515; Mon, 24 Jan 2000 15:24:03 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 24 Jan 2000 15:24:02 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Matthew Jacob Cc: FreeBSD SCSI Mailing List Subject: Re: bug in cam_periph.c In-Reply-To: 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 I found the code while implementing the autosense in software in the umass driver. This is true for the vpo driver as well. You are basically saying that we could implement the sense command there. Except that of course for example from scsi_da.c that generic routine is never called. It relies on autosense I believe. Nick On Mon, 24 Jan 2000, Matthew Jacob wrote: > You're right that the existing code makes no sense. This is actually an area > which needs some serious work, but hasn't been excercised much because we > don't have HBA's that don't do some form of autosense or self-autosense. > > In my opinion, you're patch is logically right, but the whole block is not > quite right- if auto sense failed, the midlayer should run a SENSE command, > else the command should, I guess, be retried if retries are left. > > > > On Mon, 24 Jan 2000, Nick Hibma wrote: > > > > > the following diff code does not make sense to me. first check for a > > retry count larger than zero and return EIO when it is. I guess that > > this piee of code has not been exercised very much, because changing it > > did not make a difference for the SCSI devices I have here. > > > > > > } else if (ccb->ccb_h.retry_count > 0) { > > /* > > * XXX KDM shouldn't there be a better > > * argument to return?? > > */ > > error = EIO; > > } else { > > /* decrement the number of retries */ > > retry = ccb->ccb_h.retry_count > 0; > > if (retry) > > ccb->ccb_h.retry_count--; > > /* > > * If it was aborted with no > > * clue as to the reason, just > > * retry it again. > > */ > > error = ERESTART; > > } > > > > > > > > > > Patch below: > > > > --- cam_periph.c.orig Mon Jan 24 10:34:23 2000 > > +++ cam_periph.c Mon Jan 24 10:34:27 2000 > > @@ -1439,7 +1439,7 @@ > > "CAM_AUTOSENSE_FAILED"); > > /* NOTREACHED */ > > error = EIO; > > - } else if (ccb->ccb_h.retry_count > 0) { > > + } else if (ccb->ccb_h.retry_count == 0) { > > /* > > * XXX KDM shouldn't there be a better > > * argument to return?? > > > > -- > > n_hibma@webweaving.org > > n_hibma@freebsd.org USB project > > http://www.etla.net/~n_hibma/ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 9:10:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E2D215A9B for ; Mon, 24 Jan 2000 09:10:50 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA23683; Mon, 24 Jan 2000 09:10:46 -0800 Date: Mon, 24 Jan 2000 09:10:43 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: bug in cam_periph.c In-Reply-To: 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 On Mon, 24 Jan 2000, Nick Hibma wrote: > > I found the code while implementing the autosense in software in the > umass driver. This is true for the vpo driver as well. > > You are basically saying that we could implement the sense command > there. Except that of course for example from scsi_da.c that generic > routine is never called. It relies on autosense I believe. Not 'could'- 'should'. Right now we have to have all sim drivers implement autosense their own way- big PITA if not done in H/W-F/W. Even drivers that normally could do autosense can't always do so. The Qlogic 2X00 Fibre Channel card is one example- if the target doesn't set Sense Valid in the FCP Response, the 2X00 won't automatically run a REQUEST SENSE to fill in the needed sense data if the scsi status was CHECK CONDITION- unlike the parallel SCSI versions from the same vendor. Not *usually* a problem because it's usually set and filled in, but there are cases where it isn't (look at FreeBSD's own scsi_target.c as an example). It's possible that periph_error isn't the right place to do this, but it's probably the best place to do this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 12:24: 6 2000 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 8AE25152C2 for ; Mon, 24 Jan 2000 12:24:03 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id NAA22362; Mon, 24 Jan 2000 13:10:22 -0700 (MST) Date: Mon, 24 Jan 2000 13:10:22 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200001242010.NAA22362@narnia.plutotech.com> To: Jeroen Ruigrok/Asmodai Cc: scsi@FreeBSD.org Subject: Re: Need some real good advice to track this problem down X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <20000124160434.D691@daemon.ninth-circle.org> 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 <20000124160434.D691@daemon.ninth-circle.org> you wrote: > > Then one empty connector and then followed by an _active_ terminator. > (Which I bought on Kenneth's advice I think after he mentioned that > cdrom drives sometimes suck with their termination.) I would probably be better to spread your devices across the whole bus then to have this dangling stub. Can you put one of your hard-drives on the end instead of using the external terminator? > disk4 = > da3 at ahc0 bus 0 target 4 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da3: 2047MB (4194057 512 byte sectors: 255H 63S/T 261C) > This drive has Term Enable, Term From Drive and Term To Bus set. You should not set "TP to bus". The controller is providing termination power and only once source is required. > Jan 24 15:08:13 daemon /kernel: SEQADDR == 0x112 > Jan 24 15:08:24 daemon /kernel: Unexpected busfree in Data-in phase > Jan 24 15:08:25 daemon /kernel: SEQADDR == 0x113 > Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack > Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Synchronize cache > failed, status == 0x4a, scsi status == 0x0 It looks like da3 may be the culprit. Even with a degraded bus, it is rare that a device will fail a selection. Are you sure that this device is running cool enough? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 12:47: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id CE37314EBA for ; Mon, 24 Jan 2000 12:46:58 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.28]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2203; Mon, 24 Jan 2000 21:46:54 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA05780; Mon, 24 Jan 2000 21:46:46 +0100 (CET) (envelope-from asmodai) Date: Mon, 24 Jan 2000 21:46:46 +0100 From: Jeroen Ruigrok/Asmodai To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Need some real good advice to track this problem down Message-ID: <20000124214646.D4731@daemon.ninth-circle.org> References: <20000124160434.D691@daemon.ninth-circle.org> <200001242010.NAA22362@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001242010.NAA22362@narnia.plutotech.com>; from gibbs@narnia.plutotech.com on Mon, Jan 24, 2000 at 01:10:22PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000124 21:28], Justin T. Gibbs (gibbs@narnia.plutotech.com) wrote: >In article <20000124160434.D691@daemon.ninth-circle.org> you wrote: >> >> Then one empty connector and then followed by an _active_ terminator. >> (Which I bought on Kenneth's advice I think after he mentioned that >> cdrom drives sometimes suck with their termination.) > >I would probably be better to spread your devices across the whole >bus then to have this dangling stub. Can you put one of your >hard-drives on the end instead of using the external terminator? Not easily. It's a bigtower with the AHC in the bottom of the tower, and then going up to the HD's and then to the CD-ROM drive, and that resulted in me buying an active terminator. >> disk4 = >> da3 at ahc0 bus 0 target 4 lun 0 >> da3: Fixed Direct Access SCSI-2 device >> da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing >> Enabled >> da3: 2047MB (4194057 512 byte sectors: 255H 63S/T 261C) >> This drive has Term Enable, Term From Drive and Term To Bus set. > >You should not set "TP to bus". The controller is providing termination >power and only once source is required. Ahhh ok, going to get this off... This might be the solution [hopefully]. I am not going to hold my breath though. =) >> Jan 24 15:08:13 daemon /kernel: SEQADDR == 0x112 >> Jan 24 15:08:24 daemon /kernel: Unexpected busfree in Data-in phase >> Jan 24 15:08:25 daemon /kernel: SEQADDR == 0x113 >> Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack >> Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Synchronize cache >> failed, status == 0x4a, scsi status == 0x0 > >It looks like da3 may be the culprit. Even with a degraded bus, >it is rare that a device will fail a selection. Are you sure >that this device is running cool enough? The airflow seems ok, the fresh air gets sucked in through the bottom, just below the drives, by means of a fan. And two fans near the top of the tower blow out the hot air. That should create a logical airflow. Thanks, I am going to get that jumper off and try rawio again. And else I'll have to buy something like a fancard to cool the box well enough, should that be it. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Another morning, black sunday, coming down again... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 24 13:23:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 83F3714D4D for ; Mon, 24 Jan 2000 13:23:44 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.138]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4257; Mon, 24 Jan 2000 22:20:11 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id WAA00486; Mon, 24 Jan 2000 22:19:58 +0100 (CET) (envelope-from asmodai) Date: Mon, 24 Jan 2000 22:19:57 +0100 From: Jeroen Ruigrok/Asmodai To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Need some real good advice to track this problem down Message-ID: <20000124221957.A290@daemon.ninth-circle.org> References: <20000124160434.D691@daemon.ninth-circle.org> <200001242010.NAA22362@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001242010.NAA22362@narnia.plutotech.com>; from gibbs@narnia.plutotech.com on Mon, Jan 24, 2000 at 01:10:22PM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000124 21:28], Justin T. Gibbs (gibbs@narnia.plutotech.com) wrote: >In article <20000124160434.D691@daemon.ninth-circle.org> you wrote: >> >> disk4 = >> da3 at ahc0 bus 0 target 4 lun 0 >> da3: Fixed Direct Access SCSI-2 device >> da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing >> Enabled >> da3: 2047MB (4194057 512 byte sectors: 255H 63S/T 261C) >> This drive has Term Enable, Term From Drive and Term To Bus set. > >You should not set "TP to bus". The controller is providing termination >power and only once source is required. Fixed the jumpers on da2, see below. >> Jan 24 15:08:13 daemon /kernel: SEQADDR == 0x112 >> Jan 24 15:08:24 daemon /kernel: Unexpected busfree in Data-in phase >> Jan 24 15:08:25 daemon /kernel: SEQADDR == 0x113 >> Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack >> Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Synchronize cache >> failed, status == 0x4a, scsi status == 0x0 > >It looks like da3 may be the culprit. Even with a degraded bus, >it is rare that a device will fail a selection. Are you sure >that this device is running cool enough? Well, the airflow is good, seems that the drives don't get cooled enough in their current position. I removed da3 from the chain, and moved da2 to the outer position and set it to term and term from drive. Now lets see how this behaves. I will be looking at something to cool the drives better. Any suggestions are of course welcome to improve this. I cannot at the moment place any HD at the end of the other chain since those are 3.5" drives and the mount area is 5.25", so I need to get some mount brackets before I can attempt this. Another mistake on my part, it is empty stub---cdrom----terminator, not what I said earlier: cdrom----empty stub----terminator. Thanks, -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project How the gods kill... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 25 8:58:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 84B3A1527F for ; Tue, 25 Jan 2000 08:58:16 -0800 (PST) (envelope-from girgen@partitur.se) Received: from elbas.partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id RAA10481; Tue, 25 Jan 2000 17:57:50 +0100 (CET) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by elbas.partitur.se (8.9.3/8.9.3) with ESMTP id RAA38590; Tue, 25 Jan 2000 17:57:49 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <388DD60D.B33EAF26@partitur.se> Date: Tue, 25 Jan 2000 17:57:49 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: cannot mt retension (seagate python) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I have a Seagate Python (DSS-20) tape streamer, and it won't accept a retension command. Well, it accepts it, but nothing happens. Any ideas why this is so? This is what happens: $ mt ret $ <---- immediately, I get a fresh prompt. nothing happens. I doesn't matter how much or little data there is on the tape. FreeBSD 3.3-RELEASE, adaptec 1540CS scsi card. If you need more input, don't hesitate to ask. Cheers, Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 25 9:22: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from infosite.com (infosite.com [207.173.133.50]) by hub.freebsd.org (Postfix) with ESMTP id B244114EB6 for ; Tue, 25 Jan 2000 09:21:58 -0800 (PST) (envelope-from lukeunix@infosite.com) Received: (from lukeunix@localhost) by infosite.com (8.9.1/8.9.1) id JAA32558 for freebsd-scsi@freebsd.org; Tue, 25 Jan 2000 09:21:52 -0800 (PST) From: LukeUnix Message-Id: <200001251721.JAA32558@infosite.com> Subject: CMD problems To: freebsd-scsi@freebsd.org Date: Tue, 25 Jan 2000 09:21:52 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL40 (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 I am having problems with a CMD CRD-5440 with multiple luns. The config is 2 drive trays, each on their own channel on the CMD, and one host channel to the FreeBSD 3.4 box. I was not experiencing these problems untill the 2nd drive tray was added, making the CMD use 2 luns. So far I have tried to set the number of max tags by editing sys/cam/cam_xpt.c and adding the following entry. /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, "CMD TECH", "CRD-5440*", "*" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 That does not seem to have helped.. The following are scsi errors I am seeing. /kernel: (da2:ahc1:0:1:0): SCB 0x18 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b /kernel: ahc1: Bus Device Reset on A:1. 2 SCBs aborted /kernel: (da2:ahc1:0:1:0): SCB 0x28 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b /kernel: ahc1: Bus Device Reset on A:1. 31 SCBs aborted Some info on the system.. at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 2 lun 0 (pass1,da1) at scbus1 target 1 lun 0 (pass2,da2) at scbus1 target 1 lun 1 (pass3,da3) at scbus2 target 0 lun 0 (pass4,da4) at scbus2 target 1 lun 0 (pass5,da5) fxp0: rev 0x02 int a irq 10 on pci0.6.0 fxp0: Ethernet address 00:a0:c9:55:fe:eb chip1: rev 0x01 on pci0.7.0 ahc0: rev 0x00 int a irq 11 on pci0.9.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs chip2: rev 0x02 on pci0.11.0 fxp1: rev 0x01 int a irq 11 on pci0.15.0 fxp1: Ethernet address 00:a0:c9:27:cd:1d vga0: rev 0xd3 int a irq 11 on pci0.19.0 Probing for devices on PCI bus 1: ahc1: rev 0x00 int a irq 11 on pci1.4.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: rev 0x00 int a irq 11 on pci1.5.0 ahc2: aic7880 Wide Channel B, SCSI Id=7, 16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da4 at ahc2 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4340MB (8888543 512 byte sectors: 255H 63S/T 553C) da5 at ahc2 bus 0 target 1 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 4340MB (8888543 512 byte sectors: 255H 63S/T 553C) Any ideas on this one? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 25 9:39:14 2000 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 3E98A151A1 for ; Tue, 25 Jan 2000 09:39:05 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA95528; Tue, 25 Jan 2000 10:38:49 -0700 (MST) (envelope-from ken) Date: Tue, 25 Jan 2000 10:38:48 -0700 From: "Kenneth D. Merry" To: Nick Hibma Cc: FreeBSD SCSI Mailing List Subject: Re: bug in cam_periph.c Message-ID: <20000125103848.A95459@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from n_hibma@webweaving.org on Mon, Jan 24, 2000 at 10:36:48AM +0000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 24, 2000 at 10:36:48 +0000, Nick Hibma wrote: > > the following diff code does not make sense to me. first check for a > retry count larger than zero and return EIO when it is. I guess that > this piee of code has not been exercised very much, because changing it > did not make a difference for the SCSI devices I have here. [ ... ] > Patch below: > > --- cam_periph.c.orig Mon Jan 24 10:34:23 2000 > +++ cam_periph.c Mon Jan 24 10:34:27 2000 > @@ -1439,7 +1439,7 @@ > "CAM_AUTOSENSE_FAILED"); > /* NOTREACHED */ > error = EIO; > - } else if (ccb->ccb_h.retry_count > 0) { > + } else if (ccb->ccb_h.retry_count == 0) { > /* > * XXX KDM shouldn't there be a better > * argument to return?? > Believe it or not, you're not the first person to find that one. See PR kern/15975 -- Carl Mascott found it last month. I didn't fix it before, since I didn't have an easy way to verify the fix. Anyway, I'll go ahead and check it in. 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 Jan 25 12: 4: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from george.arc.nasa.gov (george.arc.nasa.gov [128.102.194.142]) by hub.freebsd.org (Postfix) with ESMTP id 31B1914F57 for ; Tue, 25 Jan 2000 12:02:16 -0800 (PST) (envelope-from lamaster@nren.nasa.gov) Received: from localhost by george.arc.nasa.gov (8.9.3/8.9.3) with SMTP id MAA06211 for ; Tue, 25 Jan 2000 12:02:15 -0800 (PST) X-Authentication-Warning: george.arc.nasa.gov: lamaster owned process doing -bs Date: Tue, 25 Jan 2000 12:02:15 -0800 (PST) From: Hugh LaMaster X-Sender: lamaster@george.arc.nasa.gov To: FreeBSD SCSI Mailing List Subject: Problems with Buslogic BT-958C in 3.2-3.4 RELEASE? 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 I upgraded a few months ago to 3.2-RELEASE, and, immediately started seeing problems with the Buslogic BT-958 controller. I would get the following messages, and then, the system would become unreachable across the network without a reboot, although the console still worked, and you could read disks locally. Strange. Anyway, I got busy, and rather than mess with it more, I decided to go with 3.4-RELEASE instead. Same messages, but, the behavior is better, because it seems to recover, and the system continues to work. Still, I'm concerned about it. The messages are about 6 busy mailbox messages: fred# Jan 25 02:06:48 fred /kernel: bt0: Encountered busy mailbox with 191 out of 192 commands active!!! Jan 25 02:06:48 fred /kernel: bt0: Encountered busy mailbox with 191 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: Encountered busy mailbox with 190 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: Encountered busy mailbox with 190 out of 192 commands active!!! Jan 25 02:06:49 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca8ec0 Jan 25 02:06:49 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca8ec0 Jan 25 02:07:48 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:07:48 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca83c0 Jan 25 02:08:12 fred /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc5ca83c0 Jan 25 02:08:12 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: (da0:bt0:0:0:0): CCB 0xc5ca8c80 - timed out Jan 25 02:08:12 fred /kernel: bt0: No longer in timeout Jan 25 02:08:12 fred /kernel: bt0: No longer in timeout From uname -a: 3.4-RELEASE FreeBSD 3.4-RELEASE #6: Relevant other info from boot messages: Jan 24 12:51:06 fred /kernel: ahc0: rev 0x04 int a irq 0 on pci0.14.0 Jan 24 12:51:06 fred /kernel: ahc1: rev 0x04 int b irq 0 on pci0.14.1 Jan 24 12:51:06 fred /kernel: bt0: rev 0x08 int a irq 11 on pci0.16.0 Jan 24 12:51:06 fred /kernel: bt0: BT-958 FW Rev. 5.07B Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs Jan 24 12:51:06 fred /kernel: hea0: rev 0x00 int a irq 10 on pci0.18.0 Jan 24 12:51:06 fred /kernel: de0: rev 0x22 int a irq 9 on pci0.20.0 Jan 24 12:51:06 fred /kernel: de0: enabling Full Duplex 100baseTX port Jan 24 12:51:06 fred /kernel: da1 at bt0 bus 0 target 1 lun 0 Jan 24 12:51:06 fred /kernel: da1: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da3 at bt0 bus 0 target 3 lun 0 Jan 24 12:51:06 fred /kernel: da3: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da3: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da0 at bt0 bus 0 target 0 lun 0 Jan 24 12:51:06 fred /kernel: da0: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: da2 at bt0 bus 0 target 2 lun 0 Jan 24 12:51:06 fred /kernel: da2: Fixed Direct Access SCSI-2 device Jan 24 12:51:06 fred /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled Jan 24 12:51:06 fred /kernel: da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Jan 24 12:51:06 fred /kernel: cd0 at bt0 bus 0 target 4 lun 0 Jan 24 12:51:07 fred /kernel: cd0: Removable CD-ROM SCSI-2 device Jan 24 12:51:07 fred /kernel: cd0: 10.000MB/s transfers (10.000MHz, offset 15) Jan 24 12:51:07 fred /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Any ideas? -- Hugh LaMaster, M/S 233-21, Email: lamaster@nren.nasa.gov NASA Ames Research Center Or: lamaster@nas.nasa.gov Moffett Field, CA 94035-1000 Or: lamaster@george.arc.nasa.gov Phone: 650/604-1056 Disc: Unofficial, personal *opinion*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 25 12:19:46 2000 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 A5BF015215 for ; Tue, 25 Jan 2000 12:19:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA96527; Tue, 25 Jan 2000 13:19:01 -0700 (MST) (envelope-from ken) Date: Tue, 25 Jan 2000 13:19:01 -0700 From: "Kenneth D. Merry" To: LukeUnix Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CMD problems Message-ID: <20000125131901.A96487@panzer.kdm.org> References: <200001251721.JAA32558@infosite.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001251721.JAA32558@infosite.com>; from lukeunix@infosite.com on Tue, Jan 25, 2000 at 09:21:52AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jan 25, 2000 at 09:21:52 -0800, LukeUnix wrote: > I am having problems with a CMD CRD-5440 with multiple luns. The config is 2 > drive trays, each on their own channel on the CMD, and one host channel to > the FreeBSD 3.4 box. I was not experiencing these problems untill the 2nd > drive tray was added, making the CMD use 2 luns. So far I have tried to > set the number of max tags by editing sys/cam/cam_xpt.c and adding the > following entry. > > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, "CMD TECH", "CRD-5440*", "*" }, > /*quirks*/0, /*mintags*/24, /*maxtags*/32 > > That does not seem to have helped.. The following are scsi errors I am > seeing. > > /kernel: (da2:ahc1:0:1:0): SCB 0x18 - timed out while idle, LASTPHASE == > 0x1, SEQADDR == 0xa > /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b > /kernel: ahc1: Bus Device Reset on A:1. 2 SCBs aborted > /kernel: (da2:ahc1:0:1:0): SCB 0x28 - timed out while idle, LASTPHASE == > 0x1, SEQADDR == 0x9 > /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b > /kernel: ahc1: Bus Device Reset on A:1. 31 SCBs aborted > > Some info on the system.. > > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 2 lun 0 (pass1,da1) > at scbus1 target 1 lun 0 (pass2,da2) > at scbus1 target 1 lun 1 (pass3,da3) > at scbus2 target 0 lun 0 (pass4,da4) > at scbus2 target 1 lun 0 (pass5,da5) The short answer is "don't do that". Other folks have discovered that the CMD RAID arrays don't quite work right with more than one LUN enabled. Sorry I can't provide any solutions here, but this is almost certainly a problem with CMD's firmware, and the workaround is to only use one LUN on the controller. 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 Jan 25 15:26:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1910814F02 for ; Tue, 25 Jan 2000 15:26:05 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA43412; Wed, 26 Jan 2000 09:55:55 +1030 (CST) Date: Wed, 26 Jan 2000 09:55:55 +1030 From: Greg Lehey To: Palle Girgensohn Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) Message-ID: <20000126095555.C43103@freebie.lemis.com> References: <388DD60D.B33EAF26@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <388DD60D.B33EAF26@partitur.se> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] On Tuesday, 25 January 2000 at 17:57:49 +0100, Palle Girgensohn wrote: > Hi! > > I have a Seagate Python (DSS-20) tape streamer, and it won't accept > a retension command. Well, it accepts it, but nothing happens. Any > ideas why this is so? > This is what happens: > > $ mt ret > $ <---- immediately, I get a fresh prompt. nothing happens. I don't know the DSS-20, but if it's a modern tape drive, it doesn't support retensioning. The driver accepts and ignores the command. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 25 18:25:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 3C00E14D9B for ; Tue, 25 Jan 2000 18:25:39 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id VAA10439; Tue, 25 Jan 2000 21:25:31 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001260225.VAA10439@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Palle Girgensohn Cc: freebsd-scsi@FreeBSD.ORG, Greg Lehey From: "Louis A. Mamakos" Subject: Re: cannot mt retension (seagate python) References: <388DD60D.B33EAF26@partitur.se> <20000126095555.C43103@freebie.lemis.com> In-reply-to: Your message of "Wed, 26 Jan 2000 09:55:55 +1030." <20000126095555.C43103@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jan 2000 21:25:31 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > [Format recovered--see http://www.lemis.com/email/email-format.html] > > On Tuesday, 25 January 2000 at 17:57:49 +0100, Palle Girgensohn wrote: > > Hi! > > > > I have a Seagate Python (DSS-20) tape streamer, and it won't accept > > a retension command. Well, it accepts it, but nothing happens. Any > > ideas why this is so? > > > This is what happens: > > > > $ mt ret > > $ <---- immediately, I get a fresh prompt. nothing happens. > > I don't know the DSS-20, but if it's a modern tape drive, it doesn't > support retensioning. The driver accepts and ignores the command. I used to use an Archive (subsequently bought by Seagate) Python DAT drive. Could it be a DDS-2 drive? In any case, if it is a DAT drive, then ceratinly Greg's comment applies: it doesn't do retensioning. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 7: 0:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 4AF6F14D7A for ; Wed, 26 Jan 2000 07:00:13 -0800 (PST) (envelope-from girgen@partitur.se) Received: from elbas.partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id PAA21413; Wed, 26 Jan 2000 15:59:54 +0100 (CET) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by elbas.partitur.se (8.9.3/8.9.3) with ESMTP id PAA02623; Wed, 26 Jan 2000 15:59:54 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <388F0BEA.98364ACD@partitur.se> Date: Wed, 26 Jan 2000 15:59:54 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: "Louis A. Mamakos" Cc: freebsd-scsi@FreeBSD.ORG, Greg Lehey Subject: Re: cannot mt retension (seagate python) References: <388DD60D.B33EAF26@partitur.se> <20000126095555.C43103@freebie.lemis.com> <200001260225.VAA10439@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Louis A. Mamakos" wrote: > > I used to use an Archive (subsequently bought by Seagate) Python DAT > drive. Could it be a DDS-2 drive? In any case, if it is a DAT drive, DDS-2 it is. Sorry for the confusion! > then ceratinly Greg's comment applies: it doesn't do retensioning. Hmm... my tapes sometimes jam. I though a retension would help, but I guess I have to calculate on a certain amount of failure. Thanks for your input. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 14: 3:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 6D02B154A5 for ; Wed, 26 Jan 2000 14:03:33 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA52574; Thu, 27 Jan 2000 08:33:12 +1030 (CST) Date: Thu, 27 Jan 2000 08:33:12 +1030 From: Greg Lehey To: Palle Girgensohn Cc: "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) Message-ID: <20000127083312.Y44457@freebie.lemis.com> References: <388DD60D.B33EAF26@partitur.se> <20000126095555.C43103@freebie.lemis.com> <200001260225.VAA10439@whizzo.transsys.com> <388F0BEA.98364ACD@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <388F0BEA.98364ACD@partitur.se> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] On Wednesday, 26 January 2000 at 15:59:54 +0100, Palle Girgensohn wrote: > "Louis A. Mamakos" wrote: >> >> I used to use an Archive (subsequently bought by Seagate) Python DAT >> drive. Could it be a DDS-2 drive? In any case, if it is a DAT drive, > > DDS-2 it is. Sorry for the confusion! > >> then ceratinly Greg's comment applies: it doesn't do retensioning. > > Hmm... my tapes sometimes jam. I though a retension would help, but > I guess I have to calculate on a certain amount of failure. No, this is a problem with your drive. This shouldn't happen, and it's a bad sign. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 14:34:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8082514CCA for ; Wed, 26 Jan 2000 14:34:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA01339; Wed, 26 Jan 2000 14:33:40 -0800 Date: Wed, 26 Jan 2000 14:33:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Palle Girgensohn , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) In-Reply-To: <20000127083312.Y44457@freebie.lemis.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 > > Hmm... my tapes sometimes jam. I though a retension would help, but > > I guess I have to calculate on a certain amount of failure. > > No, this is a problem with your drive. This shouldn't happen, and > it's a bad sign. This happens with some frequency with DAT. Regular head cleaning helps, but this is one of the reasons that a lot of people don't like DAT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 15: 0:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 2751714D3C for ; Wed, 26 Jan 2000 14:59:47 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA53553; Thu, 27 Jan 2000 09:29:14 +1030 (CST) Date: Thu, 27 Jan 2000 09:29:13 +1030 From: Greg Lehey To: Matthew Jacob Cc: Palle Girgensohn , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) Message-ID: <20000127092913.C53307@freebie.lemis.com> References: <20000127083312.Y44457@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 26 January 2000 at 14:33:37 -0800, Matt Jacob wrote: >>> Hmm... my tapes sometimes jam. I though a retension would help, but >>> I guess I have to calculate on a certain amount of failure. >> >> No, this is a problem with your drive. This shouldn't happen, and >> it's a bad sign. > > This happens with some frequency with DAT. Regular head cleaning > helps, That depends on what's causing the jamming. I've never seen any relationship between jamming and head cleaning. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 15: 7:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id AF40A1502A for ; Wed, 26 Jan 2000 15:07:31 -0800 (PST) (envelope-from girgen@partitur.se) Received: from d1o90.telia.com (d1o90.telia.com [195.67.216.241]) by mailf.telia.com (8.9.3/8.9.3) with ESMTP id AAA26652; Thu, 27 Jan 2000 00:07:08 +0100 (CET) Received: from stordatan.telia.com (t3o90p87.telia.com [195.67.217.87]) by d1o90.telia.com (8.8.8/8.8.8) with ESMTP id AAA10208; Thu, 27 Jan 2000 00:06:58 +0100 (CET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.3/8.9.1) with ESMTP id AAA00707; Thu, 27 Jan 2000 00:06:27 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <388F7DF3.5D795DA3@partitur.se> Date: Thu, 27 Jan 2000 00:06:27 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: Greg Lehey Cc: Matthew Jacob , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) References: <20000127083312.Y44457@freebie.lemis.com> <20000127092913.C53307@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey wrote: > > On Wednesday, 26 January 2000 at 14:33:37 -0800, Matt Jacob wrote: > >>> Hmm... my tapes sometimes jam. I though a retension would help, but > >>> I guess I have to calculate on a certain amount of failure. > >> > >> No, this is a problem with your drive. This shouldn't happen, and > >> it's a bad sign. > > > > This happens with some frequency with DAT. Regular head cleaning > > helps, > > That depends on what's causing the jamming. I've never seen any > relationship between jamming and head cleaning. And this taper warns with a flashing diode when cleaning is needed, and I obey the signal... :) /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 16:18:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EF83B15464 for ; Wed, 26 Jan 2000 16:18:12 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA01712; Wed, 26 Jan 2000 16:17:46 -0800 Date: Wed, 26 Jan 2000 16:17:43 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Palle Girgensohn , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) In-Reply-To: <20000127092913.C53307@freebie.lemis.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 > On Wednesday, 26 January 2000 at 14:33:37 -0800, Matt Jacob wrote: > >>> Hmm... my tapes sometimes jam. I though a retension would help, but > >>> I guess I have to calculate on a certain amount of failure. > >> > >> No, this is a problem with your drive. This shouldn't happen, and > >> it's a bad sign. > > > > This happens with some frequency with DAT. Regular head cleaning > > helps, > > That depends on what's causing the jamming. I've never seen any > relationship between jamming and head cleaning. If enough gunk builds up on the heads, the tape lifts off slightly and starts a roll which can get reverse wrapped around a capstan roller. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 16:37:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mailf.telia.com (mailf.telia.com [194.22.194.25]) by hub.freebsd.org (Postfix) with ESMTP id 1024A154E4 for ; Wed, 26 Jan 2000 16:37:23 -0800 (PST) (envelope-from girgen@partitur.se) Received: from d1o90.telia.com (d1o90.telia.com [195.67.216.241]) by mailf.telia.com (8.9.3/8.9.3) with ESMTP id BAA01715; Thu, 27 Jan 2000 01:36:52 +0100 (CET) Received: from stordatan.telia.com (t3o90p87.telia.com [195.67.217.87]) by d1o90.telia.com (8.8.8/8.8.8) with ESMTP id BAA08259; Thu, 27 Jan 2000 01:36:51 +0100 (CET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.3/8.9.1) with ESMTP id BAA01505; Thu, 27 Jan 2000 01:36:29 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <388F930D.33757719@partitur.se> Date: Thu, 27 Jan 2000 01:36:29 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: mjacob@feral.com Cc: Greg Lehey , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > > On Wednesday, 26 January 2000 at 14:33:37 -0800, Matt Jacob wrote: > > >>> Hmm... my tapes sometimes jam. I though a retension would help, but > > >>> I guess I have to calculate on a certain amount of failure. > > >> > > >> No, this is a problem with your drive. This shouldn't happen, and > > >> it's a bad sign. > > > > > > This happens with some frequency with DAT. Regular head cleaning > > > helps, > > > > That depends on what's causing the jamming. I've never seen any > > relationship between jamming and head cleaning. > > If enough gunk builds up on the heads, the tape lifts off slightly and starts > a roll which can get reverse wrapped around a capstan roller. Actually, what has happened is that the end of the tape has twisted 90 deg. and lies "on top of the casserole" close to the tape rotation axis. (Hey, my English isn't native, please *try* to understand ;-) It is more likely that it has been rewinded too fast than that it has gotten stuck in the capstan or around the tape heads. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 16:39: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3AEB3153D8 for ; Wed, 26 Jan 2000 16:38:56 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA01835; Wed, 26 Jan 2000 16:38:42 -0800 Date: Wed, 26 Jan 2000 16:38:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Palle Girgensohn Cc: Greg Lehey , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) In-Reply-To: <388F930D.33757719@partitur.se> 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 > > > relationship between jamming and head cleaning. > > > > If enough gunk builds up on the heads, the tape lifts off slightly and starts > > a roll which can get reverse wrapped around a capstan roller. > > > Actually, what has happened is that the end of the tape has twisted 90 > deg. and lies "on top of the casserole" close to the tape rotation axis. > (Hey, my English isn't native, please *try* to understand ;-) > > It is more likely that it has been rewinded too fast than that it has > gotten stuck in the capstan or around the tape heads. Possibly, or there's junk on the capstan that causes the tape to slip sideways and rotate like you say. In either case, badness. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 16:50:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 2EA6414E85 for ; Wed, 26 Jan 2000 16:50:50 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA31960; Thu, 27 Jan 2000 10:55:11 +1030 (CST) Date: Thu, 27 Jan 2000 10:55:10 +1030 From: Greg Lehey To: Matthew Jacob Cc: Palle Girgensohn , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) Message-ID: <20000127105510.H53307@freebie.lemis.com> References: <20000127092913.C53307@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 26 January 2000 at 16:17:43 -0800, Matt Jacob wrote: > >> On Wednesday, 26 January 2000 at 14:33:37 -0800, Matt Jacob wrote: >>>>> Hmm... my tapes sometimes jam. I though a retension would help, but >>>>> I guess I have to calculate on a certain amount of failure. >>>> >>>> No, this is a problem with your drive. This shouldn't happen, and >>>> it's a bad sign. >>> >>> This happens with some frequency with DAT. Regular head cleaning >>> helps, >> >> That depends on what's causing the jamming. I've never seen any >> relationship between jamming and head cleaning. > > If enough gunk builds up on the heads, the tape lifts off slightly > and starts a roll which can get reverse wrapped around a capstan > roller. I've seen this on other tapes, but not helical scan. By the time this happens on a helical scan tape, I would imagine that the read errors would make it inoperative. I *have* seen serious problems with DDS drives, including jamming, but they have happened about equally with cleaned and uncleaned tapes. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 26 16:54:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from maile.telia.com (maile.telia.com [194.22.190.16]) by hub.freebsd.org (Postfix) with ESMTP id D4ADD14E85 for ; Wed, 26 Jan 2000 16:54:25 -0800 (PST) (envelope-from girgen@partitur.se) Received: from d1o90.telia.com (root@d1o90.telia.com [195.67.216.241]) by maile.telia.com (8.9.3/8.9.3) with ESMTP id BAA24529; Thu, 27 Jan 2000 01:54:08 +0100 (CET) Received: from stordatan.telia.com (t3o90p87.telia.com [195.67.217.87]) by d1o90.telia.com (8.8.8/8.8.8) with ESMTP id BAA13440; Thu, 27 Jan 2000 01:54:07 +0100 (CET) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.3/8.9.1) with ESMTP id BAA01567; Thu, 27 Jan 2000 01:53:45 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <388F9719.51A464AC@partitur.se> Date: Thu, 27 Jan 2000 01:53:45 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: mjacob@feral.com Cc: Greg Lehey , "Louis A. Mamakos" , freebsd-scsi@FreeBSD.ORG Subject: Re: cannot mt retension (seagate python) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > Possibly, or there's junk on the capstan that causes the tape to slip sideways > and rotate like you say. In either case, badness. Yep. badness. Cheers! Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 27 3:15: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from fuchs.omnilink.de (hase.omnilink.de [194.64.25.65]) by hub.freebsd.org (Postfix) with ESMTP id DCBCC15589 for ; Thu, 27 Jan 2000 03:15:02 -0800 (PST) (envelope-from ob@omnilink.net) Received: by fuchs.omnilink.de; id MAA02732; Thu, 27 Jan 2000 12:12:40 +0100 (MET) Received: from sondermuell.omnilink.de(194.64.25.218) by fuchs.omnilink.de via smap (V4.2) id xma002637; Thu, 27 Jan 00 12:11:48 +0100 Message-ID: <01c601bf68b7$9da58ec0$da1940c2@omnilink.de> Reply-To: "Oliver Blasnik" From: "Oliver Blasnik" To: "Kenneth D. Merry" , "LukeUnix" Cc: References: <200001251721.JAA32558@infosite.com> <20000125131901.A96487@panzer.kdm.org> Subject: Re: CMD problems Date: Thu, 27 Jan 2000 12:14:02 +0100 Organization: Omnilink ISC 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 Hi there, Luke had some (well known) Problems: > > I am having problems with a CMD CRD-5440 with multiple luns. The config is 2 > > /kernel: (da2:ahc1:0:1:0): SCB 0x18 - timed out while idle, LASTPHASE == > > 0x1, SEQADDR == 0xa > > /kernel: (da2:ahc1:0:1:0): Queuing a BDR SCB > > /kernel: (da2:ahc1:0:1:0): Bus Device Reset Message Sent > > /kernel: (da2:ahc1:0:1:0): no longer in timeout, status = 34b > > /kernel: ahc1: Bus Device Reset on A:1. 2 SCBs aborted > > /kernel: (da2:ahc1:0:1:0): SCB 0x28 - timed out while idle, LASTPHASE == > > 0x1, SEQADDR == 0x9 Go into CMD-Setup via serial, disable "Tagged Queuing" on the/all Host-Channels. Kenneth stated: > The short answer is "don't do that". > Other folks have discovered that the CMD RAID arrays don't quite work right > with more than one LUN enabled. > Sorry I can't provide any solutions here, but this is almost certainly a > problem with CMD's firmware, and the workaround is to only use one LUN on > the controller. True, the problem is that crappy firmware, which does not currectly share the commandqueue between multiple LUNs. If you _need_ multiple LUNs per Hostchannel, disable tagged queuing. This slows down disk-i/o a little bit, but the CMD works out very well due to the fast cache-access. Cu, Oliver -- __ OMNILINK Internet Service Center GmbH / \ Hahnstrasse 70, 60528 Frankfurt __\ /_________ Tel.: (0 69)66 44 10 Fax: (0 69)66 44 11 99 O M N I L I N K http://www.omnilink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jan 29 11:52:40 2000 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 8CC9C15214 for ; Sat, 29 Jan 2000 11:52:20 -0800 (PST) (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 UAA01511 for freebsd-scsi@freebsd.org; Sat, 29 Jan 2000 20:39:12 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA00555 for freebsd-scsi@freebsd.org; Sat, 29 Jan 2000 20:14:25 +0100 (CET) (envelope-from wilko) Date: Sat, 29 Jan 2000 20:14:25 +0100 From: Wilko Bulte To: FreeBSD SCSI hackers Subject: Compaq SmartArray programming manual available Message-ID: <20000129201424.A496@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org People interested in working on the driver for the Compaq PCI SmartArray family are invited to take a look at the programming specification that is now available at: ftp://www.tcja.nl/pub/wilko/Array_Controller_Spec.doc Please read the license that goes with the spec which is at: ftp://www.tcja.nl/pub/wilko/Array_Controller_Spec_License_621.doc Please note that both doc files are MSWord format. 2nd note: some parts of the programming interface are considered Compaq Intell. Property and are therefore not contained in these doc files. Thanks to the folks in Compaq Houston for giving me the docs. Enjoy, Wilko (also known as wilko.bulte@compaq.com) -- Wilko Bulte Arnhem, The Netherlands WWW : http://www.tcja.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message