From owner-freebsd-scsi Sat Mar 17 14:39:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 3BA0837B71A; Sat, 17 Mar 2001 14:39:27 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14ePHq-0001VY-00; Sat, 17 Mar 2001 14:35:03 -0800 Date: Sat, 17 Mar 2001 14:34:46 -0800 (PST) From: Tom Samplonius To: Chris Dillon Cc: James FitzGibbon , scsi@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Mylex eXtremeRAID 2000 timeout/hang In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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