Date: Tue, 20 Feb 2007 06:19:17 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Scott Long <scottl@pooker.samsco.org> Cc: FreeBSD current mailing list <current@freebsd.org> Subject: Re: [mfi] command timeouts Message-ID: <20070220061538.A47107@maildrop.int.zabbadoz.net> In-Reply-To: <45DA333F.7070800@pooker.samsco.org> References: <20070219130102.N47107@maildrop.int.zabbadoz.net> <20070219135158.E47107@maildrop.int.zabbadoz.net> <45DA333F.7070800@pooker.samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Feb 2007, Scott Long wrote: Hi, > megacli is known to be fragile. Don't Do That (tm). alternative solution? > As for the panic, > It's probably a side effect of megacli putting the card and the driver into a > chaotic state. I have also seen timeout messages after boot (while fsck was running) even if megacli was not called during that uptime. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070220061538.A47107>