From owner-freebsd-current@FreeBSD.ORG Thu Jan 6 20:56:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0AA716A4CE; Thu, 6 Jan 2005 20:56:41 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D1AC43D58; Thu, 6 Jan 2005 20:56:41 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j06KmrYp004977; Thu, 6 Jan 2005 13:48:53 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Thu, 06 Jan 2005 13:48:52 -0700 (MST) Message-Id: <20050106.134852.41638084.imp@harmony.village.org> To: simon@nitro.dk From: Warner Losh In-Reply-To: <20050106131327.GE801@zaphod.nitro.dk> References: <20041223123621.GB17515@eddie.nitro.dk> <41CADACC.9050607@freebsd.org> <20050106131327.GE801@zaphod.nitro.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 07 Jan 2005 13:10:38 +0000 cc: imp@freebsd.org cc: freebsd-current@freebsd.org cc: scottl@freebsd.org Subject: Re: pci powerstate related: aac(4) broken on Perc 3/Di on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 20:56:41 -0000 From: "Simon L. Nielsen" 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: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on > > >pci4 > > >aac0: [FAST] > > >aacd0: 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? Can you send me a complete pciconf -lv for this system? Warner