From owner-freebsd-scsi Sun Apr 13 22:54:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17384 for freebsd-scsi-outgoing; Sun, 13 Apr 1997 22:54:34 -0700 (PDT) Received: from sendero.i-connect.net ([206.190.143.100]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA17369 for ; Sun, 13 Apr 1997 22:54:29 -0700 (PDT) Received: (qmail 6821 invoked by uid 1000); 14 Apr 1997 05:43:11 -0000 Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 13 Apr 1997 19:01:06 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: SCSI Problems Since 2.2-BETA_A of 13-Feb-1997 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I apologize if i am repeating known truth, jumping in the middle of a conversation or missing the solution (I was very busy last few weeks), but this is serious. We are having a severe problem with SCSI devices (wide) connected to AHA-2940W or 2940UW (PCI). The problem manifests itself as (more or less): sd10(ahc1:13:0): timed out in dataout phase SCSISIGI = 0x0 SEQADDR = {0x6,0xf,0xa....} ahc1: Issued channel A Bus reset spec_getpage I/O read error vm_fault: pager input ... With kernels up to and including that mentioned in the Subject: line, we get this error once and it clears and continues for a time. Anything we have that is later goes into an endless loop of these, from which only PWER CYCLE will save. Now, the problem is probably real. getting the SCSI ERROR is not what I am asking for help with. The endless loop is. The system has two controllers a 2940W and a 2940UW. I cannot see any difference in behavior (but could be wrong. To these controllers are hooked up: ahc0 (the 2940W): Iomega Jaz, Ymaha CDR-100 Sony SDT-7000/BM (DAT) and 8 Seagate 2713 (2GB Baracuda. The Baracudas are on an external box, with a good cable and terminated via the internal termination on the last drive. ahc1 (the 2940Uw): 8 Quantum 4GB drives in a ``raid'' box. Each group is arranged as a CCD RAID-0 array, 4 drives per HBA. The arrangement is suboptimal in that drives are accessed sequentially on the same bus. It is also suboptimal as noise must be on the bus. Close examination of the bus reveals that when an error occures, a drive stays selected and the bus stays locked up. It stays locked up during power cycle on the drives (as soon as the drive is spinning again, it is selected again). It survives reboots and motherboard resets. It only will release if the motherboard is powered off and on again. This hard-core stuckiness is only evident with newer revisions of the aic7xxx driver. Up to the 2.2-BETA_A, the errors happen, rarely, but the driver resets the bus and recovers nicely. I am not sure if this is a ccd problem (timing, etc.; I do not think so), or a scsi layer problem (again, I do not think so), or an aic7xxx problem. I also relize that this is more hardware than most of us use, but represents about 1/3 of what we want done (48 drives per system as a base configuration). Any help I can get/give will be appreciated! Thanx, Simon ng known truth, jumping in the middle of a conversation or missing the solution (I was very busy last few weeks), but this is serious. We are having a severe problem with SCSI devices (wide) connected to AHA-2940W or 2940UW (P From owner-freebsd-scsi Tue Apr 15 07:55:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13765 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 07:55:29 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA13759 for ; Tue, 15 Apr 1997 07:55:21 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id KAA11354 for scsi@freebsd.org; Tue, 15 Apr 1997 10:42:51 -0400 (EDT) From: Peter Dufault Message-Id: <199704151442.KAA11354@hda.hda.com> Subject: scsi(8) and (3) changes To: scsi@freebsd.org Date: Tue, 15 Apr 1997 10:42:50 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've moved on to posix 4 related projects after getting no feedback about the proposed changes to scsi(8) and scsi(3). If anyone has an interest and the time they should take a look at freebsd.org:~ftp/pub/dufault/scsinew.tgz. If people think it is good I'll look at moving it into -current. Briefly, it adds support for storing command strings in a scsicap file (giving a place to put small script strings) and for being driven by other programs (including a sample Tk display of your disk error locations), and as an aside running as a server (for standalone "embedded" SCSI systems). Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Tue Apr 15 10:01:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA21424 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 10:01:54 -0700 (PDT) Received: from othello (othello.nac.net [207.99.2.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA21418 for ; Tue, 15 Apr 1997 10:01:50 -0700 (PDT) Received: from [207.99.2.234] by othello (NTMail 3.02.13) with ESMTP id la515071 for ; Tue, 15 Apr 1997 13:01:45 -0400 Message-Id: <3.0.32.19970415122245.00b56480@mail.nac.net> X-Sender: alex@mail.nac.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 15 Apr 1997 13:02:11 -0300 To: Peter Dufault , scsi@FreeBSD.ORG From: Alex Rubenstein Subject: Re: scsi(8) and (3) changes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Does this fix the adaptec 2940uw timeout problem? At 10:42 AM 4/15/97 -0400, Peter Dufault wrote: >I've moved on to posix 4 related projects after getting no feedback >about the proposed changes to scsi(8) and scsi(3). If anyone has >an interest and the time they should take a look at >freebsd.org:~ftp/pub/dufault/scsinew.tgz. If people think it is >good I'll look at moving it into -current. > >Briefly, it adds support for storing command strings in a scsicap >file (giving a place to put small script strings) and for being >driven by other programs (including a sample Tk display of your >disk error locations), and as an aside running as a server (for >standalone "embedded" SCSI systems). > >Peter > >-- >Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation >HD Associates, Inc. Voice: 508 433 6936 > From owner-freebsd-scsi Tue Apr 15 12:24:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA03479 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 12:24:55 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA03471 for ; Tue, 15 Apr 1997 12:24:51 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id VAA18155; Tue, 15 Apr 1997 21:15:32 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.5/8.8.2) id UAA18566; Tue, 15 Apr 1997 20:31:21 +0200 (CEST) Message-ID: <19970415203121.01225@klemm.gtn.com> Date: Tue, 15 Apr 1997 20:31:21 +0200 From: Andreas Klemm To: alex@nac.net Cc: scsi@FreeBSD.ORG Subject: Re: Adaptec on FreeBSD References: <33533C94.5D4B@nac.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <33533C94.5D4B@nac.net>; from Alex Rubenstein on Tue, Apr 15, 1997 at 04:30:12AM -0400 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2-RELEASE Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Alex ! On Tue, Apr 15, 1997 at 04:30:12AM -0400, Alex Rubenstein wrote: > I am having the same exact problems as you with a 2940UW giving me > strange Timeouts/freezes. Did you ever solve the problem? I updated my machine to the newest version 2.2-stable, so that Justin's newest SCSI patches are included. You have three choices here, since SCSI changes have been merged from HEAD into 2.1.x and 2.2.x: - FreeBSD-2.1.7-stable (the RELENG_2_1 branch of the CVS source repository) - FreeBSD-2.2-stable (the RELENG_2_2 branch of the source repository). - FreeBSD-current (the HEAD branch of the CVS source repository) I enabled the following SCSI options, since Justin said, that the TAGGED queuing code is the best tested now ;-) options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO Then I got still QUEUE full race conditions ... but this is not FreeBSD's fault, it's the fault of my harddisks, which can't get more than a few tags managed ! (Shit !) Justin made the proposal, that I should set the amount of allowed tags to 2. I made the necessary changes and voila, everything runs very very fine and stable now ! Big thanks to Justin ! Andreas /// My hard and cruel patch: Index: aic7xxx.c =================================================================== RCS file: /local/CVS/src/sys/i386/scsi/aic7xxx.c,v retrieving revision 1.81.2.23 diff -u -r1.81.2.23 aic7xxx.c --- aic7xxx.c 1997/04/14 02:31:44 1.81.2.23 +++ aic7xxx.c 1997/04/15 18:30:27 @@ -1910,7 +1910,7 @@ if (ahc->scb_data->maxhscbs >= 16 || (ahc->flags & AHC_PAGESCBS)) { /* Default to 8 tags */ - xs->sc_link->opennings += 6; + xs->sc_link->opennings = 2; } else { /* * Default to 4 tags on whimpy @@ -1920,7 +1920,7 @@ * slots. We should really have a better * way of providing fairness. */ - xs->sc_link->opennings += 2; + xs->sc_link->opennings = 2; } } } -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-scsi Tue Apr 15 13:21:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA08521 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 13:21:46 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA08516 for ; Tue, 15 Apr 1997 13:21:40 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id OAA27369; Tue, 15 Apr 1997 14:17:25 -0600 (MDT) Message-Id: <199704152017.OAA27369@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Andreas Klemm cc: alex@nac.net, scsi@FreeBSD.ORG Subject: Re: Adaptec on FreeBSD In-reply-to: Your message of "Tue, 15 Apr 1997 20:31:21 +0200." <19970415203121.01225@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Apr 1997 14:15:48 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >My hard and cruel patch: You're actually running with 3 tags right now since one of the openings is held by the scsi_xfer that contains the inquiry data we use to determine if tagged queuing is availible on the target. You should simply remove any manipulation of the tag count if you really want to keep the tag count at two (which is what it defaults to since the driver can handle up to two transactions for untagged devices). -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue Apr 15 16:23:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA19131 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 16:23:57 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA19100 for ; Tue, 15 Apr 1997 16:23:51 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id TAA12561; Tue, 15 Apr 1997 19:09:58 -0400 (EDT) From: Peter Dufault Message-Id: <199704152309.TAA12561@hda.hda.com> Subject: Re: scsi(8) and (3) changes In-Reply-To: <3.0.32.19970415122245.00b56480@mail.nac.net> from Alex Rubenstein at "Apr 15, 97 01:02:11 pm" To: alex@nac.net (Alex Rubenstein) Date: Tue, 15 Apr 1997 19:09:57 -0400 (EDT) Cc: scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Does this fix the adaptec 2940uw timeout problem? Nope. It is a user program only. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Tue Apr 15 18:01:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA25609 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 18:01:18 -0700 (PDT) Received: from bigdog.fred.net (bigdog.fred.net [204.215.84.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25601 for ; Tue, 15 Apr 1997 18:01:13 -0700 (PDT) Received: from bigdog.fred.net (bigdog.fred.net [204.215.84.2]) by bigdog.fred.net (8.8.5/8.6.12) with SMTP id UAA17809 for ; Tue, 15 Apr 1997 20:56:45 -0400 (EDT) Date: Tue, 15 Apr 1997 20:56:44 -0400 (EDT) From: Dale Ghent To: freebsd-scsi@freebsd.org Subject: Major 2940UW and 2.2.1 problems... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently upgraded from 2.1.5-RELEASE to 2.2.1, and have been running into some major and fatal SCSI problems. I'mm running a heavily-loaded machine (news) that has 3 2940UW controllers in it. After upgrading to 2.2.1 the machine has become quite unstable. The machine would reboot itself with no warning at all. A check in /var/log/messages shows this error right before reboot: Apr 15 19:21:40 news /kernel: sd4(ahc1:5:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 15 19:21:40 news /kernel: SEQADDR == 0x5 Apr 15 19:21:40 news /kernel: Ordered Tag queued Apr 15 19:21:40 news /kernel: sd4(ahc1:5:0): SCB 0x7 timedout while recovery in progress Apr 15 19:21:41 news /kernel: sd4(ahc1:5:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 15 19:21:41 news /kernel: SEQADDR == 0x7 Apr 15 19:21:41 news /kernel: sd4(ahc1:5:0): Queueing an Abort SCB Apr 15 19:21:41 news /kernel: sd4(ahc1:5:0): Abort Message Sent Apr 15 19:21:41 news /kernel: sd4(ahc1:5:0): SCB 0 - Abort Completed. Apr 15 19:21:41 news /kernel: sd4(ahc1:5:0): no longer in timeout Apr 15 19:21:41 news /kernel: Ordered Tag sent Apr 15 19:21:50 news /kernel: sd4(ahc1:5:0): SCB 0x5 - timed out in message out phase, SCSISIGI == 0x0 Apr 15 19:21:50 news /kernel: SEQADDR == 0x0 Apr 15 19:21:50 news /kernel: Ordered Tag queued Apr 15 19:21:50 news /kernel: sd4(ahc1:5:0): SCB 0x4 timedout while recovery in progress Please, please let there be a solution for this. This crashes the machine about 6 times a day and its really bad. This error always happens on the same controller and with the same drive. I've double-checked termination and cables, and replaced them, but no luck. Any ideas? Thanks Dale From owner-freebsd-scsi Tue Apr 15 19:10:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA29366 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 19:10:59 -0700 (PDT) Received: from nucleus.elec.uq.edu.au (root@nucleus.elec.uq.edu.au [130.102.96.81]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA29352 for ; Tue, 15 Apr 1997 19:10:49 -0700 (PDT) Received: from dendrite.elec.uq.edu.au (marcusg@dendrite.elec.uq.edu.au [130.102.96.83]) by nucleus.elec.uq.edu.au (8.8.5/8.6.12) with SMTP id CAA16308 for ; Wed, 16 Apr 1997 02:10:46 GMT Message-ID: <33543524.41C67EA6@elec.uq.edu.au> Date: Wed, 16 Apr 1997 12:10:44 +1000 From: Marcus Gallagher Organization: Electrical & Computer Engineering, University of Queensland X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2-GAMMA i386) MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc To: freebsd-scsi@freebsd.org Subject: FreeBSD 2.2.1 SCSI 2940 Problems - Help! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi - we are having problems with our 2.2.1-RELEASE system freezing regularly, most notably when performing a level 0 dump (but also at other times - perhaps when SCSI traffic is high?). We have 5 slices to back up and somewhere in dumping the third slice (the first big one) it freezes - quite reliably :) Sometimes we have to reboot it (reset switch), sometimes it reboots itself immediately. It has also crashed once on a lot of disk copying, and some other times. System specification: Pentium 120 Triton P5I437P4/FMB chipset Adaptec 2940W SCSI controller SONY SDT-5000 SCSI DAT tape 2* SEAGATE ST15230W SCSI hard disks Cirrus Logic 5430 PCI graphics card . Going to 2.2.1 from GAMMA fixed a SCSI bus resetting -> crash problem which other people have reported, but this freezing thing persists. I have tried GENERIC & custom kernels - both crash similarly. (note: I have been running the system for about 1 1/2 yrs with just a 2.1 system until 2.2-GAMMA. That never crashed. The system only began crashing/freezing after my "upgrade"). The current system was created by running a "make world" on the cvsup'd 2.2.1 source, along with a custom kernel recompilation. I don't have anything to show for it in the logs - (/var/log/messages). Stuff like: /kernel: sd1(ahc0:3:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 no longer occurs since I upgraded to 2.2.1 . I haven't tried kernel debugging or SCSIDEBUG stuff yet partly because I know almost nothing about it, partly because people want this machine up most of the time. I think it's another adaptec 2940 driver problem, and am thinking of trying the newest 2.2-RELENG source, but I don't know whether that's really the problem, or if it is, whether it's recently been fixed. any advice appreciated, thanks, Marcus. -- =-----= Marcus Gallagher->marcusg@elec.uq.edu.au http://www.elec.uq.edu.au/~marcusg/ Electrical & Computer Engineering, University of Queensland Brisbane. Q. 4072. Australia. -- "And to this day, there is very little a memory-hogging, CD-ROM loading OS can do that the Amiga can't." John C. Dvorak, PC Magazine, October 22, 1996. =-----= From owner-freebsd-scsi Tue Apr 15 20:14:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA02106 for freebsd-scsi-outgoing; Tue, 15 Apr 1997 20:14:33 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA02097 for ; Tue, 15 Apr 1997 20:14:00 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id XAA12293 for ; Tue, 15 Apr 1997 23:13:02 -0400 (EDT) Date: Tue, 15 Apr 1997 23:13:01 -0400 (EDT) From: Brian Tao To: scsi@FreeBSD.ORG Subject: Best bet for stable AHA-2940UW server? In-Reply-To: <19970415203121.01225@klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am putting together an NFS server for a client with about 30,000 users. He already has a P200 with two Adaptec 2940UW controllers and a handful of 4.3GB ultrawide drives to go with them. What is the most sane choice of FreeBSD release to go with for this server? 2.2.1 seems to have all sorts of problems with the Adaptec. Should I try 3.0-970209-SNAP, or go with 2.2.1 and grab the newest aic7xxx.c? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-scsi Wed Apr 16 02:51:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA13077 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 02:51:53 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA13072 for ; Wed, 16 Apr 1997 02:51:49 -0700 (PDT) Received: from m1.cs.man.ac.uk (0@m1.cs.man.ac.uk [130.88.13.4]) by who.cdrom.com (8.8.5/8.6.11) with SMTP id CAA04772 for ; Wed, 16 Apr 1997 02:51:42 -0700 (PDT) Received: from amu7.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL6) id AA11617; Wed, 16 Apr 97 10:49:56 BST Date: Wed, 16 Apr 97 10:50:23 BST From: David Alan Gilbert Message-Id: <9704160950.AA14274@amu7.cs.man.ac.uk> To: scsi@freebsd.org, taob@nbc.netcom.ca Subject: Re: Best bet for stable AHA-2940UW server? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well you could try 2.2-GAMMA. I'm running a version from mid-February. The machine has been 20 days or so now (although I had to restart mountd due to a bug I introduced.....) Its a P200 with 64MB of RAM an Adaptec 2940UW running a 4GB Seagate Barra and a 9GB Micropolis (both narrow non-ultra). (and a 3GB EIDE) The only problems I've had with the SCSI driver in that version is that it gets upset when the drives are upset - It doesn't like to stay up when the drives report bad blocks. The machine is an NFS server connected via 100MBps ether (Ether express Pro100B) exported to about 400 machines with typically about 15 actually having it mounted. Dave From owner-freebsd-scsi Wed Apr 16 07:42:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA00630 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 07:42:54 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA00624 for ; Wed, 16 Apr 1997 07:42:50 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id JAA16133; Wed, 16 Apr 1997 09:42:39 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma016131; Wed Apr 16 09:42:36 1997 Received: from jake.lodgenet.com ([10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id JAA09362; Wed, 16 Apr 1997 09:42:21 -0500 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.5/8.6.12) with ESMTP id JAA00650; Wed, 16 Apr 1997 09:42:43 -0500 (CDT) Message-Id: <199704161442.JAA00650@jake.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Peter Dufault cc: scsi@freebsd.org Subject: Re: scsi(8) and (3) changes In-reply-to: Your message of "Tue, 15 Apr 1997 10:42:50 EDT." <199704151442.KAA11354@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Apr 1997 09:42:42 -0500 From: "Eric L. Hernes" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Dufault writes: >freebsd.org:~ftp/pub/dufault/scsinew.tgz. If people think it is >good I'll look at moving it into -current. Yes, I for one would appreciate it. Have you thought about making the Tcl stuff into a .so and loading it directly instead of linking whole new executable? Or maybe swig-ifying libscsi, so it'd work with Tcl and Perl? I really like the idea of using Tcl to glue scsi stuff together. > >Peter > >-- >Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation >HD Associates, Inc. Voice: 508 433 6936 eric. -- erich@rrnet.com http://rrnet.com/~erich erich@freebsd.org http://www.freebsd.org/~erich erich@lodgenet.com From owner-freebsd-scsi Wed Apr 16 10:46:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA16587 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 10:46:53 -0700 (PDT) Received: from lithium.maximum.net (daleg@x.maximum.net [205.161.109.86]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA16545 for ; Wed, 16 Apr 1997 10:46:46 -0700 (PDT) Received: from localhost (daleg@localhost) by lithium.maximum.net (8.8.5/8.8.4) with SMTP id MAA05634; Wed, 16 Apr 1997 12:40:54 -0400 Date: Wed, 16 Apr 1997 12:40:54 -0400 (EDT) From: Dale Ghent Reply-To: Dale Ghent To: Alex Rubenstein cc: freebsd-scsi@freebsd.org Subject: Re: Major 2940UW and 2.2.1 problems... In-Reply-To: Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 16 Apr 1997, Alex Rubenstein wrote: | We are seeing the same; we we let you know if we find anyting; please do | the same. I think I found the fix. I was rooting around on ftp.freebsd.org last night and came accross the aic drivers in the src directory for FreeBSD-STABLE. I noticed that the rev dates on the src I had on my machine was different that that on freebsd.org. According to what I saw, the last up date to the aic7xxx.c was 5 days ago. There was also a more recent version of aic7870.c. So I grabbed these two and replaced the ones I had, recompiled the kernel, and so far after 15 hours of uptime, no reboots. Here's what you'll need to do: Replace /sys/pci/aic7870.c with: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/pci/aic7870.c Replace /sys/i386/scsi/aic7xxx.x with: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/i386/scsi/aic7xxx.c Recompile Kernel/install/reboot. Thanks to Justin for the coding the fix :) -Dale G. From owner-freebsd-scsi Wed Apr 16 10:54:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA18787 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 10:54:34 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA18774 for ; Wed, 16 Apr 1997 10:54:31 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id NAA13814; Wed, 16 Apr 1997 13:41:46 -0400 (EDT) From: Peter Dufault Message-Id: <199704161741.NAA13814@hda.hda.com> Subject: Re: scsi(8) and (3) changes In-Reply-To: <199704161442.JAA00650@jake.lodgenet.com> from "Eric L. Hernes" at "Apr 16, 97 09:42:42 am" To: erich@lodgenet.com (Eric L. Hernes) Date: Wed, 16 Apr 1997 13:41:45 -0400 (EDT) Cc: dufault@hda.com, scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Yes, I for one would appreciate it. Have you thought about making > the Tcl stuff into a .so and loading it directly instead of > linking whole new executable? Or maybe swig-ifying libscsi, so it'd > work with Tcl and Perl? I really like the idea of using Tcl to glue > scsi stuff together. Tcl isn't linked in - the input/output look like tcl lists and is driven through popen. I don't know what "swig" is. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-scsi Wed Apr 16 11:38:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA00729 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 11:38:52 -0700 (PDT) Received: from othello (othello.nac.net [207.99.2.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA00684 for ; Wed, 16 Apr 1997 11:38:39 -0700 (PDT) Received: from [207.99.2.234] by othello (NTMail 3.02.13) with ESMTP id ca517896 for ; Wed, 16 Apr 1997 14:38:22 -0400 Message-Id: <3.0.32.19970416143431.00b74af0@mail.nac.net> X-Sender: alex@mail.nac.net X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 16 Apr 1997 14:39:00 -0300 To: Dale Ghent From: Alex Rubenstein Subject: Re: Major 2940UW and 2.2.1 problems... Cc: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks, I forwarded it to our FreeBSD kernel builder. Thanks again. At 12:40 PM 4/16/97 -0400, Dale Ghent wrote: >On Wed, 16 Apr 1997, Alex Rubenstein wrote: > >| We are seeing the same; we we let you know if we find anyting; please do >| the same. > >I think I found the fix. I was rooting around on ftp.freebsd.org last >night and came accross the aic drivers in the src directory for >FreeBSD-STABLE. I noticed that the rev dates on the src I had on my >machine was different that that on freebsd.org. According to what I saw, >the last up date to the aic7xxx.c was 5 days ago. There was also a more >recent version of aic7870.c. So I grabbed these two and replaced the ones >I had, recompiled the kernel, and so far after 15 hours of uptime, no >reboots. > >Here's what you'll need to do: > >Replace /sys/pci/aic7870.c with: >ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/pci/aic7870.c > >Replace /sys/i386/scsi/aic7xxx.x with: >ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/i386/scsi/aic7xxx.c > >Recompile Kernel/install/reboot. > >Thanks to Justin for the coding the fix :) > > -Dale G. > > From owner-freebsd-scsi Wed Apr 16 11:48:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03030 for freebsd-scsi-outgoing; Wed, 16 Apr 1997 11:48:03 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA02998 for ; Wed, 16 Apr 1997 11:47:58 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id NAA29547; Wed, 16 Apr 1997 13:47:45 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma029536; Wed Apr 16 13:47:26 1997 Received: from jake.lodgenet.com ([10.0.11.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id NAA14655; Wed, 16 Apr 1997 13:47:10 -0500 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.5/8.6.12) with ESMTP id NAA07317; Wed, 16 Apr 1997 13:47:33 -0500 (CDT) Message-Id: <199704161847.NAA07317@jake.lodgenet.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Peter Dufault cc: erich@lodgenet.com (Eric L. Hernes), scsi@freebsd.org Subject: Re: scsi(8) and (3) changes In-reply-to: Your message of "Wed, 16 Apr 1997 13:41:45 EDT." <199704161741.NAA13814@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Apr 1997 13:47:33 -0500 From: "Eric L. Hernes" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Dufault writes: > >Tcl isn't linked in - the input/output look like tcl lists and is >driven through popen. I don't know what "swig" is. Yea, but the README mentions possibly integrating it into a tclsh/wish app. swig will take c or c++ style declarations and generate glue-code to build tcl/perl/python/etc. libraries. for example, say I have a file scsi.i that contains: ------------------------ %init Scsi_Init %{ #include %} struct scsireq_t; scsireq_t *scsireq_reset(scsireq_t *); scsireq_t *scsireq_new(void); ------------------------- then swig/compile/link it as: (ttyp3@jake)$ swig scsi.i Making wrappers for Tcl (ttyp3@jake)$ gcc -fpic -c scsi_wrap.c (ttyp3@jake)$ ld -Bshareable scsi_wrap.o -o scsi.so -lscsi I get a shared object that can be loaded into a tclsh or wish and provide two new commands `scsireq_new' and `scsireq_reset' that are direct hooks to the scsi(3) functions. I can use them like: (ttyp3@jake)$ tclsh % load scsi.so % set t [scsireq_new] _8300_scsireq_t_p % scsireq_reset $t _8300_scsireq_t_p % at this point `scsireq_t' is opaque to tcl. If you declare the full structure in the .i file, swig create helper functions to access the structure's members, and an object to manipulate the structure in the spirit of Tk widgets (cget/configure). /usr/ports/devel/SWIG > >-- >Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation >HD Associates, Inc. Voice: 508 433 6936 eric. -- erich@rrnet.com http://rrnet.com/~erich erich@freebsd.org http://www.freebsd.org/~erich erich@lodgenet.com From owner-freebsd-scsi Thu Apr 17 09:13:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA17779 for freebsd-scsi-outgoing; Thu, 17 Apr 1997 09:13:18 -0700 (PDT) Received: from vipunen.hut.fi (vipunen.hut.fi [130.233.224.20]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA17756 for ; Thu, 17 Apr 1997 09:13:02 -0700 (PDT) Received: from pooh.tky.hut.fi (pooh.tky.hut.fi [130.233.23.135]) by vipunen.hut.fi (8.8.5/8.8.2) with ESMTP id TAA56852 for ; Thu, 17 Apr 1997 19:12:29 +0300 Received: by pooh.tky.hut.fi (TAA19568); Thu, 17 Apr 1997 19:12:29 +0300 (EEST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: scsi@freebsd.org From: Timo J Rinne Subject: Re: SCSI Problems Since 2.2-BETA_A of 13-Feb-1997 References: Reply-to: tri@iki.fi Organization: Helsinki University of Technology, Espoo, Finland X-Face: 7N&%4=;/9+e`m7vVp3kmZ^FZ~;TBHua/@dBeFi*{xAoyz+8feePXCUmOK[GaY*0[QU`{lo *D3.D?xc>nBKUHDdXo)*OiG-MGf-a2dCZ5{yYMZV9:+H1h:%g$']XOPwUx{<5fH@l?+U8B Cr!lG(V:g=`_gdg86&u$/ez/jG_H3uU8!TB&ZuEz-BKqfBL3HGS@oA#,GsugP3o3.ckI- X-Newsreader: Gnus v5.4.45/XEmacs 19.15 Date: 17 Apr 1997 19:11:07 +0300 Message-ID: Lines: 12 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Simon Shapiro wrote: > sd10(ahc1:13:0): timed out in dataout phase SCSISIGI = 0x0 > SEQADDR = {0x6,0xf,0xa....} > ahc1: Issued channel A Bus reset > spec_getpage I/O read error > vm_fault: pager input ... I have seen a few of those in my 970209 snap. It always barfs my machine after a while. I thought that it was a dying scsi-disk, but maybe it's a software prob... //Rinne From owner-freebsd-scsi Fri Apr 18 07:54:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA10502 for freebsd-scsi-outgoing; Fri, 18 Apr 1997 07:54:18 -0700 (PDT) Received: from outland.cyberwar.com (root@outland.cyberwar.com [206.88.128.42]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA10495 for ; Fri, 18 Apr 1997 07:54:13 -0700 (PDT) Received: from zippy (zippy.cyberwar.com [206.88.128.80]) by outland.cyberwar.com (8.8.5/8.8.5) with SMTP id KAA11547 for ; Fri, 18 Apr 1997 10:54:05 -0400 (EDT) Message-Id: <3.0.32.19970418105323.00970e40@pop.cyberwar.com> X-Sender: wjgrun@pop.cyberwar.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 18 Apr 1997 10:53:24 -0400 To: freebsd-scsi@freebsd.org From: Bill Grunfelder Subject: "Sending SDTR!!" message on boot. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can some one tell me what a "Sending SDTR!!" message on boot means? I have not seen this ?error? message before, but it's my first time using a Western Digital SCSI drive. Is this message a problem? Are there any known problems with Western Digital SCSI drives? I've attached a snippet from dmesg below. fxp0: Ethernet address 00:a0:c9:1f:4c:f7 ahc0 rev 0 int a irq 10 on pci0:11 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "QUANTUM XP34301 1071" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4106MB (8410200 512 byte sectors) ahc1 rev 0 int a irq 11 on pci0:12 ahc1: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc1 waiting for scsi devices to settle Sending SDTR!! ahc1: target 2 Tagged Queuing Device (ahc1:2:0): "WDIGTL ENTERPRISE 1.61" type 0 fixed SCSI 2 sd1(ahc1:2:0): Direct-Access 4157MB (8515173 512 byte sectors) Sending SDTR!! ahc1: target 5 Tagged Queuing Device (ahc1:5:0): "WDIGTL ENTERPRISE 1.61" type 0 fixed SCSI 2 sd2(ahc1:5:0): Direct-Access 4157MB (8515173 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard Thanks, Bill ....................................................................... Bill Grunfelder System Administrator wjgrun@cyberwar.com Cyber Warrior, Inc. http://www.cyberwar.com/~wjgrun/ (201) 703-1517 -The above does not necessarily coincide with the views of my employer- From owner-freebsd-scsi Fri Apr 18 08:35:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA12497 for freebsd-scsi-outgoing; Fri, 18 Apr 1997 08:35:30 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA12492 for ; Fri, 18 Apr 1997 08:35:27 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id JAA12608; Fri, 18 Apr 1997 09:35:20 -0600 (MDT) Message-Id: <199704181535.JAA12608@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Bill Grunfelder cc: freebsd-scsi@FreeBSD.ORG Subject: Re: "Sending SDTR!!" message on boot. In-reply-to: Your message of "Fri, 18 Apr 1997 10:53:24 EDT." <3.0.32.19970418105323.00970e40@pop.cyberwar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Apr 1997 09:33:47 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can some one tell me what a "Sending SDTR!!" message on boot means? I have >not seen this ?error? message before, but it's my first time using a Western >Digital SCSI drive. Is this message a problem? Are there any known problems >with Western Digital SCSI drives? I've attached a snippet from dmesg below. It's a diagnostic in the driver that says that a drive initiated sync negotiation and the driver replied to it. Most drives wait for the initiator (the adaptec card) to initiate wide/sync negotiation, but some drives will immediately attempt to negotiate sync after they receive a wide negotiation message. I'll remove the printf. The message only means that the driver is doing what it is supposed to. >Thanks, > >Bill >....................................................................... >Bill Grunfelder System Administrator >wjgrun@cyberwar.com Cyber Warrior, Inc. >http://www.cyberwar.com/~wjgrun/ (201) 703-1517 > >-The above does not necessarily coincide with the views of my employer- -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Apr 19 23:06:10 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA06857 for freebsd-scsi-outgoing; Sat, 19 Apr 1997 23:06:10 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA06832; Sat, 19 Apr 1997 23:05:57 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id CAA21154; Sun, 20 Apr 1997 02:04:50 -0400 (EDT) Date: Sun, 20 Apr 1997 02:04:50 -0400 (EDT) From: Brian Tao Reply-To: Brian Tao To: freebsd-scsi@freebsd.org cc: freebsd-current@freebsd.org Subject: "Data overrun" with 3.0-SNAP, 2940UW controllers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm stress testing a new NFS server with 2.0-970209-SNAP to see how it deals with having a couple of Adaptec 2940UW controllers. About half an hour into the tests, the machine appears to have crashed (no response to pings), and I don't have physical access to the machine right now. :( The system is a P200 with two 2940UW's and a Buslogic BT-946C with no devices attached to it (it will be dedicated to a DLT drive in the future). The first Adaptec has four 4GB Seagate ST34371W's and the second has three. The first is a boot drive and the remaining six are striped together (alternating controllers) into ccd0. The tests consist of four scripts: replicate the entire FreeBSD source tree into a new directory and then delete it, touch 10000 randomly named files in a directory and delete them, dd /dev/zero into files with random block sizes, and run bonnie. Five copies of each script are run concurrently. Only three of the drives are shown here, but the others have identical stats: % iostat -w5 sd1 sd2 sd3 tty sd1 sd2 sd3 cpu tin tout sps tps msps sps tps msps sps tps msps us ni sy in id 0 19 192 7 0.0 193 8 0.0 192 7 0.0 1 0 3 0 96 0 25 4359 159 0.0 4332 157 0.0 4470 159 0.0 1 0 65 6 28 0 25 4525 155 0.0 4601 159 0.0 4414 151 0.0 1 0 66 5 28 0 25 4450 159 0.0 4378 157 0.0 4492 158 0.0 1 0 63 6 29 0 25 4825 183 0.0 4681 181 0.0 4690 177 0.0 1 0 70 7 23 0 25 4521 173 0.0 4529 174 0.0 4622 174 0.0 0 0 73 6 20 0 43 4664 180 0.0 4890 191 0.0 4547 175 0.0 0 0 66 7 27 0 25 4246 152 0.0 4207 154 0.0 4484 161 0.0 1 0 67 5 27 0 25 4204 157 0.0 4279 159 0.0 3955 147 0.0 2 0 59 6 34 0 25 4596 174 0.0 4584 179 0.0 4611 176 0.0 0 0 73 6 21 0 25 4454 158 0.0 4490 160 0.0 4497 160 0.0 0 0 66 6 28 These messages started showing up in the syslog during the tests. I tried running with /dev/ccd0c sync and async: the messages appeared for both. No other syslog messages were logged other than ones produced purposely by the scripts themselves to track their progress. Is there anything I can do to correct this problem (which I believe is related to the crash)? I'm going to try a pre-2.2 release as most people have suggested to see if that fixes the problems. dmesg output is included below as well. % fgrep 'data overrun' /var/log/messages Apr 19 23:22:51 nfs /kernel: sd5: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:22:53 nfs /kernel: sd4: data overrun of 4068 bytes detected. Forcing a retry. Apr 19 23:24:49 nfs /kernel: sd6: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:24:53 nfs /kernel: sd2: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:24:58 nfs /kernel: sd6: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:25:18 nfs /kernel: sd5: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:26:02 nfs /kernel: sd1: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:26:57 nfs /kernel: sd1: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:27:22 nfs /kernel: sd3: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:27:50 nfs /kernel: sd5: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:28:12 nfs /kernel: sd6: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:29:02 nfs /kernel: sd2: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:30:00 nfs /kernel: sd3: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:30:18 nfs /kernel: sd4: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:30:51 nfs /kernel: sd5: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:31:19 nfs /kernel: sd4: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:31:26 nfs /kernel: sd6: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:32:01 nfs /kernel: sd4: data overrun of 484 bytes detected. Forcing a retry. Apr 19 23:33:30 nfs /kernel: sd2: data overrun of 484 bytes detected. Forcing a retry. [...] Apr 19 23:35:28 nfs /kernel: sd2: data overrun of 497 bytes detected. Forcing a retry. Apr 19 23:35:29 nfs /kernel: sd2: data overrun of 484 bytes detected. Forcing a retry. FreeBSD 3.0-970209-SNAP #0: Sat Apr 19 16:08:33 EDT 1997 root@nfs:/usr/depot/src/sys/compile/NFS Calibrating clock(s) relative to mc146818A clock ... i586 clock: 199426620 Hz, i8254 clock: 1193152 Hz CPU: Pentium (199.43-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 129490944 (126456K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 5 on pci0:13:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4148MB (8496884 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 4148MB (8496884 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 4148MB (8496884 512 byte sectors) sd3 at scbus0 target 3 lun 0 sd3: type 0 fixed SCSI 2 sd3: Direct-Access 4148MB (8496884 512 byte sectors) ahc1 rev 0 int a irq 9 on pci0:14:0 ahc1: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc1: waiting for scsi devices to settle scbus1 at ahc1 bus 0 sd4 at scbus1 target 1 lun 0 sd4: type 0 fixed SCSI 2 sd4: Direct-Access 4148MB (8496884 512 byte sectors) sd5 at scbus1 target 2 lun 0 sd5: type 0 fixed SCSI 2 sd5: Direct-Access 4148MB (8496884 512 byte sectors) sd6 at scbus1 target 3 lun 0 sd6: type 0 fixed SCSI 2 sd6: Direct-Access 4148MB (8496960 512 byte sectors) bt0 rev 0 int a irq 11 on pci0:15:0 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 4.28D, async only, parity, 32 mbxs, 32 ccbs bt0: Using Strict Round robin scheme bt0: waiting for scsi devices to settle scbus2 at bt0 bus 0 de0 rev 18 int a irq 10 on pci0:16:0 de0: SMC 9332 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:99:00:e6 de0: enabling 100baseTX port Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not found at 0x2f8 lpt0 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in bt: unit number (1) too high bt1 not found at 0x330 npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"