From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 7 17:10:59 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 46AC816A401; Fri, 7 Apr 2006 17:10:59 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7542043D5C; Fri, 7 Apr 2006 17:10:53 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k37HAvYA031183; Fri, 7 Apr 2006 13:11:00 -0400 X-ORBL: [71.139.116.48] Received: from [10.0.0.53] (ppp-71-139-116-48.dsl.snfc21.pacbell.net [71.139.116.48]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k37HAmW2134106; Fri, 7 Apr 2006 13:10:49 -0400 Message-ID: <44369CEF.1040702@root.org> Date: Fri, 07 Apr 2006 10:10:07 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: John Baldwin References: <20060406113433.O6088@netserv1.chg.ru> <200604061103.16570.jhb@freebsd.org> <20060407125705.T67462@netserv1.chg.ru> <200604071046.50669.jhb@freebsd.org> In-Reply-To: <200604071046.50669.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 07 Apr 2006 17:10:59 -0000 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. -- Nate