Date: Thu, 10 Jun 2004 05:19:37 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: sos@FreeBSD.org Subject: Re: Interrupt storm detected (was: Re: hang after after update: "adX: FAILURE - already active DMA on this device" (ICH5 system)) Message-ID: <20040610051739.C5702@gamplex.bde.org> In-Reply-To: <20040609202412.098e005c@Magellan.Leidinger.net> References: <20040606123224.46e27502@Magellan.Leidinger.net> <20040606140441.13e52926@Magellan.Leidinger.net> <20040608183625.23360ce9.manlix@demonized.net> <20040609202412.098e005c@Magellan.Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 9 Jun 2004, Alexander Leidinger wrote: > On Tue, 8 Jun 2004 18:36:25 +0200 > Johan Pettersson <manlix@demonized.net> wrote: > > > Todays -CURRENT works just fint. It even works as it should with HTT > > enabled now. Wee! :) Can it be the recent ACPI-changes that fixed it? > > Confirmed. > > BTW.: I get "Interrupt storm detected on "irq18: uhci2+"; throttling > interrupt source", is anybody interested in a dmesg of a system? I fixed interrupt storm handling to actually work in more cases. However, if you get the "Interrupt strorm detected" message, then you also get low performance for devices on that interrupt, especially after my changes. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040610051739.C5702>