From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 10 18:05:34 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61EFB16A400 for ; Mon, 10 Apr 2006 18:05:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF9743D7B for ; Mon, 10 Apr 2006 18:05:26 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k3AI5OqY009119; Mon, 10 Apr 2006 14:05:25 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Mon, 10 Apr 2006 14:04:36 -0400 User-Agent: KMail/1.9.1 References: <20060406113433.O6088@netserv1.chg.ru> <200604071046.50669.jhb@freebsd.org> <44369CEF.1040702@root.org> In-Reply-To: <44369CEF.1040702@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604101404.37699.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1389/Mon Apr 10 08:58:55 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org Subject: Re: se7520af2 intel motherboard acpi problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 18:05:34 -0000 On Friday 07 April 2006 13:10, Nate Lawson wrote: > John Baldwin wrote: > > On Friday 07 April 2006 05:02, Anton Menshutin wrote: > >> On Thu, 6 Apr 2006, John Baldwin wrote: > >> > >>> Can you give more detail about how the pci-e busses do not work? > >>> > >> In dmesg output you can see kernel says nothing about areca raid > >> controller, which is on pci-e bus. And > >> pcib5: at device 0.0 on pci6 > >> pcib5: secondary bus 8 > >> pcib5: subordinate bus 8 > >> pcib5: I/O decode 0xf000-0xfff > >> pcib5: memory decode 0xfe900000-0xfe9fffff > >> pcib5: prefetched decode 0xfbc00000-0xfbffffff > >> device_attach: pcib5 attach returned 6 > >> what i think means there is a problem during init of pci-e bus. > > > > Ah, ok. It would be most helpful if you could add a bunch of printf's > > to the attach routine in sys/dev/acpica/acpi_pcib_pci.c to see where > > the error comes from. > > > > Oh, I think I've seen this before. This is due to incompetent BIOS > > writers. Edit sys/dev/acpica/acpi_pcib.c and in the acpi_pcib_attach() > > function comment out the acpi_DeviceIsPresent() check. The BIOS is > > claiming that the specific PCI bus doesn't exist. > > If that is the case, we should change acpi_pcib to have a separate check > for just the "functional" bit or whatever the AML does report. I > thought we did that before, but it's been a year or so. I think it is indistinguishable from other cases like the PCI bus in the docking station on my (older) Dell laptop. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org