From owner-freebsd-current@FreeBSD.ORG  Tue Feb 20 15:17:39 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5C07D16A9C9
	for <current@freebsd.org>; Tue, 20 Feb 2007 14:53:08 +0000 (UTC)
	(envelope-from scottl@samsco.org)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.freebsd.org (Postfix) with ESMTP id 18E8B13C4F7
	for <current@freebsd.org>; Tue, 20 Feb 2007 14:53:08 +0000 (UTC)
	(envelope-from scottl@samsco.org)
Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id l1KEr06s070501;
	Tue, 20 Feb 2007 07:53:06 -0700 (MST)
	(envelope-from scottl@samsco.org)
Message-ID: <45DB0B39.2070107@samsco.org>
Date: Tue, 20 Feb 2007 07:52:41 -0700
From: Scott Long <scottl@samsco.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US;
	rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1
MIME-Version: 1.0
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.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>
In-Reply-To: <20070220061538.A47107@maildrop.int.zabbadoz.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]);
	Tue, 20 Feb 2007 07:53:06 -0700 (MST)
X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed 
	version=3.1.1
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org
Cc: FreeBSD current mailing list <current@freebsd.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Feb 2007 15:17:39 -0000

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