Date: Tue, 17 Feb 2004 22:09:41 -0500 (EST) From: "Jason M. Leonard" <fuzz@ldc.upenn.edu> To: Scott Long <scottl@freebsd.org> Cc: Raphael.Becker@gmx.de Subject: Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI Message-ID: <20040217214845.B61621@lorax.ldc.upenn.edu> In-Reply-To: <4032CC86.7000800@freebsd.org> References: <20040217102453.V59439@lorax.ldc.upenn.edu> <4032A691.3020006@freebsd.org><4032CC86.7000800@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040217214845.B61621>