From owner-freebsd-current@FreeBSD.ORG Tue Feb 20 06:20:13 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 EC0D6173309 for ; Tue, 20 Feb 2007 06:20:12 +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 A82B713C428 for ; Tue, 20 Feb 2007 06:20:12 +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 08ECB1FFD41; Tue, 20 Feb 2007 07:20:11 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id A48941FFC58; Tue, 20 Feb 2007 07:20:05 +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 5A6E6444889; Tue, 20 Feb 2007 06:19:18 +0000 (UTC) Date: Tue, 20 Feb 2007 06:19:17 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Scott Long In-Reply-To: <45DA333F.7070800@pooker.samsco.org> Message-ID: <20070220061538.A47107@maildrop.int.zabbadoz.net> References: <20070219130102.N47107@maildrop.int.zabbadoz.net> <20070219135158.E47107@maildrop.int.zabbadoz.net> <45DA333F.7070800@pooker.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 06:20:13 -0000 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