From owner-freebsd-current@FreeBSD.ORG Tue Sep 9 10:08:28 2003 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 857C216A4BF for ; Tue, 9 Sep 2003 10:08:28 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id F327743FE3 for ; Tue, 9 Sep 2003 10:08:27 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 89602 invoked by uid 1000); 9 Sep 2003 17:08:28 -0000 Date: Tue, 9 Sep 2003 10:08:28 -0700 (PDT) From: Nate Lawson To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= In-Reply-To: Message-ID: <20030909100311.T89599@root.org> References: <20030906141328.Q78854@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT cc: current@freebsd.org Subject: Re: ACPI problems on MSI K7D 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: Tue, 09 Sep 2003 17:08:28 -0000 On Tue, 9 Sep 2003, Dag-Erling [iso-8859-1] Smørgrav wrote: > Nate Lawson writes: > > Please report the dmesg from boot -v as that should help figure out why > > pci_cfgregopen() fails. > > Full log attached, both with and without ACPI. Perhaps someone who knows our PCI code better could address this? Here is the valid case (without ACPI): pci_open(1): mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=700c1022) Here is the invalid case (with ACPI): acpi0: on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x80ff003c pci_open(2): mode 2 enable port (0x0cf8) is 0xff panic: AcpiOsDerivePciId unable to initialize pci bus Obviously, the pci_open(2) is bogus. If no one else addresses this, I will try to get to it soon. For now, try changing the panic to a return 0 and see how it affects system operation. > > Also, I think the following should be "\_S3": > > Name (\SS3, Package (0x04) > > That shouldn't have any impact on my problem though, should it? Nope, just something I noticed. -Nate