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