Date: Thu, 06 Mar 1997 19:37:14 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: "Harry Reed" <doon@eeyore.lv-hrc.nevada.edu> Cc: freebsd-questions@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: 2.1.5->2.1.7 causes SCSI errors? Message-ID: <4919.857705834@time.cdrom.com> In-Reply-To: Your message of "Thu, 06 Mar 1997 07:58:16 PST." <199703061557.HAA00182@eeyore.lv-hrc.nevada.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hm, Unfortunately our disk is a conner! Ah, so much for that theory. Damn. > We had the exact same harward running Linux 1.2.13 for many months. > We had a severe security breah and decided to move up to a more secure, > robust OS - FreeBSD :} Went to install 2.1.6 and out 2940 gave out the > strange messages all without even cycling power on the box! Had to put > in an old spare 1542B. Do we have a case where an old, crusty version of > Linux > can do something that FBSD 2.1.6 can't???? 10 * :} - that's a joke son, > I say, that's a joke!!!! Well, I appreciate the humor, but trust me when I say that non-functioning FreeBSD systems are no joke to us! :-) Did any previous release of FreeBSD work on this hardware? Some changes were made to the Adaptec 2940 driver to in order to deal with performance issues with the newer drives which support tagged queueing and other nice features we weren't taking full advantage of. Now that we do, however, it appears that some previously working systems are now falling over. Cal you tell us a little more about this system and its attached drives, keeping Justin Gibbs on the Cc line? Thanks! Maybe we can figure out what broke and release a patch to 2.1.7. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4919.857705834>