Date: Thu, 6 Jan 2005 14:13:28 +0100 From: "Simon L. Nielsen" <simon@nitro.dk> To: Scott Long <scottl@freebsd.org> Cc: "M. Warner Losh" <imp@FreeBSD.org> Subject: Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT Message-ID: <20050106131327.GE801@zaphod.nitro.dk> In-Reply-To: <41CADACC.9050607@freebsd.org> References: <20041223123621.GB17515@eddie.nitro.dk> <41CADACC.9050607@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--xA/XKXTdy9G3iaIz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.12.23 07:48:44 -0700, Scott Long wrote: >=20 > 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= =20 > >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 >=20 > 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=3D1 by default. If I add hw.pci.do_powerstate=3D"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. --=20 Simon L. Nielsen --xA/XKXTdy9G3iaIz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB3Tl3h9pcDSc1mlERAjVpAJ4wBQlx3n6rT7mljofz/yOJOcCPdwCgxIM6 NLvIEKMojfMvAwmt+t1wJqk= =96Hf -----END PGP SIGNATURE----- --xA/XKXTdy9G3iaIz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050106131327.GE801>