From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 22 22:19:48 2005 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 32B5216A421 for ; Tue, 22 Nov 2005 22:19:48 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEEDA43D49 for ; Tue, 22 Nov 2005 22:19:46 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2446761 for multiple; Tue, 22 Nov 2005 17:19:44 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAMMJfOm085334; Tue, 22 Nov 2005 17:19:41 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Tue, 22 Nov 2005 17:16:56 -0500 User-Agent: KMail/1.8.2 References: <200511171725.27877.jhb@freebsd.org> <98968A23-2F26-4A01-801D-65C8731D71A7@club-internet.fr> <200511221543.18043.jhb@freebsd.org> In-Reply-To: <200511221543.18043.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511221716.57350.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: [PATCH] Fix weird PCI bus numbers with pci_linkX 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, 22 Nov 2005 22:19:48 -0000 On Tuesday 22 November 2005 03:43 pm, John Baldwin wrote: > On Tuesday 22 November 2005 03:03 pm, Mathieu Prevot wrote: > > Weird addresses disappeared. But I don't why I have invalid IRQ ... > > > > ... > > ACPI APIC Table: > > ioapic0 irqs 0-23 on motherboard > > ... > > pcib0: port 0xcf8-0xcff on acpi0 > > pci_link9: BIOS IRQ 11 for 0.16.INTA is invalid > > pci_link9: BIOS IRQ 5 for 0.16.INTB is invalid > > pci_link9: BIOS IRQ 10 for 0.16.INTC is invalid > > pci_link10: BIOS IRQ 10 for 0.17.INTC is invalid > > pci_link11: BIOS IRQ 11 for 0.18.INTA is invalid > > ... > > uhci0: port 0xd400-0xd41f irq 21 at > > device 16.0 on pci0 > > You are using an I/O APIC. In your ASL, your pci link resources get > different IRQs when using APIC than when not using APIC. The BIOS never > uses APIC mode, so it programs IRQs for each PCI device according to the > non-APIC (aka PIC) mode. The messages above mean that we found out during > the boot that the interrupt for 0.16.INTA (PCI bus 0, device (slot) 16, pin > A#) is routed via the pci_link9 device, and that the BIOS had set the IRQ > for that device to 11. However, when we switch over to APIC mode, then the > list of valid IRQs for that link device are something like 20, 21, 22, and > 23. The IRQ the BIOS used (11) isn't in that list, so we ignore it and > pick an IRQ out of the list (21 in this case). You don't need to worry > about these messages. I'll see if I can't shut them up in this case (BIOS > uses an ISA IRQ but this link device only has non-ISA IRQs). > > In fact, I've just whipped up a patch to shut these warnings up. It's > attached. Patch got killed apparently. You can fetch it from http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org