From owner-freebsd-questions@FreeBSD.ORG  Sun May 10 17:13:41 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7C7DC106578F
	for <freebsd-questions@freebsd.org>;
	Sun, 10 May 2009 17:13:41 +0000 (UTC)
	(envelope-from perryh@pluto.rain.com)
Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34])
	by mx1.freebsd.org (Postfix) with ESMTP id 531C08FC14
	for <freebsd-questions@freebsd.org>;
	Sun, 10 May 2009 17:13:41 +0000 (UTC)
	(envelope-from perryh@pluto.rain.com)
Received: from agora.rdrop.com (66@localhost [127.0.0.1])
	by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n4AHDalq045738
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Sun, 10 May 2009 10:13:37 -0700 (PDT)
	(envelope-from perryh@pluto.rain.com)
Received: (from uucp@localhost)
	by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n4AHDa2v045737; 
	Sun, 10 May 2009 10:13:36 -0700 (PDT)
Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407)
	id AA11978; Sun, 10 May 09 10:05:53 PDT
Date: Sun, 10 May 2009 10:05:45 -0700
From: perryh@pluto.rain.com
To: onemda@gmail.com
Message-Id: <4a070969.mYZsiV8emLhJVvVg%perryh@pluto.rain.com>
References: <4a04702a.ZaIfHAUzw/YexVK2%perryh@pluto.rain.com>
	<3a142e750905090746g5324d8ffl1ea10645c0e5f45c@mail.gmail.com>
	<4a05f963.OI3CMfJ3/j2hbi4D%perryh@pluto.rain.com>
	<3a142e750905100452s73aa391bjcdc8fea49636ee37@mail.gmail.com>
In-Reply-To: <3a142e750905100452s73aa391bjcdc8fea49636ee37@mail.gmail.com>
User-Agent: nail 11.25 7/29/05
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-questions@freebsd.org
Subject: Re: how to fix "interrupt storm"
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 May 2009 17:13:42 -0000

"Paul B. Mahol" <onemda@gmail.com> wrote:
> On 5/9/09, perryh@pluto.rain.com <perryh@pluto.rain.com> wrote:
> > "Paul B. Mahol" <onemda@gmail.com> wrote:
> >> On 5/8/09, perryh@pluto.rain.com <perryh@pluto.rain.com> wrote:
> >> > What, exactly, is an "interrupt storm", and how do I fix it?
> > ...
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   interrupt storm detected on "irq9:"; throttling interrupt source
> >> >   ad6: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED>
> >> >   ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936
> >> >
> >> > etc. etc. until I killed it with ^C.  (Just entering "q", to cause
> >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not
> >> > stop the spew of messages.)
> >> >
> >> > What does this indicate?  Hardware problems?  Bad configuration?
> >> > Something else?
> >>
> >> Output of "vmstat -i"?
> >
> > $ vmstat -i
> > interrupt                          total       rate
> > irq0: clk                      497386851       1004
> > irq1: atkbd0                        2491          0
> > irq3: xl0                           2030          0
> > irq6: fdc0                            11          0
> > irq7: ppbus0 ppc0                      1          0
> > irq8: rtc                       63654324        128
> > irq9: uhci0+                      166216          0
>
> uhci0 is doing strange things, what usb device are connected?

There are no USB devices connected.  I think those must actually
be atapci1 interrupts, since irq9 is where dmesg reported it.

> It could be bad configuration, bug or hardware problem.