kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI
Scott Long
scottl at freebsd.org
Sun Feb 22 12:35:07 PST 2004
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 at 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
More information about the freebsd-current
mailing list