From owner-freebsd-current@FreeBSD.ORG Thu Jan 6 23:12:39 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 6D04B16A4CE; Thu, 6 Jan 2005 23:12:39 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D568B43D48; Thu, 6 Jan 2005 23:12:38 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j06NFffk024030; Thu, 6 Jan 2005 16:15:42 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41DDC5E4.6020607@freebsd.org> Date: Thu, 06 Jan 2005 16:12:36 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Simon L. Nielsen" References: <20041223123621.GB17515@eddie.nitro.dk> <41CADACC.9050607@freebsd.org> <20050106131327.GE801@zaphod.nitro.dk> <20050106.134852.41638084.imp@harmony.village.org> <20050106230856.GQ801@zaphod.nitro.dk> In-Reply-To: <20050106230856.GQ801@zaphod.nitro.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Warner Losh cc: freebsd-current@freebsd.org cc: imp@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 23:12:39 -0000 Simon L. Nielsen wrote: > On 2005.01.06 13:48:52 -0700, Warner Losh wrote: > >>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? > > > Yes, it also happens with a -CURRENT from today. > > >>Can you send me a complete pciconf -lv for this system? > > > It should be attached. > > In the email I sent a few minutes ago i described the problem. Now all we have to do is string Warner up by his toes and lash him with soggy spaghetti noodles until he fixes it =-) Scott