From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 17:00:41 2005 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 689E416A4CE; Tue, 5 Apr 2005 17:00:41 +0000 (GMT) Received: from barton.dreadbsd.org (massena-4-82-67-196-50.fbx.proxad.net [82.67.196.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CC7343D49; Tue, 5 Apr 2005 17:00:40 +0000 (GMT) (envelope-from antoine@massena-4-82-67-196-50.fbx.proxad.net) Received: from barton.dreadbsd.org (localhost [127.0.0.1]) by barton.dreadbsd.org (8.13.3/8.13.1) with ESMTP id j35Gx2Ak000717; Tue, 5 Apr 2005 18:59:38 +0200 (CEST) (envelope-from antoine@massena-4-82-67-196-50.fbx.proxad.net) Received: (from antoine@localhost) by barton.dreadbsd.org (8.13.3/8.13.1/Submit) id j35GwVVp000716; Tue, 5 Apr 2005 18:58:31 +0200 (CEST) (envelope-from antoine) Date: Tue, 5 Apr 2005 18:58:31 +0200 From: Antoine Brodin To: John Baldwin Message-Id: <20050405185831.2484695e.antoine.brodin@laposte.net> In-Reply-To: <200504051110.35735.jhb@FreeBSD.org> References: <424EF205.6010202@root.org> <20050402234142.440b3449.antoine.brodin@laposte.net> <200504051110.35735.jhb@FreeBSD.org> X-Mailer: Sylpheed version 1.9.7 (GTK+ 2.6.4; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: k-gleb@yandex.ru cc: dan.cojocar@gmail.com cc: nate@root.org Subject: Re: Interrupt storm 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, 05 Apr 2005 17:00:41 -0000 John Baldwin wrote: > On Saturday 02 April 2005 04:41 pm, Antoine Brodin wrote: > > Nate Lawson wrote: > > > I'm a little confused. I don't know of anyone that has problems with > > > the 6-current PCI irq code that works on 5-stable (which is what your > > > cvs command updates it to). > > > > > > Do either of you have a problem with irq routing on 6-current that works > > > on 5-stable? Please send details if so. > > > > Hi, > > > > I have this problem too, but since it's on a desktop I didn't really > > care about acpi. > > > > Here are some details: > > > > current with pci irq code from 23-Nov-2004 dmesg: > > http://bsd.miki.eu.org/~antoine/current+oldacpi.dmesg > > > > current with current pci irq code dmesg: > > http://bsd.miki.eu.org/~antoine/current+acpi.dmesg > > (there are timeouts and interrupt storms) > > > > acpi tables and asl: > > http://bsd.miki.eu.org/~antoine/acpidump > > So the differences in actual IRQ assignments look like this: > > 13c13 > < pcib1: slot 4 INTA routed to irq 5 via \\_SB_.PCI0.LNK2 > --- > > pcib1: slot 4 INTA routed to irq 9 via \\_SB_.PCI0.LNK2 > 15,16c15,16 > < pcib1: slot 7 INTA is already routed to irq 12 > < pcib1: slot 10 INTA routed to irq 11 via \\_SB_.PCI0.LNK1 > --- > > pcib1: slot 7 INTA routed to irq 12 via \\_SB_.PCI0.LNK4 > > pcib1: slot 10 INTA routed to irq 12 via \\_SB_.PCI0.LNK1 > > That is, LNK2 is routed to 9 rather than 5 and LNK1 is routed to 12 rather > than 11. > > I'm not sure why it does this unless somehow the wrong device_t is getting > associated with a handle. > > > grep 'LNK[12]' current+acpi.dmesg > pci_link10: irq 11 on acpi0 > pci_link11: irq 5 on acpi0 > pcib1: matched entry for 1.4.INTA (src \\_SB_.PCI0.LNK2:0) > pcib1: slot 4 INTA routed to irq 9 via \\_SB_.PCI0.LNK2 > pcib1: matched entry for 1.10.INTA (src \\_SB_.PCI0.LNK1:0) > pcib1: slot 10 INTA routed to irq 12 via \\_SB_.PCI0.LNK1 > > Can you apply this patch and provide a non-verbose dmesg? Here it is: http://bsd.miki.eu.org/~antoine/current+acpi+semiverbose.dmesg Cheers, Antoine