From owner-freebsd-scsi Sun Sep 5 5:54:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arutam.inch.com (ns.inch.com [207.240.140.101]) by hub.freebsd.org (Postfix) with ESMTP id 1EC2A14C93 for ; Sun, 5 Sep 1999 05:54:37 -0700 (PDT) (envelope-from freyes@inch.com) Received: from win98 (freyes.static.inch.com [207.240.212.43]) by arutam.inch.com (8.9.3/8.9.3/UTIL-INCH-2.0.0) with SMTP id IAA02632 for ; Sun, 5 Sep 1999 08:54:03 -0400 (EDT) Message-Id: <199909051254.IAA02632@arutam.inch.com> From: "Francisco Reyes" To: "FreeBSD SCSI List" Date: Sun, 05 Sep 1999 08:54:38 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Kernel error from SCSI card/tape? Meaning? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am getting the error below after/while(?) using tar on a SCSI tape with a BT (Buslogic) controller. Aug 30 06:39:07 sanson /kernel: (sa0:bt0:0:3:0): WRITE(06). CDB: a 1 0 0 2 0 Aug 30 06:39:07 sanson /kernel: (sa0:bt0:0:3:0): ILLEGAL REQUEST asc:80,81 Aug 30 06:39:07 sanson /kernel: (sa0:bt0:0:3:0): Vendor Specific ASC What do those errors mean? The only thing I am doing that I can think of is: mt comp on #don't think this one is the error though mt blocksize 5120 And with tar I use -b 20 Previously there were errors saying the block size had to be a multiple of 5 bytes so I changed to 5120 and that error went away. The tape is: sa0: Removable Sequential Access SCSI-2 device To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 5 6:32:35 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 9B1FD15234; Sun, 5 Sep 1999 06:32:27 -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 11NcPB-0007jV-00; Sun, 5 Sep 1999 13:32:25 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id PAA00703; Sun, 5 Sep 1999 15:26:43 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199909051326.PAA00703@canyon.demon.nl> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909042352.RAA27822@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 4, 1999 05:52:47 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Sun, 5 Sep 1999 15:26:43 +0200 (CEST) Cc: rene@canyon.demon.nl (Rene de Vries), freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, 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 Ken, Unfortunately the AIC7890 has a 68pin HD connector for which I don't have a cable. As far as the scanner goes: I didn't expect it to have a decent SCSI implementation, this is the reason I used a separate NCR810 to connect it to my system. But I find it strange that the system panics on this configuration, if something is wrong I expected the kernel to complain but not panic (you could call a panic the ultimate way for the kernel to compain, but this was not very helpfull). I'll try to get my hands on an 25 (Centronics) <-> 68pin HD cable (is there someone near Delft, NL that has such a cable that I can borrow for a day or two?). Whould it help if I took my old PC and installed FreeBSD 2.2.6 (the latest 2.2R i've got) and see what happens? Rene > 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 -- 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 Sun Sep 5 12:20:33 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 20F7414F56; Sun, 5 Sep 1999 12:20:16 -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 VAA10582; Sun, 5 Sep 1999 21:04:04 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA05110; Sun, 5 Sep 1999 20:45:42 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909051845.UAA05110@yedi.iaf.nl> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909042352.RAA27822@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 4, 1999 5:52:47 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Sun, 5 Sep 1999 20:45:42 +0200 (CEST) Cc: rene@canyon.demon.nl, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG 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 Kenneth D. Merry wrote ... > 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. The relevant code snippet is: } else if (ccb->csio.scsi_status == SCSI_STATUS_CHECK_COND && status != CAM_AUTOSENSE_FAIL) { /* no point in decrementing the retry count */ panic("cam_periph_error: scsi status of " "CHECK COND returned but no sense " "information is availible. " "Controller should have returned " "CAM_AUTOSENSE_FAILED"); /* NOTREACHED */ error = EIO; Even if we assume the scanner yelled for attention and/or the ncr driver is at fault I don't really understand why the cam layer decides to panic the machine. Wouldn't it be sufficient to return EIO, or maybe just whine on the console? IIRC I've seen systems report 'no sense' in their log files in situations like this (non-FreeBSD systems that is). So I *guess* there are SCSI devices out there that exhibit this behaviour.. 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 Sun Sep 5 22:15:17 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 98BAD1544B; Sun, 5 Sep 1999 22:15:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA34043; Sun, 5 Sep 1999 23:13:56 -0600 (MDT) (envelope-from ken) Message-Id: <199909060513.XAA34043@panzer.kdm.org> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909051326.PAA00703@canyon.demon.nl> from Rene de Vries at "Sep 5, 1999 03:26:43 pm" To: rene@canyon.demon.nl (Rene de Vries) Date: Sun, 5 Sep 1999 23:13:56 -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: multipart/mixed; boundary=ELM936594835-33868-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM936594835-33868-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Rene de Vries wrote... > > 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. > > Unfortunately the AIC7890 has a 68pin HD connector for which I don't have a > cable. As far as the scanner goes: I didn't expect it to have a decent SCSI > implementation, this is the reason I used a separate NCR810 to connect it to > my system. But I find it strange that the system panics on this > configuration, if something is wrong I expected the kernel to complain but > not panic (you could call a panic the ultimate way for the kernel to compain, > but this was not very helpfull). I'll try to get my hands on an > 25 (Centronics) <-> 68pin HD cable (is there someone near Delft, NL that > has such a cable that I can borrow for a day or two?). > Whould it help if I took my old PC and installed FreeBSD 2.2.6 (the latest > 2.2R i've got) and see what happens? I'm not sure installing 2.2.6 would be that helpful, since it probably won't exhibit the same behavior. Here are some things to try: - if you can, put the scanner on your 7890 - turn the panic statement into a printf If you turn it into a printf, that may give us a better idea of just what command is failing. The attached patch for cam_periph.c should do the trick. The patch is against -current, but I think it should apply to -stable okay. I haven't checked to make sure it compiles or works, so you may have to tweak it if it doesn't. Ken -- Kenneth Merry ken@kdm.org --ELM936594835-33868-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=cam_periph_panic.patch.090599 Content-Description: cam_periph_panic.patch.090599 Content-Transfer-Encoding: 7bit ==== //depot/cam/sys/cam/cam_periph.c#74 - /a/ken/perforce/cam/sys/cam/cam_periph.c ==== *** /tmp/tmp.25426.0 Sun Sep 5 23:10:36 1999 --- /a/ken/perforce/cam/sys/cam/cam_periph.c Sun Sep 5 23:10:02 1999 *************** *** 1434,1445 **** SCSI_STATUS_CHECK_COND && status != CAM_AUTOSENSE_FAIL) { /* no point in decrementing the retry count */ ! panic("cam_periph_error: scsi status of " "CHECK COND returned but no sense " ! "information is availible. " ! "Controller should have returned " ! "CAM_AUTOSENSE_FAILED"); ! /* NOTREACHED */ error = EIO; } else if (ccb->ccb_h.retry_count > 0) { /* --- 1434,1448 ---- SCSI_STATUS_CHECK_COND && status != CAM_AUTOSENSE_FAIL) { /* no point in decrementing the retry count */ ! printf("cam_periph_error: scsi status of " "CHECK COND returned but no sense " ! "information is availible.\n" ! "cam_periph_error: Controller should " ! "have returned CAM_AUTOSENSE_FAILED\n"); ! ! retry = ccb->ccb_h.retry_count > 0; ! if (retry) ! ccb->ccb_h.retry_count--; error = EIO; } else if (ccb->ccb_h.retry_count > 0) { /* --ELM936594835-33868-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Sep 5 22:21:25 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 825AF15470; Sun, 5 Sep 1999 22:21:21 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA34103; Sun, 5 Sep 1999 23:20:25 -0600 (MDT) (envelope-from ken) Message-Id: <199909060520.XAA34103@panzer.kdm.org> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909051845.UAA05110@yedi.iaf.nl> from Wilko Bulte at "Sep 5, 1999 08:45:42 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 5 Sep 1999 23:20:25 -0600 (MDT) Cc: rene@canyon.demon.nl, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@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 Wilko Bulte wrote... > As Kenneth D. Merry wrote ... > > 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. > > The relevant code snippet is: > > } else if (ccb->csio.scsi_status == > SCSI_STATUS_CHECK_COND > && status != CAM_AUTOSENSE_FAIL) { > /* no point in decrementing the retry count > */ > panic("cam_periph_error: scsi status of " > "CHECK COND returned but no sense " > "information is availible. " > "Controller should have returned " > "CAM_AUTOSENSE_FAILED"); > /* NOTREACHED */ > error = EIO; > > Even if we assume the scanner yelled for attention and/or the ncr > driver is at fault I don't really understand why the cam layer > decides to panic the machine. Wouldn't it be sufficient to return > EIO, or maybe just whine on the console? Well, perhaps. My guess is that the intent was to catch problems with incorrectly written device drivers. It looks like it may have caught a problem in the NCR driver somewhere. I can't remember the rationale behind having a panic instead of a printf at the moment. > IIRC I've seen systems report 'no sense' in their log files in situations > like this (non-FreeBSD systems that is). So I *guess* there are > SCSI devices out there that exhibit this behaviour.. Apparantly so. I sent Rene a patch to turn the panic into a printf. The idea is that the error will get propagated back up, and we may be able to get a better idea of just what is failing. 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 Sep 6 14:32:19 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 42DD315564; Mon, 6 Sep 1999 14:32:00 -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 XAA11273; Mon, 6 Sep 1999 23:19:58 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA03179; Mon, 6 Sep 1999 23:19:07 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909062119.XAA03179@yedi.iaf.nl> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909060520.XAA34103@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 5, 1999 11:20:25 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Mon, 6 Sep 1999 23:19:07 +0200 (CEST) Cc: rene@canyon.demon.nl, freebsd-scsi@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG 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 Kenneth D. Merry wrote ... > Wilko Bulte wrote... > > As Kenneth D. Merry wrote ... ... > > Even if we assume the scanner yelled for attention and/or the ncr > > driver is at fault I don't really understand why the cam layer > > decides to panic the machine. Wouldn't it be sufficient to return > > EIO, or maybe just whine on the console? > > Well, perhaps. My guess is that the intent was to catch problems with > incorrectly written device drivers. It looks like it may have caught a > problem in the NCR driver somewhere. I can't remember the rationale behind > having a panic instead of a printf at the moment. > > > IIRC I've seen systems report 'no sense' in their log files in situations > > like this (non-FreeBSD systems that is). So I *guess* there are > > SCSI devices out there that exhibit this behaviour.. > > Apparantly so. I sent Rene a patch to turn the panic into a printf. The > idea is that the error will get propagated back up, and we may be able to > get a better idea of just what is failing. Just had him on the phone. No luck. The driver does see 'something' out there, but attaches it as a da device. Blurk. Sounds like completely bogus plumbing to me. Or something just as drastic as that. On W95 with scsi board that came with the scanner things work OK, including a sensible inquire string etc. So, looks like hardware to me. At least for now. The NCR810 is known good, as is the scanner. Leaves the cable. I'm suspicious about the HD50 to SubD25 cable (how wonderful these non-standard connectors..) Time permitting more investigation to follow coming weekend. 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 Sep 6 14:50:41 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 19A3914D96 for ; Mon, 6 Sep 1999 14:50:37 -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 11O6bn-0006R8-00; Mon, 6 Sep 1999 21:47:27 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id XAA00439; Mon, 6 Sep 1999 23:29:40 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199909062129.XAA00439@canyon.demon.nl> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909060520.XAA34103@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 5, 1999 11:20:25 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Mon, 6 Sep 1999 23:29:40 +0200 (CEST) Cc: wilko@yedi.iaf.nl (Wilko Bulte), freebsd-scsi@freebsd.org 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 Ken, Wilko, Freebsd-Scsi readers, This is the continuing saga about a panicing FreeBSD 3.3RC, a NCR810 and a Umax 1220s scanner. Currently the panic is replaced with a printf (and the retry count is decremented) but it did not bring the scanner to life... All it had to say was: da1 at ncr0 bus 0 target 6 lun 0 da1: < > Fixed Direct Access SCSI-0 device da1: 3.300MB/s transfers da1: 0MB (2957417921 0 byte sectors: 0H 0S/T 0C) And 7 times the "cam_periph_error:...." former panic message... Which is totally not good as far as I understand SCSI devices. (I would love to store 2.7Gb on my scanner but somehow I think that this is not going to work....) I talked to Wilko over the phone and he suggested to connect the scanner thru the NCR810 and the same cable to my W95 box. Currently it is connected to the W95 box with the SCSI adapter that was packaged with the scanner. I'll do so tomorrow evening (time permitting). 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 Tue Sep 7 3:32:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from imr1.srv.uk.deuba.com (imr1.srv.uk.deuba.com [194.196.205.49]) by hub.freebsd.org (Postfix) with ESMTP id E80EE14D09 for ; Tue, 7 Sep 1999 03:32:30 -0700 (PDT) (envelope-from Steve.Gailey@db.com) Received: by imr1.srv.uk.deuba.com id LAA01531; Tue, 7 Sep 1999 11:31:30 +0100 (BST) Received: from bmr2-e1.srv.uk.deuba.com(10.140.222.2) by imr1.srv.uk.deuba.com via mail (V2.1/2.1) id xma001508; Tue, 7 Sep 99 11:31:21 +0100 Received: from pow.srv.uk.deuba.com by bmr2-e1.srv.uk.deuba.com id LAA24984; Tue, 7 Sep 1999 11:31:20 +0100 (BST) Received: from dmglon010020773 by pow.srv.uk.deuba.com id LAA05072; Tue, 7 Sep 1999 11:31:17 +0100 (BST) Message-Id: <199909071031.LAA05072@pow.srv.uk.deuba.com> From: "Steve Gailey" To: freebsd-scsi@FreeBSD.ORG Date: Tue, 7 Sep 1999 11:16:09 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: amd scsi controllers Reply-To: Steve.Gailey@db.com X-mailer: Pegasus Mail for Win32 (v3.12a) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anyone know if the amd scsi controller has been ported to the new CAM system yet? If not, is anyone working on this? My old HP laptop is stuck on 2.2.8 until the onboard scsi drivers are available for the 3 branch. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 7 7:54:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mocha.baileylink.net (mocha.baileylink.net [63.71.213.4]) by hub.freebsd.org (Postfix) with ESMTP id CD38D14EC2 for ; Tue, 7 Sep 1999 07:54:42 -0700 (PDT) (envelope-from brad@baileylink.net) Received: from togo (dhcp51.javabit.com [63.71.213.51]) by mocha.baileylink.net (Netscape Mail Server v2.02) with SMTP id AAA18366; Tue, 7 Sep 1999 09:51:55 -0500 From: brad@baileylink.net To: "Chris D. Faulhaber" , "todd" Cc: Subject: RE: Compaq 3200 Smart Raid Controller support. Date: Tue, 7 Sep 1999 09:46:24 -0500 Message-ID: <002b01bef93f$c22ae700$33d5473f@togo.javabit.com> 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.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have the same problem that Todd described. In the interest of bandwidth I have created a site (http://testbed.baileylink.net/~brad/ida-debugs/) for the information that I have gathered, including my dmesg, sysctl -a, and uname -a. If you need more information I will gather it. Here is my config: Compaq 1600R 1 Pentium II 450 320MB RAM 1 Compaq SMART ARRAY 3200 2 Compaq Hot Swap Drive 9GB 10K RPM the drives are configured RAID level 1 The problem manifested itself like this... I ftp'd the ports.tar.gz from several ftp sites all of them giving me an error similar to this when I tried to unpack them with tar -xvzf ports.tar.gz: gzip: stdin: invalid compressed data--format violated tar: Unexpected EOF on archive file tar: child returned status 1 if I try gunzip ports.tar.gz I get: invalid compressed data--format violated If I make md5 hashes during this whole process I keep getting different values. I can also sometimes change the md5 just my doing a sync. For more information look at the script labeled md5-script.txt I have downloaded this file on a different machine and determined (through md5) that the file that I have downloaded is good. (more info in md5-script.txt) If anyone can help I would appreciate it. Thanx, BMG -----Original Message----- From: owner-freebsd-scsi@FreeBSD.ORG [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Chris D. Faulhaber Sent: Tuesday, August 17, 1999 7:21 AM To: todd Cc: freebsd-scsi@freebsd.org Subject: Re: Compaq 3200 Smart Raid Controller support. On Mon, 16 Aug 1999, todd wrote: > > I am having a problem with large files. Mainly any large tar files. tar > ends with the following error > > gzip: stdin: invalid compressed data--format violated > tar: Unexpected EOF on archive file > tar: child returned status 1 > Please define "large files"; IIRC, the tar (1.11.2) that comes standard has a problem with files > 2GB... > > I think I am getting errors with the ida driver on my system. Here is my configuration > An error log of some sort, along with the output of dmesg may help point to hardware or software problems. Regards, Chris ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one and always Reality Check Information, Inc. | pointed to someone better. 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 Tue Sep 7 13: 2:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3424E14D35; Tue, 7 Sep 1999 13:02:13 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA28237; Tue, 7 Sep 1999 16:01:09 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA00933; Tue, 7 Sep 1999 16:00:38 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 7 Sep 1999 16:00:38 -0400 (EDT) To: scsi@freebsd.org Cc: gibbs@freebsd.org, anderson@cs.duke.edu Subject: data corruption when using aic7890 X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14293.26481.521753.519004@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a bunch of ASUS P2B-LS motherboards with on-board AIC7890 U2 controllers. I'm running a kernel with rev 1.20 of src/sys/pci/ahc_pci.c (eg, after the CACHETHEN fix). When I run a local data-integrity checking program, I'm seeing occasional data corruption on Seagate ST39140W drives connected to the on-board U2 controller. This program writes a known pattern of data into a variable size (512MB in this case) file on disk & reads it back over & over again. If it encounters corruption, it reports just the first word where corruption was found & then skips to the next page, so its hard to tell how complete the corruption is. We see things like this: ##error 0 page 8228 expected [0x030241d8] saw [0x07c5b1d8] ##error 1 page 9718 expected [0x035f61f0] saw [0x072081f0] ##error 2 page 15719 expected [0x03d671c8] saw [0x016441c8] The last 3 bytes are the offset into the page. Since they are non-zero, at least part of the data is correct. It seems that the corruption only occurs after the first 400 or so bytes data in a page. It seems to be happening fairly infrequently (about every 500GB of data or so). Most importantly, it seems to be happenening only on drives connected to the on-board U2 interfaces, so my first guess would be that we can rule out anything but a driver or hardware problem. Eg, this machine has 2 more ST39140W drives connected to an ncr 53c875 & I've never seen any corruption on them. Ditto for the an IDE disk connected to the on-board ide controller. Any ideas? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 PS: Here's a dmesg of the box: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Sep 3 16:19:50 EDT 1999 gallatin@grasshopper.cs.duke.edu:/freebsd/src/sys/compile/SLICEX86 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300683643 Hz CPU: Pentium III (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387f9ff,MMX,FXSR,> real memory = 134205440 (131060K bytes) avail memory = 126316544 (123356K bytes) Preloaded elf kernel "kernel" at 0xc0325000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 chip1: at device 4.2 on pci0 intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 ahc0: irq 12 at device 6.0 on pci0 BRDCTL = 0x2 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: irq 10 at device 7.0 on pci0 fxp0: Ethernet address 00:e0:18:98:12:26 ncr0: irq 12 at device 9.0 on pci0 pci0: unknown card DGH8043 (vendor=0x10e8, dev=0x8043) at 12.0 irq 11 Probing for PnP devices: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da3 at ncr0 bus 0 target 2 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da3: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da2 at ncr0 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) changing root device to wd0s1a tpz0: irq 11 at device 12.0 on pci0 tpz0: Myrinet LANai 4.3 address 00:60:dd:7f:e7:53 (M2M-PCI32c-21956) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 7 13:23:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 6189A15636 for ; Tue, 7 Sep 1999 13:23:53 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id PAA18274; Tue, 7 Sep 1999 15:22:57 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id PAA22973; Tue, 7 Sep 1999 15:22:55 -0500 (CDT) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id PAA25178; Tue, 7 Sep 1999 15:22:55 -0500 (CDT) Date: Tue, 7 Sep 1999 15:22:55 -0500 (CDT) From: Jonathan Lemon Message-Id: <199909072022.PAA25178@free.pcs> To: brad@baileylink.net, scsi@freebsd.org Subject: Re: Compaq 3200 Smart Raid Controller support. X-Newsgroups: local.mail.freebsd-scsi In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >I have the same problem that Todd described. In the interest of bandwidth I >have created a site (http://testbed.baileylink.net/~brad/ida-debugs/) for >the information that I have gathered, including my dmesg, sysctl -a, and >uname -a. If you need more information I will gather it. > >Here is my config: >Compaq 1600R >1 Pentium II 450 >320MB RAM >1 Compaq SMART ARRAY 3200 >2 Compaq Hot Swap Drive 9GB 10K RPM Try this patch, I'm not 100% sure if it'll fix the problem, but I think it probably will. If it does, please let me know ASAP so it can get merged into 3.3-RC -- Jonathan Index: ida.c =================================================================== RCS file: /tuna/ncvs/src/sys/i386/isa/Attic/ida.c,v retrieving revision 1.1.2.2 diff -r1.1.2.2 ida.c 734c734,735 < qcbp->hdr.flags = 0x24; --- > qcbp->hdr.flags = > (sizeof(struct ida_req) + sizeof(struct ida_sgb) * IDA_MAX_SGLEN) >> 2; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 7 13:57: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 C76C01536B for ; Tue, 7 Sep 1999 13:57:31 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA45884; Tue, 7 Sep 1999 14:56:48 -0600 (MDT) (envelope-from ken) Message-Id: <199909072056.OAA45884@panzer.kdm.org> Subject: Re: amd scsi controllers In-Reply-To: <199909071031.LAA05072@pow.srv.uk.deuba.com> from Steve Gailey at "Sep 7, 1999 11:16:09 am" To: Steve.Gailey@db.com Date: Tue, 7 Sep 1999 14:56: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 Steve Gailey wrote... > Hi, > > Does anyone know if the amd scsi controller has been ported to > the new CAM system yet? If not, is anyone working on this? > > My old HP laptop is stuck on 2.2.8 until the onboard scsi drivers > are available for the 3 branch. There is a CAM amd driver, written by Tekram and cleaned up by Justin, in -current. It hasn't been merged into -stable yet. Hopefully Justin will merge it into -stable before 3.3 goes out the door. If you want to use it now, it shouldn't be too hard to use it in -stable. (You should be able to copy the two driver files over, and then edit sys/conf/files) 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 Sep 7 14: 7:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A72714D0B for ; Tue, 7 Sep 1999 14:07:19 -0700 (PDT) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (va-152.skylink.it [194.185.55.152]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id XAA17562; Tue, 7 Sep 1999 23:06:20 +0200 Received: from localhost (localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id VAA07511; Tue, 7 Sep 1999 21:06:47 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Tue, 7 Sep 1999 21:06:47 GMT Date: Tue, 7 Sep 1999 23:06:47 +0200 (CEST) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: "Kenneth D. Merry" Cc: Steve.Gailey@db.com, freebsd-scsi@FreeBSD.ORG Subject: Re: amd scsi controllers In-Reply-To: <199909072056.OAA45884@panzer.kdm.org> 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'd probably be able to convince JKH if you send him a Makefile for a sys/module Nick On Tue, 7 Sep 1999, Kenneth D. Merry wrote: > Steve Gailey wrote... > > Hi, > > > > Does anyone know if the amd scsi controller has been ported to > > the new CAM system yet? If not, is anyone working on this? > > > > My old HP laptop is stuck on 2.2.8 until the onboard scsi drivers > > are available for the 3 branch. > > There is a CAM amd driver, written by Tekram and cleaned up by Justin, in > -current. It hasn't been merged into -stable yet. > > Hopefully Justin will merge it into -stable before 3.3 goes out the door. > > If you want to use it now, it shouldn't be too hard to use it in -stable. > (You should be able to copy the two driver files over, and then edit > sys/conf/files) > > Ken > -- > Kenneth Merry > ken@kdm.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 7 15:39:13 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 A270314F93 for ; Tue, 7 Sep 1999 15:39:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA46618; Tue, 7 Sep 1999 16:36:51 -0600 (MDT) (envelope-from ken) Message-Id: <199909072236.QAA46618@panzer.kdm.org> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909062129.XAA00439@canyon.demon.nl> from Rene de Vries at "Sep 6, 1999 11:29:40 pm" To: rene@canyon.demon.nl (Rene de Vries) Date: Tue, 7 Sep 1999 16:36:51 -0600 (MDT) Cc: wilko@yedi.iaf.nl, 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 Rene de Vries wrote... > Ken, Wilko, Freebsd-Scsi readers, > > This is the continuing saga about a panicing FreeBSD 3.3RC, a NCR810 and > a Umax 1220s scanner. > Currently the panic is replaced with a printf (and the retry count is > decremented) but it did not bring the scanner to life... > All it had to say was: > > da1 at ncr0 bus 0 target 6 lun 0 > da1: < > Fixed Direct Access SCSI-0 device > da1: 3.300MB/s transfers > da1: 0MB (2957417921 0 byte sectors: 0H 0S/T 0C) > > And 7 times the "cam_periph_error:...." former panic message... > > Which is totally not good as far as I understand SCSI devices. Indeed. It looks like the inquiry information is getting totally corrupted. I suspect a hardware problem of some sort. > (I would love to store 2.7Gb on my scanner but somehow I think that this is not > going to work....) > > I talked to Wilko over the phone and he suggested to connect the scanner thru > the NCR810 and the same cable to my W95 box. Currently it is connected to the > W95 box with the SCSI adapter that was packaged with the scanner. > I'll do so tomorrow evening (time permitting). That's a good suggestion, let me know 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 Tue Sep 7 20:29:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mocha.baileylink.net (mocha.baileylink.net [63.71.213.4]) by hub.freebsd.org (Postfix) with ESMTP id 1F15A154A3 for ; Tue, 7 Sep 1999 20:29:04 -0700 (PDT) (envelope-from brad@baileylink.net) Received: from togo (dhcp51.javabit.com [63.71.213.51]) by mocha.baileylink.net (Netscape Mail Server v2.02) with SMTP id AAA25414; Tue, 7 Sep 1999 22:27:00 -0500 From: brad@baileylink.net To: "Jonathan Lemon" , Subject: RE: Compaq 3200 Smart Raid Controller support. Date: Tue, 7 Sep 1999 22:21:30 -0500 Message-ID: <000201bef9a9$3e3989a0$33d5473f@togo.javabit.com> 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.2173.0 In-Reply-To: <199909072022.PAA25178@free.pcs> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thank you for the patch Jonathan, but I don't think that it helped. I didn't quite understand why you would want to >> at the end, a can understand why you would want to multiply by 4 but not divide. If you have a compiled kernel that you would like me try I am willing to try that also. It is currently very difficult for me adjust the machine in question because it is my only FreeBSD box and the source tree keeps getting corrupt. The patched version of my kernel (assuming that I patched the thing correctly) exhibits the same problem. Please let me know if you have any other ideas. Thanx, BMG -----Original Message----- From: owner-freebsd-scsi@FreeBSD.ORG [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of Jonathan Lemon Sent: Tuesday, September 07, 1999 3:23 PM To: brad@baileylink.net; scsi@freebsd.org Subject: Re: Compaq 3200 Smart Raid Controller support. In article you write: >I have the same problem that Todd described. In the interest of bandwidth I >have created a site (http://testbed.baileylink.net/~brad/ida-debugs/) for >the information that I have gathered, including my dmesg, sysctl -a, and >uname -a. If you need more information I will gather it. > >Here is my config: >Compaq 1600R >1 Pentium II 450 >320MB RAM >1 Compaq SMART ARRAY 3200 >2 Compaq Hot Swap Drive 9GB 10K RPM Try this patch, I'm not 100% sure if it'll fix the problem, but I think it probably will. If it does, please let me know ASAP so it can get merged into 3.3-RC -- Jonathan Index: ida.c =================================================================== RCS file: /tuna/ncvs/src/sys/i386/isa/Attic/ida.c,v retrieving revision 1.1.2.2 diff -r1.1.2.2 ida.c 734c734,735 < qcbp->hdr.flags = 0x24; --- > qcbp->hdr.flags = > (sizeof(struct ida_req) + sizeof(struct ida_sgb) * IDA_MAX_SGLEN) >> 2; 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 Tue Sep 7 20:59:42 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 B102114D77 for ; Tue, 7 Sep 1999 20:59:39 -0700 (PDT) (envelope-from kris@airnet.net) Received: from airnet.net (tc14-216-180-35-34.dialup.HiWAAY.net [216.180.35.34] (may be forged)) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA29569 for ; Tue, 7 Sep 1999 22:59:08 -0500 (CDT) Message-ID: <37D5DF0B.FFF98713@airnet.net> Date: Tue, 07 Sep 1999 22:59:07 -0500 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: scsi@freebsd.org Subject: Reformatting a 520-byte-per-sector drive Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org da3 at ahc0 bus 0 target 0 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 5.000MB/s transfers (5.000MHz, offset 12), Tagged Queueing Enabled da3: 957MB (1931265 520 byte sectors: 64H 32S/T 943C) I want this to be 512 bytes/sector. I've tried to edit the modepage, but it comes up blank in vi. I'm going to guess that that means I can't change any of those parameters. :-) IBM's webpage on the drive says that I can change the number of blocks and the block size ("Block descriptor"). However, I don't seem to find anything in camcontrol's manpage to indicate how to go about changing it. Make no mistake about it, I can read the bytes/sector from modepage 0x03, but I can't change them. I know that Seagate has a few drives that can change bytes/sector. I'm currently perusing a manual from Seagate about SCSI-II/III but if someone else comes up with an answer sooner... PS: I'm not on -scsi. -- Kris Kirby ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Sep 7 22:35:13 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 D56FD15047 for ; Tue, 7 Sep 1999 22:35:07 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA48516; Tue, 7 Sep 1999 23:34:08 -0600 (MDT) (envelope-from ken) Message-Id: <199909080534.XAA48516@panzer.kdm.org> Subject: Re: Reformatting a 520-byte-per-sector drive In-Reply-To: <37D5DF0B.FFF98713@airnet.net> from Kris Kirby at "Sep 7, 1999 10:59:07 pm" To: kris@airnet.net (Kris Kirby) Date: Tue, 7 Sep 1999 23:34:08 -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 Kris Kirby wrote... > da3 at ahc0 bus 0 target 0 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 5.000MB/s transfers (5.000MHz, offset 12), Tagged Queueing Enabled > da3: 957MB (1931265 520 byte sectors: 64H 32S/T 943C) > > I want this to be 512 bytes/sector. > > I've tried to edit the modepage, but it comes up blank in vi. I'm going > to guess that that means I can't change any of those parameters. :-) > IBM's webpage > on the > drive says that I can change the number of blocks and the block size > ("Block descriptor"). However, I don't seem to find anything in > camcontrol's manpage to indicate how to go about changing it. Make no > mistake about it, I can read the bytes/sector from modepage 0x03, but I > can't change them. Hmm. Well, there's no option from the camcontrol modepage command to edit things in the block descriptor. If you want to do that, you'll probably have to do it with a manual command. (i.e. camcontrol cmd) Here's how you can display the mode page header and block descriptor: # camcontrol cmd da1 -v -c "1A 0 3 0 c 0" -i 0xc "i1 i1 i1 i1 i1 i3 i1 i3" 35 0 16 8 1 1052654 0 512 The last 3-byte integer is the block size. So, in theory, I suppose you could change the blocksize by doing something like this: # camcontrol cmd da1 -v -c "15 10 0 0 c 0" -o 0xc "b 0 0 8 0 0:i3 0 v:i3" 512 [ of course you'd substitute "da3" for "da1" above ] Hmm, that's remarkably similar to something Greg Lehey told me he had to do to get a Seagate drive of his to format to a different sector size. Here's a quote from Greg: ======================================================================== Yup, there's some other way to change it. Set the current values, then immediately issue a format command: # camcontrol cmd da1 -v -c "15 10 0 0 v:i1 0" 12 -o 12 "0 0 0 8 0 0:i3 0 v:i3" 512 # camcontrol cmd -n da -u 1 -v -t 7200 -c "4 0 0 0 0 0" # camcontrol modepage da1 -m 3 Tracks per Zone: 19 Alternate Sectors per Zone: 12 Alternate Tracks per Zone: 0 Alternate Tracks per Logical Unit: 38 Sectors per Track: 84 Data Bytes per Physical Sector: 512 Interleave: 1 Track Skew Factor: 13 Cylinder Skew Factor: 22 SSEC: 0 HSEC: 1 RMB: 0 SURF: 0 ======================================================================== I wasn't paying a whole lot of attention at the time, so I thought he actually ended up setting the current parameters in mode page 3. In actuality, he was setting them in the block descriptor. Hmm, well, if this works (either Greg's command or my command, followed *immediately* by a format), an example of this might be a good thing to stick in the camcontrol man page. > I know that Seagate has a few drives that can change bytes/sector. I'm > currently perusing a manual from Seagate about SCSI-II/III but if > someone else comes up with an answer sooner... Well, I think with most IBM disks you can change the blocksize from mode page 3, but apparantly with this one you have to do it from the block descriptor. It sounds similar to the Seagate disk that Greg used the above command on. Since you've got to format your disk anyway, you might want to try out my format patches to camcontrol. They've been sitting around for months in my tree, and as far as I know, no one (except me) has tried them. Here they are: http://www.freebsd.org/~ken/camcontrol.format.061799 I think the patches should apply okay to -current or -stable, but if they don't it shouldn't be too hard to get them to apply. One warning, though -- in your situation, you'll probably want to use the -q option to camcontrol format. The reason is, without "quiet" turned on, camcontrol will do an inquiry on your disk, which may nullify any block setting you just made, if your disk behaves anything like Greg's Seagate. 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 8 4: 0: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.3]) by hub.freebsd.org (Postfix) with ESMTP id 7452314E3A for ; Wed, 8 Sep 1999 04:00:02 -0700 (PDT) (envelope-from mw@io.freibergnet.de) Received: (from mw@localhost) by io.freibergnet.de (8.9.3/8.9.1) id MAA56613 for scsi@freebsd.org; Wed, 8 Sep 1999 12:58:55 +0200 (CEST) (envelope-from mw) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 08 Sep 1999 12:58:55 +0200 (CEST) Reply-To: mw@freibergnet.de Organization: FreibergNet Systemhaus / Liebscher & Partner From: Martin Welk To: scsi@freebsd.org Subject: Tandberg SLR6 / FreeBSD-3.3-RC Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi everybody, I have successfully installed some QIC tape drives with FreeBSD, some Wangtek 5150ES and similar (Archive, ...) and some Tandberg SLR 5 in the past, and now I want to get a SLR6 (before known as SLR24, a 12/24 GByte 1/4" tape drive) to run with FreeBSD. The machine is a P-II/400 on a Asus P2B-S, one SCSI disk (IBM LVD drive) and the SLR6 tape (UW-SCSI) connected as SCSI ID 15. I built a RELENG_3 CVS version on it, which was a 3.3-RC this morning, and the kernel recognizes the tape drive fine. The hard disk works also flawlessly, and I'm sure I've connected and terminated everything write. So I tried to run this: dump 0uaf /dev/nrsa0 / dump 0uaf /dev/nrsa0 /usr dump 0uaf /dev/nrsa0 /home dump 0uaf /dev/nrsa0 /var dump 0uaf /dev/rsa0 /tmp The root file system is dumped fine, as it seems. Every further dump gives me the following error message: .../kernel: (sa0:ahc0:0:15:0): WRITE(06). CDB: a 0 0 28 0 0 /kernel: (sa0:ahc0:0:15:0): ILLEGAL REQUEST asc:50,0 /kernel: (sa0:ahc0:0:15:0): Write append error What happens? Did I miss something? Thanks in advance, as always :-) Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 4:14:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 6063E15B88 for ; Wed, 8 Sep 1999 04:14:29 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id HAA15711; Wed, 8 Sep 1999 07:12:43 -0400 (EDT) Received: (from ath@localhost) by stiegl.niksun.com (8.9.2/8.8.7) id HAA68752; Wed, 8 Sep 1999 07:12:43 -0400 (EDT) (envelope-from ath) To: Andrew Gallatin Subject: Re: data corruption when using aic7890 Cc: freebsd-scsi@freebsd.org References: <14293.26481.521753.519004@grasshopper.cs.duke.edu> From: Andrew Heybey Date: 08 Sep 1999 07:12:42 -0400 In-Reply-To: Andrew Gallatin's message of "Tue, 7 Sep 1999 16:00:38 -0400 (EDT)" Message-ID: <85g10pbqs5.fsf@stiegl.niksun.com> Lines: 49 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin writes: > Hi, > > I have a bunch of ASUS P2B-LS motherboards with on-board AIC7890 U2 > controllers. I'm running a kernel with rev 1.20 of > src/sys/pci/ahc_pci.c (eg, after the CACHETHEN fix). > > When I run a local data-integrity checking program, I'm seeing > occasional data corruption on Seagate ST39140W drives connected to the > on-board U2 controller. This program writes a known pattern of data > into a variable size (512MB in this case) file on disk & reads it back > over & over again. If it encounters corruption, it reports just the > first word where corruption was found & then skips to the next page, > so its hard to tell how complete the corruption is. We see things > like this: > > ##error 0 page 8228 expected [0x030241d8] saw [0x07c5b1d8] > ##error 1 page 9718 expected [0x035f61f0] saw [0x072081f0] > ##error 2 page 15719 expected [0x03d671c8] saw [0x016441c8] > > The last 3 bytes are the offset into the page. Since they are > non-zero, at least part of the data is correct. It seems that the > corruption only occurs after the first 400 or so bytes data in a page. > It seems to be happening fairly infrequently (about every 500GB of > data or so). > > Most importantly, it seems to be happenening only on drives connected > to the on-board U2 interfaces, so my first guess would be that we can > rule out anything but a driver or hardware problem. Eg, this machine > has 2 more ST39140W drives connected to an ncr 53c875 & I've never > seen any corruption on them. Ditto for the an IDE disk connected to > the on-board ide controller. This sounds vaguely similar to kern/10243, except that I always saw corruption at the *end* of a page. How much data is corrupt? Is the bad data recognizable as being from elsewhere in the file? Try fiddling with the PCI bus latency setting in the bios (increasing it). However, the only sure solution that I found to my problem was to put the disks on the regular Ultra connector and live with 40MB/s. I have seen the problem with both IBM DRVS drives and Seagate ST39102LW. I have also seen the problem on the P2B-LS and a Supermicro motherboard with on-board AIC7890. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 6:58:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from imr1.srv.uk.deuba.com (imr1.srv.uk.deuba.com [194.196.205.49]) by hub.freebsd.org (Postfix) with ESMTP id 8368615278 for ; Wed, 8 Sep 1999 06:58:34 -0700 (PDT) (envelope-from Steve.Gailey@db.com) Received: by imr1.srv.uk.deuba.com id OAA21413; Wed, 8 Sep 1999 14:57:40 +0100 (BST) Received: from bmr1-e1.srv.uk.deuba.com(10.141.44.112) by imr1.srv.uk.deuba.com via mail (V2.1/2.1) id xma021400; Wed, 8 Sep 99 14:57:32 +0100 Received: from pow.srv.uk.deuba.com by bmr1-e1.srv.uk.deuba.com id OAA15714; Wed, 8 Sep 1999 14:57:31 +0100 (BST) Received: from accounts by pow.srv.uk.deuba.com id OAA01720; Wed, 8 Sep 1999 14:57:24 +0100 (BST) Message-Id: <199909081357.OAA01720@pow.srv.uk.deuba.com> From: "Steve Gailey" Organization: Metronome Solutions Ltd To: "Kenneth D. Merry" Date: Wed, 8 Sep 1999 15:00:25 GMT0B MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: amd scsi controllers Reply-To: steve.gailey@db.com Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: <199909072056.OAA45884@panzer.kdm.org> References: <199909071031.LAA05072@pow.srv.uk.deuba.com> from Steve Gailey at "Sep 7, 1999 11:16:09 am" X-mailer: Pegasus Mail for Win32 (v3.11) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for this. Steve > Steve Gailey wrote... > > Hi, > > > > Does anyone know if the amd scsi controller has been ported to > > the new CAM system yet? If not, is anyone working on this? > > > > My old HP laptop is stuck on 2.2.8 until the onboard scsi drivers > > are available for the 3 branch. > > There is a CAM amd driver, written by Tekram and cleaned up by Justin, in > -current. It hasn't been merged into -stable yet. > > Hopefully Justin will merge it into -stable before 3.3 goes out the door. > > If you want to use it now, it shouldn't be too hard to use it in -stable. > (You should be able to copy the two driver files over, and then edit > sys/conf/files) > > 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 8 9:27:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D4F8F14E3A for ; Wed, 8 Sep 1999 09:27:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA08808; Wed, 8 Sep 1999 09:26:13 -0700 Date: Wed, 8 Sep 1999 09:26:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Martin Welk Cc: scsi@FreeBSD.ORG Subject: Re: Tandberg SLR6 / FreeBSD-3.3-RC 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 > dump 0uaf /dev/nrsa0 / > dump 0uaf /dev/nrsa0 /usr > dump 0uaf /dev/nrsa0 /home > dump 0uaf /dev/nrsa0 /var > dump 0uaf /dev/rsa0 /tmp > > The root file system is dumped fine, as it seems. Every further dump > gives me the following error message: > > .../kernel: (sa0:ahc0:0:15:0): WRITE(06). CDB: a 0 0 28 0 0 > /kernel: (sa0:ahc0:0:15:0): ILLEGAL REQUEST asc:50,0 > /kernel: (sa0:ahc0:0:15:0): Write append error > > What happens? Did I miss something? Darn- I would have thought " SLR*" would catch all the Tandberg models, but I guess not.. Umm- it's not putting the drive in fixed length mode, and with the write append error I shouldn't wonder that it's also terminating the tape with two filemarks. Variable mode should be okay (Well, *I* think variable mode for QIC drives is foolish, but there are those out there who don't agree). Either set SA_QUIRK_1FM for this drive (and fixed if you want it), or use mt -f /dev/nrsa0 seteotmodel 1 before using the tape and see what happens. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 9:30:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay1.mail.uk.psi.net (relay1.mail.uk.psi.net [154.32.105.6]) by hub.freebsd.org (Postfix) with ESMTP id 7B43E14E3A for ; Wed, 8 Sep 1999 09:30:50 -0700 (PDT) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay1.mail.uk.psi.net with smtp (Exim 2.12 #2) id 11Okb3-0001Wg-00 for freebsd-scsi@freebsd.org; Wed, 8 Sep 1999 17:29:22 +0100 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.4 (830.2 3-23-1999)) id 802567E6.005A8DEE ; Wed, 8 Sep 1999 17:29:05 +0100 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: freebsd-scsi@freebsd.org Message-ID: <802567E6.005A8CEA.00@mail.plasmon.co.uk> Date: Wed, 8 Sep 1999 17:29:02 +0100 Subject: fd leak? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In lib/libcam/camlib.c:cam_open_btl() there appears to be a fd leak, in that the xpt device is opened, but never closed. Andrew. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 9:35:50 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 A776014FA9 for ; Wed, 8 Sep 1999 09:35:39 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA51567; Wed, 8 Sep 1999 10:34:32 -0600 (MDT) (envelope-from ken) Message-Id: <199909081634.KAA51567@panzer.kdm.org> Subject: Re: fd leak? In-Reply-To: <802567E6.005A8CEA.00@mail.plasmon.co.uk> from "amobbs@allstor-sw.co.uk" at "Sep 8, 1999 05:29:02 pm" To: amobbs@allstor-sw.co.uk Date: Wed, 8 Sep 1999 10:34:31 -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 amobbs@allstor-sw.co.uk wrote... > > In lib/libcam/camlib.c:cam_open_btl() there appears to be a fd leak, in that the > xpt device is opened, but never closed. Looks like you're right. Oops. Thanks for catching it. 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 8 10: 5:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sol.freibergnet.de (sol.freibergnet.de [194.123.255.4]) by hub.freebsd.org (Postfix) with ESMTP id 42A5E14F59 for ; Wed, 8 Sep 1999 10:05:54 -0700 (PDT) (envelope-from mw@sol.freibergnet.de) Received: (from mw@localhost) by sol.freibergnet.de (8.9.3/8.9.3) id TAA30776; Wed, 8 Sep 1999 19:04:37 +0200 (CEST) (envelope-from mw) Date: Wed, 8 Sep 1999 19:04:37 +0200 From: Martin Welk To: Matthew Jacob Cc: Martin Welk , scsi@FreeBSD.ORG Subject: Re: Tandberg SLR6 / FreeBSD-3.3-RC Message-ID: <19990908190437.B24911@sol.freibergnet.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Matthew Jacob on Wed, Sep 08, 1999 at 09:26:09AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Sep 08, 1999 at 09:26:09AM -0700, Matthew Jacob wrote: > Darn- I would have thought " SLR*" would catch all the Tandberg models, > but I guess not.. It's SCSI name is TANDBERG SLR6, so it should be caught by SLR* as it's written in .../scsi_sa.c > Either set SA_QUIRK_1FM for this drive (and fixed if you want it), or > use > > mt -f /dev/nrsa0 seteotmodel 1 > > before using the tape and see what happens. server# mt -f /dev/nrsa0 seteotmodel 1 /dev/nrsa0: old model was 2 filemarks at EOT /dev/nrsa0: new model is 1 filemark at EOT This is what you meant, when I understand you right? Now it seems to work. Thank you. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 10:11:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 826E014F59 for ; Wed, 8 Sep 1999 10:11:34 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA09071; Wed, 8 Sep 1999 10:10:54 -0700 Date: Wed, 8 Sep 1999 10:10:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Martin Welk Cc: scsi@FreeBSD.ORG Subject: Re: Tandberg SLR6 / FreeBSD-3.3-RC In-Reply-To: <19990908190437.B24911@sol.freibergnet.de> 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 Wed, Sep 08, 1999 at 09:26:09AM -0700, Matthew Jacob wrote: > > > Darn- I would have thought " SLR*" would catch all the Tandberg models, > > but I guess not.. > > It's SCSI name is TANDBERG SLR6, so it should be caught by SLR* as it's > written in .../scsi_sa.c Let's have the full Inquiry string from messages.. it sure shoulda caught it... > > > Either set SA_QUIRK_1FM for this drive (and fixed if you want it), or > > use > > > > mt -f /dev/nrsa0 seteotmodel 1 > > > > before using the tape and see what happens. > > server# mt -f /dev/nrsa0 seteotmodel 1 > /dev/nrsa0: old model was 2 filemarks at EOT > /dev/nrsa0: new model is 1 filemark at EOT > > This is what you meant, when I understand you right? Bingo. > > Now it seems to work. Thank you. > Sehr gut... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 11:49:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id DD7D3150C5 for ; Wed, 8 Sep 1999 11:49:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA08113; Wed, 8 Sep 1999 14:48:06 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA86711; Wed, 8 Sep 1999 14:47:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 8 Sep 1999 14:47:35 -0400 (EDT) To: Andrew Heybey Cc: freebsd-scsi@freebsd.org Subject: Re: data corruption when using aic7890 In-Reply-To: <85g10pbqs5.fsf@stiegl.niksun.com> References: <14293.26481.521753.519004@grasshopper.cs.duke.edu> <85g10pbqs5.fsf@stiegl.niksun.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14294.42593.953415.402280@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Heybey writes: > Andrew Gallatin writes: > > > > ##error 0 page 8228 expected [0x030241d8] saw [0x07c5b1d8] > > ##error 1 page 9718 expected [0x035f61f0] saw [0x072081f0] > > ##error 2 page 15719 expected [0x03d671c8] saw [0x016441c8] > > > > The last 3 bytes are the offset into the page. Since they are > > non-zero, at least part of the data is correct. It seems that the > > corruption only occurs after the first 400 or so bytes data in a page. > > It seems to be happening fairly infrequently (about every 500GB of > > data or so). > > > > Most importantly, it seems to be happenening only on drives connected > > to the on-board U2 interfaces, so my first guess would be that we can > > rule out anything but a driver or hardware problem. Eg, this machine > > has 2 more ST39140W drives connected to an ncr 53c875 & I've never > > seen any corruption on them. Ditto for the an IDE disk connected to > > the on-board ide controller. > > This sounds vaguely similar to kern/10243, except that I always saw > corruption at the *end* of a page. How much data is corrupt? Is the > bad data recognizable as being from elsewhere in the file? Well, at least the first 1/2 k of the page are corruption free... If your suggestion doesn't help, I'll modify my tool so as to reveal more information about the corrupt data (or just switch to yours..) With regards to your comment about network interrupts, the problem *does* seem to get worse when we're using our Myrinet gigabit network cards. I'm trying to leave them out of the equation for this test though. I managed to achieve my corruption with essentially no network traffic at all, just 2 other disk controllers were in contention for the bus. (53c875 & the on-board PIIX4). > Try fiddling with the PCI bus latency setting in the bios (increasing > it). However, the only sure solution that I found to my problem was > to put the disks on the regular Ultra connector and live with > 40MB/s. This must be what Mike Smith was talking about when Matt Dillon ran into corruption due to the CACHETHEN problem. I've used pciconf to set it to 64 (it was at 32) I'm currently re-running my test at the new setting. Have you tried BIOS any upgrades? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 11:57:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 9B81815121 for ; Wed, 8 Sep 1999 11:57:51 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id OAA17716; Wed, 8 Sep 1999 14:57:32 -0400 (EDT) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.9.2/8.8.7) with ESMTP id OAA74051; Wed, 8 Sep 1999 14:57:32 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Message-Id: <199909081857.OAA74051@stiegl.niksun.com> From: Andrew Heybey To: Andrew Gallatin Cc: freebsd-scsi@freebsd.org Subject: Re: data corruption when using aic7890 In-reply-to: Your message of Wed, 08 Sep 1999 14:47:35 -0400. <14294.42593.953415.402280@grasshopper.cs.duke.edu> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Wed, 08 Sep 1999 14:57:31 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>On Wed, 8 Sep 1999 14:47:35 -0400 (EDT), Andrew Gallatin said: gallatin> Have you tried BIOS any upgrades? The last time I tried the test it was with BIOS version 1008 or 1009 (don't remember which--I do remember that the last upgrade I tried bumped up the Adaptec BIOS version to 2.11). There is now BIOS version 1010 available for the ASUS P2B-LS. I haven't tried my test with that BIOS. I have seen the same problem on the Supermicro P6DGU as well, which has a different chipset (the P2B-LS is BX, the P6DGU is GX). andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 12:33:45 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 34F9015696 for ; Wed, 8 Sep 1999 12:33:36 -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 11OnRv-0003Gb-00; Wed, 8 Sep 1999 19:32:07 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id VAA00696; Wed, 8 Sep 1999 21:31:18 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199909081931.VAA00696@canyon.demon.nl> Subject: Re: FBSD3.3RC + UMAX astra 1220S + NCR810 => panic In-Reply-To: <199909072236.QAA46618@panzer.kdm.org> from "Kenneth D. Merry" at "Sep 7, 1999 04:36:51 pm" To: ken@kdm.org (Kenneth D. Merry) Date: Wed, 8 Sep 1999 21:31:18 +0200 (CEST) Cc: wilko@yedi.iaf.nl (Wilko Bulte), freebsd-scsi@freebsd.org 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 Ken, Wilko, FreeBSD-scsi readers, I plugged the NCR810 into my W95 system (that already has a NCR810 as controller for the "root" disk). Used the same cable as I did with FreeBSD and W95 would not find my scanner (nor did the NCR bios mention the scanner during startup). I tested the NCR card by connecting my disk/cdrom to it and the system still booted (after I switched the cards, I hate plug and play ;-). So my conclusion (and Wilko also got to the same conclusion on the phone) is that the cable must be broken. I'm going to try to find an other cable (hard because it is an 25SubD-50HD, non-standard ;-(. Let's see what the new cable brings... Rene > Rene de Vries wrote... > > Ken, Wilko, Freebsd-Scsi readers, > > > > This is the continuing saga about a panicing FreeBSD 3.3RC, a NCR810 and > > a Umax 1220s scanner. > > Currently the panic is replaced with a printf (and the retry count is > > decremented) but it did not bring the scanner to life... > > All it had to say was: > > > > da1 at ncr0 bus 0 target 6 lun 0 > > da1: < > Fixed Direct Access SCSI-0 device > > da1: 3.300MB/s transfers > > da1: 0MB (2957417921 0 byte sectors: 0H 0S/T 0C) > > > > And 7 times the "cam_periph_error:...." former panic message... > > > > Which is totally not good as far as I understand SCSI devices. > > Indeed. It looks like the inquiry information is getting totally > corrupted. I suspect a hardware problem of some sort. > > > (I would love to store 2.7Gb on my scanner but somehow I think that this is not > > going to work....) > > > > I talked to Wilko over the phone and he suggested to connect the scanner thru > > the NCR810 and the same cable to my W95 box. Currently it is connected to the > > W95 box with the SCSI adapter that was packaged with the scanner. > > I'll do so tomorrow evening (time permitting). > > That's a good suggestion, let me know what happens. > > Ken -- 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 Wed Sep 8 12:42:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 28CFC1572A for ; Wed, 8 Sep 1999 12:42:16 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id PAA09373; Wed, 8 Sep 1999 15:42:06 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id PAA87189; Wed, 8 Sep 1999 15:41:36 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 8 Sep 1999 15:41:36 -0400 (EDT) To: Andrew Heybey Cc: freebsd-scsi@freebsd.org Subject: Re: data corruption when using aic7890 In-Reply-To: <199909081934.PAA74312@stiegl.niksun.com> References: <14294.45611.153782.537489@grasshopper.cs.duke.edu> <199909081934.PAA74312@stiegl.niksun.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14294.47942.226648.687089@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Heybey writes: > > Well, if you find anything that works, please let me know. I've > mostly abandoned this problem for now (except for prowling the mailing > lists hoping to find that someone else has solved it) because I have > too many other things to do and there is a workaround (use the 40MB/s > connector). However, I'd love to get my performance back... > > andrew What!?? You mean if I just move the cable to the 20Mhz connector, all my problems will just go away??? Even though its just a different port on the same PCI controller? (at least on my P2B-LS) Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 13:32: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (gw.niksun.com [206.20.52.122]) by hub.freebsd.org (Postfix) with ESMTP id 1847914C87 for ; Wed, 8 Sep 1999 13:31:58 -0700 (PDT) (envelope-from ath@niksun.com) Received: from stiegl.niksun.com (stiegl.niksun.com [10.0.0.44]) by arjun.niksun.com (8.8.8/8.8.8) with ESMTP id QAA18194; Wed, 8 Sep 1999 16:31:51 -0400 (EDT) Received: from stiegl.niksun.com (localhost.niksun.com [127.0.0.1]) by stiegl.niksun.com (8.9.2/8.8.7) with ESMTP id QAA74557; Wed, 8 Sep 1999 16:31:49 -0400 (EDT) (envelope-from ath@stiegl.niksun.com) Message-Id: <199909082031.QAA74557@stiegl.niksun.com> From: Andrew Heybey To: Andrew Gallatin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: data corruption when using aic7890 In-reply-to: Your message of Wed, 08 Sep 1999 15:41:36 -0400. <14294.47942.226648.687089@grasshopper.cs.duke.edu> Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: Wed, 08 Sep 1999 16:31:49 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Well, if you find anything that works, please let me know. I've >> mostly abandoned this problem for now (except for prowling the >> mailing lists hoping to find that someone else has solved it) >> because I have too many other things to do and there is a >> workaround (use the 40MB/s connector). However, I'd love to get >> my performance back... gallatin> What!?? You mean if I just move the cable to the 20Mhz gallatin> connector, all my problems will just go away??? Even gallatin> though its just a different port on the same PCI gallatin> controller? (at least on my P2B-LS) Well, I don't know if *your* problems will go away (I'm not 100% sure that your problem is the same as my problem). However, my problem went away went I moved the cable to the plain "Ultra" (20MHz) connector rather than the "Ultra2" (40MHz) connector. Peak performance is lower (at least with multiple disks on the bus). Sorry, I thought that I had mentioned this someplace. Maybe I should submit a follow-up to the PR to mention this work-around. andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 14:29:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 882C014DAA for ; Wed, 8 Sep 1999 14:29:46 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA12196; Wed, 8 Sep 1999 17:29:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA87397; Wed, 8 Sep 1999 17:28:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 8 Sep 1999 17:28:34 -0400 (EDT) To: Andrew Heybey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: data corruption when using aic7890 In-Reply-To: <199909082031.QAA74557@stiegl.niksun.com> References: <14294.47942.226648.687089@grasshopper.cs.duke.edu> <199909082031.QAA74557@stiegl.niksun.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14294.54296.976860.242067@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Heybey writes: > gallatin> What!?? You mean if I just move the cable to the 20Mhz > gallatin> connector, all my problems will just go away??? Even > gallatin> though its just a different port on the same PCI > gallatin> controller? (at least on my P2B-LS) > > Well, I don't know if *your* problems will go away (I'm not 100% sure > that your problem is the same as my problem). However, my problem > went away went I moved the cable to the plain "Ultra" (20MHz) > connector rather than the "Ultra2" (40MHz) connector. > > Peak performance is lower (at least with multiple disks on the bus). > > Sorry, I thought that I had mentioned this someplace. Maybe I should > submit a follow-up to the PR to mention this work-around. You mentioned it to me, in your original follow up. But I took it to mean you'd purchased a working UltraWide controller & plugged it into a PCI slot. I've now plugged my drives into the UltraWide connector on the motherboard. This won't cause a slowdown for me, as they are only 20Mhz UltraWide drives anyway. I'm running the test again. I'll let you know how it comes out. Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Sep 8 17:40:38 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 0315214BFA for ; Wed, 8 Sep 1999 17:40:32 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-22.dialup.HiWAAY.net [216.180.14.22]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id TAA19265; Wed, 8 Sep 1999 19:40:17 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA27449; Wed, 8 Sep 1999 19:11:06 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199909090011.TAA27449@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kirby Cc: scsi@FreeBSD.ORG From: David Kelly Subject: Re: Reformatting a 520-byte-per-sector drive In-reply-to: Message from Kris Kirby of "Tue, 07 Sep 1999 22:59:07 CDT." <37D5DF0B.FFF98713@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Sep 1999 19:11:06 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kris Kirby writes: > da3 at ahc0 bus 0 target 0 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 5.000MB/s transfers (5.000MHz, offset 12), Tagged Queueing Enabled > da3: 957MB (1931265 520 byte sectors: 64H 32S/T 943C) > > I want this to be 512 bytes/sector. Kris, I dunno if FreeBSD is smart enough to live with the drive blocked at 520 octets, if so then use it that way. I took an IBM 9G HD out of a StorageTek/Clariion RAID and tried every Win9x, NT, Macintosh, SGI, and Sun utility I could find for changing the block size "back" to 512. The drive would happily chug right along doing a low level format. But after it completed it was right back there at 520. I believe IBM ships drives with custom firmware for RAID OEM's with all parameters locked with the OEM's selections. Unless you can find new firmware and the utility to load it, you are probably stuck. Oh, and the drive wouldn't map out bad blocks either. After this exercise I was able to put the drive back into the RAID as a new drive, then bind it back into the RAID5. The binding process completed before I checked it the next morning. -- 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 Thu Sep 9 8:59:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AE6815F1C for ; Thu, 9 Sep 1999 08:59:27 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA01479; Thu, 9 Sep 1999 11:58:25 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA98386; Thu, 9 Sep 1999 11:57:55 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 9 Sep 1999 11:57:54 -0400 (EDT) To: Andrew Heybey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: data corruption when using aic7890 In-Reply-To: <199909082031.QAA74557@stiegl.niksun.com> References: <14294.47942.226648.687089@grasshopper.cs.duke.edu> <199909082031.QAA74557@stiegl.niksun.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14295.54853.441698.273640@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Heybey writes: > gallatin> What!?? You mean if I just move the cable to the 20Mhz > gallatin> connector, all my problems will just go away??? Even > gallatin> though its just a different port on the same PCI > gallatin> controller? (at least on my P2B-LS) > > Well, I don't know if *your* problems will go away (I'm not 100% sure There is still no joy in mudville -- I'm getting the errors even after moving the connector. I've upgraded my P2B-LS bios from 1006 to 1011. After the bios upgrade, the 7890 bios went from v2.01 to v2.11. While I had a monitor on it, I also took the PCI latency setting from 32->128. I'm re-running my tests now to see if the bios upgrade had any effect. Sigh, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Sep 9 12: 0:54 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 3E262152BD for ; Thu, 9 Sep 1999 12:00:48 -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 11P9Pu-0004oJ-00; Thu, 9 Sep 1999 18:59:30 +0000 Received: (from rene@localhost) by canyon.demon.nl (8.9.3/8.9.3) id UAA04631; Thu, 9 Sep 1999 20:42:41 +0200 (CEST) (envelope-from rene) From: Rene de Vries Message-Id: <199909091842.UAA04631@canyon.demon.nl> Subject: UMAX + NCR810 -> panic.... To: ken@kdm.org (Kenneth D. Merry), wilko@yedi.iaf.nl (Wilko Bulte), freebsd-scsi@freebsd.org Date: Thu, 9 Sep 1999 20:42:41 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ken, Wilko, FreeBSD-SCSI readers, Today I bought a new cable and connected the Umax scanner to my system. $ camcontrol inquiry pass4 pass4: Fixed Scanner SCSI-2 device pass4: Serial Number › pass4: 3.300MB/s transfers Which means: Yes, it works. Shows again that cables are very important. Now lets see if I can get sane to work (it does not seem to find my scanner...) 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 Thu Sep 9 14:18:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pathlink.net (linda.pathlink.com [165.113.238.197]) by hub.freebsd.org (Postfix) with ESMTP id 0196715259 for ; Thu, 9 Sep 1999 14:18:22 -0700 (PDT) (envelope-from kachun@pathlink.com) Received: from dvl-1 (dvl-1.pathlink.com [207.211.168.211]) by pathlink.net (8.9.3/8.8.7) with SMTP id OAA39115; Thu, 9 Sep 1999 14:17:29 -0700 (PDT) Message-Id: <199909092117.OAA39115@pathlink.net> To: gallatin@cs.duke.edu Subject: Re: data corruption when using aic7890 Cc: freebsd-scsi@freebsd.org From: kachun@pathlink.com (Kachun Lee) Date: Thu, 09 Sep 1999 14:17:03 -0700 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: <14295.54853.441698.273640@grasshopper.cs.duke.edu> References: <199909082031.QAA74557@stiegl.niksun.com> <14295.54853.441698.273640@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <14295.54853.441698.273640@grasshopper.cs.duke.edu>, you say... > > >Andrew Heybey writes: > > gallatin> What!?? You mean if I just move the cable to the 20Mhz > > gallatin> connector, all my problems will just go away??? Even > > gallatin> though its just a different port on the same PCI > > gallatin> controller? (at least on my P2B-LS) > > > > Well, I don't know if *your* problems will go away (I'm not 100% sure > >There is still no joy in mudville -- I'm getting the errors even after >moving the connector. > >I've upgraded my P2B-LS bios from 1006 to 1011. After the bios >upgrade, the 7890 bios went from v2.01 to v2.11. While I had a >monitor on it, I also took the PCI latency setting from 32->128. >I'm re-running my tests now to see if the bios upgrade had any >effect. > >Sigh, > >Drew I believe I am seeing similar problem as you did. I have this NFS server - P2B-DS (only 1 CPU) + extra 7890 + 13 ST118273LW (18G LVD) - panics once every several days with 'ufs_dirbad: bad dir' or 'fault on nofault entry'. I spend past 4 months swapping out every pieces of hardware with our other systems that would run for months. The only variable is that this is our 1st server using LVD (Ultra2) drives. You may have confirmed my suspicion that there was a problem with 7890 running Ultra2 drives. I tried upgrade the adaptec BIOS to v2.11 and increaed the PCI lateny setting to 128, but that did not solve the problem. I am at the point of giving up on the adaptec controller. I saw you mentioned that you had no problem with the NCR 35C875 chip. I was wondering which board manufacturer did you use . Do you know if they make a dual channel LVD (Ultra2-wide - we need the LVD bus because of the cable length) board using the NCR 35C875(6)? Or anyone has success with one? Regards >------------------------------------------------------------------------------ >Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin >Duke University Email: gallatin@cs.duke.edu >Department of Computer Science Phone: (919) 660-6590 > > >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 10 12:42:40 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 41A8E15DA7; Fri, 10 Sep 1999 12:42:38 -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 NAA02899; Fri, 10 Sep 1999 13:42:59 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909101942.NAA02899@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Tue, 07 Sep 1999 16:00:38 EDT." <14293.26481.521753.519004@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 13:42:59 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >Hi, > >I have a bunch of ASUS P2B-LS motherboards with on-board AIC7890 U2 >controllers. I'm running a kernel with rev 1.20 of >src/sys/pci/ahc_pci.c (eg, after the CACHETHEN fix). Can you see if this has any effect on your problem? This is the setting left over from the BIOS on my systems here. I would expect the best performance to be a setting of RD_DFTHRSH_MIN|WR_DFTHRSH_100 but lets try this first. -- Justin ==== //depot/FreeBSD-current/src/sys/pci/ahc_pci.c#22 - /usr/src/sys/pci/ahc_pci.c ==== *** /tmp/tmp.2882.0 Fri Sep 10 13:36:27 1999 --- /usr/src/sys/pci/ahc_pci.c Fri Sep 10 13:35:34 1999 *************** *** 826,832 **** * and 75% on ULTRA2 controllers. */ if ((ahc->features & AHC_ULTRA2) != 0) { ! ahc_outb(ahc, DFF_THRSH, RD_DFTHRSH_75|WR_DFTHRSH_75); } else { ahc_outb(ahc, DSPCISTATUS, DFTHRSH_100); } --- 826,832 ---- * and 75% on ULTRA2 controllers. */ if ((ahc->features & AHC_ULTRA2) != 0) { ! ahc_outb(ahc, DFF_THRSH, RD_DFTHRSH_MIN|WR_DFTHRSH_MIN); } else { ahc_outb(ahc, DSPCISTATUS, DFTHRSH_100); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 10 13:45:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 899C914F4F; Fri, 10 Sep 1999 13:45:18 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA19708; Fri, 10 Sep 1999 16:45:16 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA01966; Fri, 10 Sep 1999 16:44:46 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 10 Sep 1999 16:44:45 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-Reply-To: <199909101942.NAA02899@caspian.plutotech.com> References: <14293.26481.521753.519004@grasshopper.cs.duke.edu> <199909101942.NAA02899@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14297.27236.577546.795593@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > > > >Hi, > > > >I have a bunch of ASUS P2B-LS motherboards with on-board AIC7890 U2 > >controllers. I'm running a kernel with rev 1.20 of > >src/sys/pci/ahc_pci.c (eg, after the CACHETHEN fix). > > Can you see if this has any effect on your problem? This is the setting > left over from the BIOS on my systems here. I would expect the best > performance to be a setting of RD_DFTHRSH_MIN|WR_DFTHRSH_100 but lets > try this first. This does seem to have an effect, so you might have the right knob to twiddle! Unfortunately, the change seems to make things even worse. The errors are occurring much more freqently now. Also, the errors are occuring later in the page. Where as before, the errors would almost always occur in the first 500 bytes of the page, now they're occuring near the end of the page (some around 2500 bytes, most near 3900). I'm as a wild stab in the dark, I'm trying RD_DFTHRSH_MAX|WR_DFTHRSH_MIN right now. Thanks!! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 10 13:48:52 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 082BA1602D; Fri, 10 Sep 1999 13:48:47 -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 OAA03111; Fri, 10 Sep 1999 14:49:08 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909102049.OAA03111@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: "Justin T. Gibbs" , scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Fri, 10 Sep 1999 16:44:45 EDT." <14297.27236.577546.795593@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 14:49:08 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >This does seem to have an effect, so you might have the right knob to >twiddle! > >Unfortunately, the change seems to make things even worse. The >errors are occurring much more freqently now. Also, the errors are >occuring later in the page. Where as before, the errors would almost >always occur in the first 500 bytes of the page, now they're occuring >near the end of the page (some around 2500 bytes, most near 3900). What are the dynamics of your test program? Are you sure that this is a problem with reads and not with writes? If it is a problem with reads, WR_DFTHRSH is what you should be tweaking, since the directions are relative to the bus master (i.e. the aic7xxx part). -- 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 10 14:50:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 01D6C152AF; Fri, 10 Sep 1999 14:50:20 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA21258; Fri, 10 Sep 1999 17:50:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA02122; Fri, 10 Sep 1999 17:49:48 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 10 Sep 1999 17:49:48 -0400 (EDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-Reply-To: <199909102049.OAA03111@caspian.plutotech.com> References: <14297.27236.577546.795593@grasshopper.cs.duke.edu> <199909102049.OAA03111@caspian.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14297.30000.669959.29706@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > >This does seem to have an effect, so you might have the right knob to > >twiddle! > > > >Unfortunately, the change seems to make things even worse. The > >errors are occurring much more freqently now. Also, the errors are > >occuring later in the page. Where as before, the errors would almost > >always occur in the first 500 bytes of the page, now they're occuring > >near the end of the page (some around 2500 bytes, most near 3900). > > What are the dynamics of your test program? Are you sure that this > is a problem with reads and not with writes? If it is a problem > with reads, WR_DFTHRSH is what you should be tweaking, since the > directions are relative to the bus master (i.e. the aic7xxx part). > > -- > Justin We're using a home-grown program called 'hunt' (as in hunt for errors). I've left you source & an i386 binary on freefall in ~gallatin/hunt. Run it with the arguments -touch= -fileio= -size= So on a 512MB x86, you'd say './hunt.i386 -touch=4096 -fileio=zot -size=131072' It sequentially writes out the data & reads it back multiple times. The data set is large enough (>physical memory) so that its not being cached. So at least one successful read of the entire file indicates that it was written properly. When an error is encountered, that page of the file is re-written with the correct data. It prints '<' when it starts initializing, '>' after the file is completely written, and '.' for each successful read of the file. On an error, you'll see some information regarding what was read & what was expected. So, using an NCR875 controller I see: <>!.............................................. On the 7890, I'm seeing: <>!..........##error 1 page 16167 expected [0x03f27ff8] saw [0x056deff8] My tweak didn't seem to help either. The default setting seem to be the most reliable. Should I continue to tweak this variable, or do you have other ideas? I really appreciate your help. We've got 20 of these machines & I'd really like to avoid having to purchase 20 scsi controllers to replace the on-board ones. Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Sep 10 15:36:35 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 062D315E12; Fri, 10 Sep 1999 15:36:19 -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 QAA03334; Fri, 10 Sep 1999 16:36:35 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909102236.QAA03334@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: "Justin T. Gibbs" , scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Fri, 10 Sep 1999 17:49:48 EDT." <14297.30000.669959.29706@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 16:36:35 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >My tweak didn't seem to help either. The default setting seem to >be the most reliable. Should I continue to tweak this variable, or do >you have other ideas? I would continue to tweak the variable. I assume you tried setting the read threshold to MIN and the write threshold to MAX? In other words, don't start a read from host memory until the FIFO is almost empty, and don't start a write to host memory until the FIFO is almost full. The assumption here is that PCI is faster than the SCSI bus speed so we'll get the longest bursts this way. >I really appreciate your help. We've got 20 of these machines & I'd >really like to avoid having to purchase 20 scsi controllers to replace >the on-board ones. I'd like to ensure that the driver works correctly too. -- 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 10 18:38:30 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 2671015276; Fri, 10 Sep 1999 18:38:28 -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 TAA03862; Fri, 10 Sep 1999 19:38:47 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909110138.TAA03862@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 Cc: Andrew Gallatin , "Justin T. Gibbs" , scsi@freebsd.org, gibbs@freebsd.org, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Fri, 10 Sep 1999 16:36:35 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Sep 1999 19:38:47 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I would continue to tweak the variable. I assume you tried setting >the read threshold to MIN and the write threshold to MAX? In other >words, don't start a read from host memory until the FIFO is almost >empty, and don't start a write to host memory until the FIFO is almost >full. The assumption here is that PCI is faster than the SCSI bus >speed so we'll get the longest bursts this way. I misread the data book. If you set them both to MAX, then you would get this behavior. The read fifo threshold is based on the amount of empty space in the fifo, not the amount of data in it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 11 0:20:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 0E26215332; Sat, 11 Sep 1999 00:20:42 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA17425; Sat, 11 Sep 1999 00:20:30 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA19641; Sat, 11 Sep 1999 00:20:29 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA06762; Sat, 11 Sep 1999 00:20:28 -0700 (PDT) From: Don Lewis Message-Id: <199909110720.AAA06762@salsa.gv.tsc.tdk.com> Date: Sat, 11 Sep 1999 00:20:28 -0700 In-Reply-To: "Justin T. Gibbs" "Re: data corruption when using aic7890" (Sep 10, 4:36pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Justin T. Gibbs" , Andrew Gallatin Subject: Re: data corruption when using aic7890 Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG, anderson@cs.duke.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sep 10, 4:36pm, "Justin T. Gibbs" wrote: } Subject: Re: data corruption when using aic7890 } >My tweak didn't seem to help either. The default setting seem to } >be the most reliable. Should I continue to tweak this variable, or do } >you have other ideas? } } I would continue to tweak the variable. I assume you tried setting } the read threshold to MIN and the write threshold to MAX? In other } words, don't start a read from host memory until the FIFO is almost } empty, and don't start a write to host memory until the FIFO is almost } full. The assumption here is that PCI is faster than the SCSI bus } speed so we'll get the longest bursts this way. Please tell me that this hardware doesn't silently corrupt data on a FIFO underflow or overflow without at least setting a flag somewhere ... I've got one of these at home and am getting ready to put three more in service at work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 11 7:38:40 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 5147014E39; Sat, 11 Sep 1999 07:38:37 -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 IAA08309; Sat, 11 Sep 1999 08:38:52 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909111438.IAA08309@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis Cc: "Justin T. Gibbs" , Andrew Gallatin , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG, anderson@cs.duke.edu Subject: Re: data corruption when using aic7890 In-reply-to: Your message of "Sat, 11 Sep 1999 00:20:28 PDT." <199909110720.AAA06762@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Sep 1999 08:38:52 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Please tell me that this hardware doesn't silently corrupt data on a >FIFO underflow or overflow without at least setting a flag somewhere ... I can't tell you what it does as I haven't reproduced the problem myself and haven't seen enough information to hazard a guess at just what is happening. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Sep 11 22:49:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f294.hotmail.com [207.82.251.185]) by hub.freebsd.org (Postfix) with SMTP id 6A7FA14DB8 for ; Sat, 11 Sep 1999 22:49:44 -0700 (PDT) (envelope-from mut3x@hotmail.com) Received: (qmail 40113 invoked by uid 0); 12 Sep 1999 05:49:44 -0000 Message-ID: <19990912054944.40112.qmail@hotmail.com> Received: from 206.165.200.116 by www.hotmail.com with HTTP; Sat, 11 Sep 1999 22:49:44 PDT X-Originating-IP: [206.165.200.116] From: "Mutex Records USA" To: scsi@freebsd.org Subject: Re: data corruption when using aic7890 Date: Sat, 11 Sep 1999 22:49:44 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i have one in a server right now (supermicro motherboard p6dgs) that i have been testing... it has a 5 day uptime right now, and it's working OK so far... or am i missing something and not noticing? i am keeping a close eye on the logs and my data and it seems fine so far. (it's running 3.2-stable, apache, sendmail, cyrus imap, php stuff, etc, i am testing the (so far, pretty cool) horde/imp php3 webmail stuff on it.) adam. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message