From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 19:09:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65A6316A4CE; Tue, 17 Feb 2004 19:09:42 -0800 (PST) Received: from lorax.ldc.upenn.edu (lorax.ldc.upenn.edu [158.130.16.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E2EF43D1F; Tue, 17 Feb 2004 19:09:42 -0800 (PST) (envelope-from fuzz@ldc.upenn.edu) Received: by lorax.ldc.upenn.edu (Postfix, from userid 32822) id CE97D22852; Tue, 17 Feb 2004 22:09:41 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by lorax.ldc.upenn.edu (Postfix) with ESMTP id C351922831; Tue, 17 Feb 2004 22:09:41 -0500 (EST) Date: Tue, 17 Feb 2004 22:09:41 -0500 (EST) From: "Jason M. Leonard" To: Scott Long In-Reply-To: <4032CC86.7000800@freebsd.org> Message-ID: <20040217214845.B61621@lorax.ldc.upenn.edu> References: <20040217102453.V59439@lorax.ldc.upenn.edu> <4032A691.3020006@freebsd.org><4032CC86.7000800@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: Raphael.Becker@gmx.de Subject: Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 18 Feb 2004 03:09:42 -0000 On Tue, 17 Feb 2004, Scott Long wrote: > Lachlan O'Dea wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 18 Feb 2004, at 10:41, Scott Long wrote: > > > >> Jason M. Leonard wrote: > >> > >>> Without seeing the actual SCSI errors it is hard to say, but I was > >>> experiencing a very similar issue with my PE2650. Disabling write > >>> caching > >>> on the RAID 1 container cleared it up. I do not know if that is the > >>> best > >>> way to go about it, but this server had to be in production pronto, so I > >>> was happy. > >>> :Fuzz > >> > >> > >> If there is any way that you could send me the errors that you were > >> getting, I would appreciate it. I was seeing the same "aac0: command 0xXXXXXX timeout" error as below. > > > > Hi Scott, > > > > This may be completely unrelated, but I just went from 5.2-RELEASE to > > 5.2.1-RC2. After a while started seeing lots of these on the console: > > > > aac0: command 0xXXXXXX timeout after 8597 seconds > > As was mentioned, changing /sys/dev/aac/aacvar.h:AAC_MAX_FIBS from 512 > to 504 will work around this problem. I'll commit this to RELENG_5_2 in > a minute. Thanks! :Fuzz