From owner-freebsd-stable@FreeBSD.ORG Wed Sep 21 07:37:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC1EF16A41F for ; Wed, 21 Sep 2005 07:37:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3E7C43D5C for ; Wed, 21 Sep 2005 07:37:23 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j8L7bFYa007261 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 21 Sep 2005 17:37:16 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j8L7bFSR058098; Wed, 21 Sep 2005 17:37:15 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j8L7bE2D058097; Wed, 21 Sep 2005 17:37:14 +1000 (EST) (envelope-from pjeremy) Date: Wed, 21 Sep 2005 17:37:14 +1000 From: Peter Jeremy To: Joel Rees Message-ID: <20050921073714.GJ40237@cirb503493.alcatel.com.au> References: <43307286.4020601@leadhill.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable Subject: Re: ep0 Interrupt Storm, 3Com EtherLink III (PnP) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2005 07:37:24 -0000 On Wed, 2005-Sep-21 10:34:43 +0900, Joel Rees wrote: > >On 平成 17/09/21, at 5:35, Billy Newsom wrote: > >>Does anyone know exactly what to do about an interrupt storm, > >My understanding is that an interrupt storm is a noisy interrupt >line. It could be a flaky chip, an incompatible setting for the >interrupt lines in the BIOS, a loose wire, dust or some sort of >condensate (very typically tobacco tar) on the PC board, ... Or a driver bug: Failing to clear the condition causing the interrupt before sending an end-of-interrupt notification to the device will cause it to re-assert the interrupt request. I've also seen it when a device configured for polling (and hence without an installed interrupt handler) decides to raise an interrupt and gets upset at the interrupt not being handled. -- Peter Jeremy