Date: Sat, 17 Mar 2001 14:34:46 -0800 (PST) From: Tom Samplonius <tom@sdf.com> To: Chris Dillon <cdillon@wolves.k12.mo.us> Cc: James FitzGibbon <jfitz@FreeBSD.ORG>, scsi@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Mylex eXtremeRAID 2000 timeout/hang Message-ID: <Pine.BSF.4.05.10103171431520.221-100000@misery.sdf.com> In-Reply-To: <Pine.BSF.4.32.0103161713530.26609-100000@mail.wolves.k12.mo.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Mar 2001, Chris Dillon wrote: ... > I also had a problem after a recent upgrade to 4.3-BETA where if I > left my extra drive in the chassis, I would get the following error > just before the 0:6:0 errors: The mly driver has been updated a short while ago. I've recently discovered some issues as well. I can hang the disks under heavy IO with a Mylex 352 card. ... > P.S.: I'm getting stuff in my dmesg buffer from _previous_ boots... > I've never seen a system do that. That's how I could cut/paste that > panic. :-) Is that a bug, or a feature? Its a nice feature (which my > other 4.2-STABLE boxes don't seem to have). Some of the information Been around for a long time. As long as your hardware preserved the memory state during a warm boot, the previous dmesg can be found by the kernel. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10103171431520.221-100000>