From owner-freebsd-current@FreeBSD.ORG Tue Feb 20 19:00:20 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 05F8C16BDD8 for ; Tue, 20 Feb 2007 19:00:20 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id BA45113C4A6 for ; Tue, 20 Feb 2007 19:00:19 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id D43E81FFE3E; Tue, 20 Feb 2007 20:00:17 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 8C2CB1FFE29; Tue, 20 Feb 2007 20:00:12 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 716CC444CC1; Tue, 20 Feb 2007 19:00:07 +0000 (UTC) Date: Tue, 20 Feb 2007 19:00:07 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Scott Long In-Reply-To: <45DB0B39.2070107@samsco.org> Message-ID: <20070220184639.F6506@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> <45DB0B39.2070107@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: FreeBSD current mailing list Subject: Re: [mfi] command timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Feb 2007 19:00:20 -0000 On Tue, 20 Feb 2007, Scott Long wrote: Hi, > Bjoern A. Zeeb wrote: >> On Mon, 19 Feb 2007, Scott Long wrote: >> >>> 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. Yes, from what I tried, I wrote down what works and what doesn't. I'll send a summary hopefully next week when I am back at work. > 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. It would be really good if LSI (and Dell) both would understand that there are LOTS of FreeBSD "users" using their hardware and start to support FreeBSD. I wouldn't care if there were binary releases only if someone was allowed to write, build and distribute them (even as not officially supported by those companies but "sponsored by" or something like that). Something built from source of course would be better but I'd be fine with having something that just works. I guess it would cost them less than close to nothing to make that happen and it would be a really great thing. >>> 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? yes after another round or so. > 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. I'll give it a try and let you know. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT