Date: Tue, 20 Feb 2007 07:52:41 -0700 From: Scott Long <scottl@samsco.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: FreeBSD current mailing list <current@freebsd.org> Subject: Re: [mfi] command timeouts Message-ID: <45DB0B39.2070107@samsco.org> In-Reply-To: <20070220061538.A47107@maildrop.int.zabbadoz.net> References: <20070219130102.N47107@maildrop.int.zabbadoz.net> <20070219135158.E47107@maildrop.int.zabbadoz.net> <45DA333F.7070800@pooker.samsco.org> <20070220061538.A47107@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote: > On Mon, 19 Feb 2007, Scott Long wrote: > > Hi, > >> megacli is known to be fragile. Don't Do That (tm). > > alternative solution? > Run the monitoring commands, don't run the commands that have given you demonstrated problems. Another path would be to contact LSI and negotiate an NDA for their docs so that you can write your own tools. Several FreeBSD-using companies have done this already, contact me privately if you want details. >> 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. > But it eventually recovers? If you're interested in tracking this down, break into serial DDB when it happens and dump out the command structure from the address given. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45DB0B39.2070107>