Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI (fwd)

> 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

cpuid = 1;

boot() called on cpu#1

syncing disks, buffers remaining... kernel trap 12 with interrupts
disabled

fatal trap 12: page fault while in kernel mode
cpuid=0; apic is = 00
fault virtual address		= 0x24
fault code			= supervisor read, page not present
instruction pointer		= 0x8:0xc04de488
stack pointer			= 0x10:0xe148dc68
frame pointer			= 0x10:0xe148dc78
code segment			= base 0x0, limit 0xfffff, type 0x1b
				= DPL 0, pres 1, def 32, gran 1
processor eflags		= resume, IOPL = 0
current process			= 65 (swi5:+)
trap number			= 12


:Fuzz