From owner-freebsd-current@FreeBSD.ORG Tue Apr 5 19:48:03 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 462D616A4CE; Tue, 5 Apr 2005 19:48:03 +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 8B89543D1F; Tue, 5 Apr 2005 19:48:02 +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 j35Jm09I000724; Tue, 5 Apr 2005 21:48:00 +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 j35JlxsF000723; Tue, 5 Apr 2005 21:47:59 +0200 (CEST) (envelope-from antoine) Date: Tue, 5 Apr 2005 21:47:59 +0200 From: Antoine Brodin To: John Baldwin Message-Id: <20050405214759.3921d21d.antoine.brodin@laposte.net> In-Reply-To: <200504051449.30871.jhb@FreeBSD.org> References: <200504051349.13620.jhb@FreeBSD.org> <20050405204106.15e9d993.antoine.brodin@laposte.net> <200504051449.30871.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 19:48:03 -0000 John Baldwin wrote: > On Tuesday 05 April 2005 02:41 pm, Antoine Brodin wrote: > > John Baldwin wrote: > > > Ok, I see the issue now. The problem is that the BIOS sets the IRQ > > > registers in the PCI devices to values that don't match how the links are > > > programmed and we tend to trust the BIOS over the links in those cases. > > > Can you tell me what IRQ sk0 gets if you don't use ACPI? Does it get 5 > > > or 9? If it gets 9, does it work ok? > > > > > > You can try this patch for ACPI. Unfortunately, some BIOSes lie when you > > > ask a link which IRQ it is routed to, so I'm not sure if this patch can > > > be committed as is. Nate, do you know if such BIOSen only return no IRQ > > > at all (0 or 255) when they lie rather than a bogus "valid" IRQ? > > > > Without ACPI, sk0 gets irq 5 and it works ok. > > > > With your patch and ACPI, sk0 no longer timeouts, and it's usable. > > But I still have interrupt storms. > > dmesg: http://bsd.miki.eu.org/~antoine/current+acpi+patch.dmesg > > Well, all the interrupts are now routed the same as with the old ACPI code. > Perhaps, can you try commenting out the code that calls _DIS in > acpi_pci_link_attach()? Specifically, here: > And let me know if that makes a difference. Thanks ! That makes everything work well ! Also, backing out your previous change and only #if0ing the code that calls _DIS makes everything work well too. So I guess the _DIS methods of my BIOS are the culprit. Antoine