From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 2 12:42:59 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FA071065676 for ; Tue, 2 Jun 2009 12:42:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D784F8FC1A for ; Tue, 2 Jun 2009 12:42:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8D86546B39; Tue, 2 Jun 2009 08:42:58 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 8495E8A02C; Tue, 2 Jun 2009 08:42:57 -0400 (EDT) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Tue, 2 Jun 2009 08:11:34 -0400 User-Agent: KMail/1.9.7 References: <4A24D29A.5030604@ts.fujitsu.com> In-Reply-To: <4A24D29A.5030604@ts.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906020811.35082.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 02 Jun 2009 08:42:57 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: Re: Failure to get past a PCI bridge 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: Tue, 02 Jun 2009 12:42:59 -0000 On Tuesday 02 June 2009 3:19:54 am Josef Moellers wrote: > Hi, > > (I've posted this to freebsd-questions before. Ian Smith redirected me > to this list). > > I'm trying to install 7.2-RELEASE on a pretty new system (a Fujitsu > RX300S5). > The first obstacle was the fact that while the system has an > AT-Keyboard-Controller, it ist not used (keyboard and mouse are > connected via USB) and I have found that I can get past that by specifying > > set hint.atkbd.0.disabled=1 > set hint.atkbdc.0.disabled=1 > > The install kernel then boots properly and reaches the "Country Selection". > At that point, no keyboard input is accepted. An optical mouse is off, > so I assume the USB power to be off. > > I have hooked up a serial connection to log the kernel's output (some > 1000+ lines): > > set boot_serial=1 > set boot_verbose=1 > set boot_multicons=1 > set console="comconsole vidconsole" > > The following lines make me wonder if the kernel fails to get past PCI > bridges and thus can't reach the UHCI controllers: > > pcib0: on acpi0 > pcib0: could not get PCI interrupt routing table for \_SB_.CPU0 - > AE_NOT_FOUND > : > pcib1: on acpi0 > pcib1: could not get PCI interrupt routing table for \_SB_.CPU1 - > AE_NOT_FOUND > : > pcib2: port 0xcf8-0xcff on acpi0 > pcib2: couldn't find _ADR > pcib2: trying bus number 2 > pci2: on pcib2 > pci2: domain=0, physical bus=2 > > I talked to the guy who does the BIOS for the machine and he says that > it makes no sense for the kernel to try and find the _PRT for \_SB_.CPU0 > or \_SB_.CPU1! Can you get an acpidump? It seems that the BIOS has the wrong _HID for the CPU objects and has marked them as Host-PCI bridges instead. Although CPUs should be Processor objects and not Device objects anyway. Sounds like a very busted BIOS. -- John Baldwin