Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Feb 2004 13:32:16 -0700
From:      Scott Long <scottl@freebsd.org>
To:        "Jason M. Leonard" <fuzz@lorax.ldc.upenn.edu>
Cc:        freebsd-current@freebsd.org
Subject:   Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI
Message-ID:  <403911D0.2090709@freebsd.org>
In-Reply-To: <20040222151412.M686@lorax.ldc.upenn.edu>
References:  <20040217102453.V59439@lorax.ldc.upenn.edu> <4032A691.3020006@freebsd.org> <D4A757A6-61A5-11D8-9F04-000A95DBB47C@ca.com> <4032CC86.7000800@freebsd.org> <20040217214845.B61621@lorax.ldc.upenn.edu> <20040222151412.M686@lorax.ldc.upenn.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Jason M. Leonard wrote:
> On Tue, 17 Feb 2004, Jason M. Leonard wrote:
> 
> 
>>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.
> 
> 
> cvsup'd last night...
> 
> lorax.ldc.upenn.edu 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Sun Feb 22
> 01:58:58 EST 2004     fuzz@lorax.ldc.upenn.edu:/usr/obj/usr/src/sys/LORAX
> i386
> 
> Today while doing a portupgrade the machine crashed.  This is what was on
> the console when I got there (copied by hand):
> 
> command 0xc5e280f8 not in queue, flags = 0x5, bit = 0x80
> 
> panic: command not in queue at line 534 in file
> /usr/src/sys/dev/aac/aacvar.h

Thanks for the feedback.  Yeah, I'm aware of this but not having much
luck in fixing it yet (severe lack of time at the moment).  Bumping
AAC_MAX_FIBS back down to 504 again will avoid the problem.

Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?403911D0.2090709>