Date: Fri, 27 Jan 2006 01:00:28 +0200 From: Niki Denev <nike_d@cytexbg.com> To: Joshua Coombs <jcoombs@gwi.net> Cc: freebsd-stable@freebsd.org Subject: Re: Adaptec SCSI going nuts Message-ID: <43D9548C.3040105@cytexbg.com> In-Reply-To: <drbehj$dl$1@sea.gmane.org> References: <drbehj$dl$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joshua Coombs wrote: > Just got a dual Opteron system to play with amd64 builds of FreeBSD. > Poking around to see how it behaived, I initially tossed FreeBSD 4.11 on > it, and was surprised to see a dump of the scsi controller state at the > end of the dmesg. Tried 6.0-Rel, both x86 and amd64, same behavior. > Bumped up to 6-stable from yesterday, same behavior. After the dump, > the system appears solid, no other errors, so I'm guessing it's just a > problem with how the card is initialized, FreeBSD corrects it and moves on. > > Should I be more concerned, or consider it a quirk of the machine? > > Joshua Coombs > [...] I was seeing similar stuff on one machine. I solved the problem with forcing the scsi controller to U160, and splitting the disks on the both channels to distribute the load. (mine was dual-channel onboard U320 and four Seagate 36G 10Krpm hdds) I've heard that this has something to do with firmware incompatibility on some Seagate SCSI drives and Adaptec U320 controllers, but i don't know if it's true. I haven't found stability issues before and after this change, but i left it at U160 to get rid of these messages. Niki -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD2VSMHNAJ/fLbfrkRAlfWAJ9Q+O23RU16oNT4PSKyRXLYDpggOQCgkumW oZxp6JHj+M5tfK0S700bj0k= =kXPQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43D9548C.3040105>