Re: aac(4) broken on Perc 4/Di on -CURRENT

From: Simon L. Nielsen <simon_at_FreeBSD.org>
Date: Thu, 23 Dec 2004 23:11:49 +0100
On 2004.12.23 07:48:44 -0700, Scott Long wrote:
> 
> Simon L. Nielsen wrote:
> >Hello
> >
> >Recent -CURRENT seems to have broken aac(4) on a Dell Perc 4/Di.  The
> >system is a Dell PowerEdge 2650 with 4 36GB IBM disks in a RAID0+1
> >configuration.
> >
> >It runs fine on a 5-STABLE kernel, but when booting -CURRENT it prints
> >a lot of errors from the RAID controller and then fails to mount the
> >root file-system.
> >
> >I have attached dmesg from 6-CURRENT and 5-STABLE, but the main
> >interesting parts from -CURRENT are:
> >
> >aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on 
> >pci4
> >aac0: [FAST]
> >aacd0: <RAID 0/1> on aac0
> >aacd0: 69425MB (142182912 sectors)
> >SMP: AP CPU #3 Launched!
> >SMP: AP CPU #1 Launched!
> >SMP: AP CPU #2 Launched!
> >aac0: **Monitor**         NMI ISR: NMI_SECONDARY_ATU_ERROR
> >aac0: **Monitor**         NMI ISR: NMI_SECONDARY_ATU_ERROR
> >aac0: COMMAND 0xc2409438 TIMEOUT AFTER 41 SECONDS
> 
> There are very few differences between the driver in 6-CURRENT and
> 5-STABLE, and none of the differences look like ones that could
> cause problems.  Would you get able to step the source backwards until
> you find the point where it starts working again?

Sure, it might be some days before I can really try it, since I will
not be near the server, so if I rearlly crash it I won't be able to
get it back up :-).

BTW. it is a Perc 3/Di, not Perc 4/Di, as I wrote by mistake.

-- 
Simon L. Nielsen

Received on Thu Dec 23 2004 - 21:11:50 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:25 UTC