From owner-freebsd-acpi@FreeBSD.ORG Mon Apr 3 14:31:45 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 460BC16A41F; Mon, 3 Apr 2006 14:31:45 +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 9910243D45; Mon, 3 Apr 2006 14:31:44 +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 k33EVgrl042708; Mon, 3 Apr 2006 10:31:43 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 3 Apr 2006 09:30:44 -0400 User-Agent: KMail/1.9.1 References: <200603311738.02120.jkim@FreeBSD.org> In-Reply-To: <200603311738.02120.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604030930.46207.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1369/Mon Apr 3 06:25:15 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-3.9 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: Jung-uk Kim Subject: Re: IBM x336 does not boot with APIC. 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, 03 Apr 2006 14:31:45 -0000 On Friday 31 March 2006 17:38, Jung-uk Kim wrote: > I tried to install FreeBSD 6.1-BETA4 on IBM x336 and it was not > booting. I googled a bit and I found this is known problem for this > platform: > > http://docs.freebsd.org/cgi/mid.cgi?200510061556.55464.jhb > > To make the system up and running, I had to disable APIC and force > keyboard to attach. Of course, I didn't like that. ;-) > > The first thing I wanted to fix was: > > acpi0: on motherboard > acpi0: [MPSAFE] > pci_open(1): mode 1 addr port (0x0cf8) is 0x80000144 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=80] is there > (id=35908086) > acpi_bus_number: root bus has no _BBN, assuming 0 > acpi_bus_number: can't get _ADR > acpi_bus_number: can't get _ADR > ... > > I added 'PNP0A08' to pcib_ids in src/sys/dev/acpica/acpi_pcib_acpi.c > because this system had this: > > Scope (\_SB) > { > Device (PCI0) > { > Name (_HID, EisaId ("PNP0A08")) > Name (_CID, 0x030AD041) This compat ID is PNP0A03. > ... > > This ID was added in ACPI 3.0 as 'PCI Express Root Bridge', instead of > 'PNP0A03', which is PCI/PCI-X root bridge. However, I got something > like this instead: > > acpi0: could not allocate interrupt > ACPI-0210: *** Error: Unable to install System Control Interrupt > Handler, AE_ALREADY_EXISTS > acpi0: Could not enable ACPI: AE_ALREADY_EXISTS It shouldn't have made a difference since the device should have already probed due to the compat ID. Can you get full verbose dmesg's w/o the patch and w/ the patch? > No driver was able to allocate IRQ after this and I am quite puzzled > right now. Is it correct thing to do? Why does it break? Why can't > I install SCI handler? I bet you have no interrupts on your interrupt controllers (amd64 kernel w/o device atpic and APIC disabled would do it). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org