Date: Sat, 29 Mar 1997 20:31:23 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: "Roy M. Hooper" <rhooper@toybox.ottawa.on.ca> Cc: freebsd-scsi@freebsd.org Subject: Re: AHA2940/3940 troubles Message-ID: <Pine.BSF.3.95.970329201525.20974B-100000@opus.cts.cwu.edu> In-Reply-To: <199703291527.KAA02613@toybox.ottawa.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Roy! I sense that you are getting a little bit frustrated :) If it is any small consolation, I have over 40 gigabytes of storage across 5 machines running the RELENG_ branches of 2_1_0 and 2_2, including a reasonably busy news server as well as cvsup.freebsd.org; all on aha3940W and 2940 controllers and all with no problem. My point is not to make you more frustrated, but to let you know that this stuff normally works really really really well. Now then, you don't mention what kind of hardware you have, but if your disks are not major-label (eg. Seagate, Quantum) you might want to disable tagged command queueing. MEMIO has never worked for me on P5 motherboards from asus, either - producing random lockups and crashes. If you do have major-label drives, is your firmware up-to-date? What kinds of cables are you using? I pay the extra money for adaptec cables with active terminators, and remove all drive termination. What about BIOS settings for the PCI bus? If you have an old MB conceivably there could be problems here. Are you seeing any other problems, like processes randomly exiting on signal 11 or 12? Perhaps your memory timing in BIOS is too aggressive? What about your setup values in the Adaptec setup? You might search this mailing list via the www interface (www.freebsd.org) and look for postings from Justin Gibbs. Hope this helps, -Chris On Sat, 29 Mar 1997, Roy M. Hooper wrote: > > No matter what i've tried: > - switching the AHA2940s with a AHA3940 > - adding all the AHC_ opptions > - ugprading to 2.2.1 > - etc. > > I just can't make the FreeBSD box stay up. It almost always goes down on > some SCSI driver error and comes back up, but occasionally just locks up > and stays locked. > > This unstability is getting to the point where we will need to scrap FreeBSD > and try other operating systems, as much as we do not want to. > > Any help not covered above would help alot. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970329201525.20974B-100000>