Date: Mon, 30 Jun 2008 11:36:38 -0400 From: "Brian A. Seklecki" <bseklecki@collaborativefusion.com> To: Simon <simon@optinet.com> Cc: Sean McAfee <smcafee@collaborativefusion.com>, Jason Thomson <jason.thomson@mintel.com>, scottl@freebsd.org, Benjie Chen <benjie@addgene.org>, "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes Message-ID: <1214840198.18670.43.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> In-Reply-To: <1195160114.4042.154.camel@new-host> References: <20071114122210.42E8613C4BB@mx1.freebsd.org> <1195160114.4042.154.camel@new-host>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2007-11-15 at 15:55 -0500, Brian A Seklecki (Mobile) wrote: > Normally I'd be praising Dell, but I think a little vendor bashing is > due here. All: Just to follow up, we've been running these 1st-generation 2950s in our lab with RHEl5.2 x86_64 for ~3 weeks w/o any disk or I/O problems. It must have been some random bug with the FreeBSD mfi(4) that only affected that revision of the PERC5, or, since the motherboard/CPU family/chipset is entirely different in R2 and R3, something with FreeBSD and how it was handling the controller (ACPI?) We never had any stability problems with R2 and R3 on RELENG_6_3 on the 2950 or 1950. >From now on we'll wait for R2 before we go anywhere near new Dell gear. What do you think the chances of them dumping LSI for Acera and Broadcom for Intel? :) ~BAS > Its a software bug (driver). It can probably be easily fixed. I > think there's a PR on it somewhere (will check). -- Brian A. Seklecki <bseklecki@collaborativefusion.com> Collaborative Fusion, Inc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1214840198.18670.43.camel>