Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT

On 2005.01.06 13:48:52 -0700, Warner Losh wrote:
> From: "Simon L. Nielsen" <simon_at_nitro.dk>
> Subject: Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT
> Date: Thu, 6 Jan 2005 14:13:28 +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?
> > 
> > After several rounds of backstepping I found that the problem is
> > caused by sys/dev/pci/pci.c v. 1.268 which sets hw.pci.do_powerstate=1
> > by default.  If I add hw.pci.do_powerstate="0" to loader.conf the
> > system boots fine.  I have no idea why this only manifests itself as
> > an aac(4) error.
> > 
> > This system has a Dell remote management card and I rememeber that
> > Lukas Ertl, some time ago, reported some problem with the power state
> > change and a (HP?) remote management card, so perhaps this is a
> > similar issue.
> 
> Interesting.  This is even after my changes to current to make it not
> power down system devices?

Yes, it also happens with a -CURRENT from today.

> Can you send me a complete pciconf -lv for this system?

It should be attached.

-- 
Simon L. Nielsen