From owner-freebsd-scsi Sun Sep 17 10:39:46 2000 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 95C3E37B423 for ; Sun, 17 Sep 2000 10:39:43 -0700 (PDT) Received: (from gibbs@localhost) by caspian.plutotech.com (8.9.3/8.9.1) id BAA14539; Sat, 16 Sep 2000 01:00:15 -0600 (MDT) (envelope-from gibbs) Date: Sat, 16 Sep 2000 01:00:15 -0600 (MDT) Message-Id: <200009160700.BAA14539@caspian.plutotech.com> From: "Justin T. Gibbs" To: David Bushong Cc: scsi@FreeBSD.org Subject: Re: Adaptec 21960 X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <20000915004534.A486@bushong.net> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000915004534.A486@bushong.net> you wrote: > It doesn't seem to happen with all 29160's, but it does seem to happen with > all SuperMicro 370DL3 motherboards. I have IBM 36GB 10k drives, so it's not > that they're Seagates... > > --David Bushong Be aware that even IBM has had firmware issues with their 10K U160 product line. One particular bug made a seek miss a catastrophic event. Oh, and whatever sector you were shooting for would be corrupted too. Unfortunately I don't know exactly which models and firmware revisions were affected. Anyway, I did find reference to one situation that could potentially cause corruption of the controller's per-transaction data area when running the 7892/99 on a 66MHz pci bus. The latest version of the driver (referenced in another piece of email) avoids that issue and may fix this problem. If it doesn't, I'll order up a SM 370DL3 (or find one in our test lab) and see if I can determine what is going wrong on that board. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message