From owner-freebsd-questions@FreeBSD.ORG Sun May 10 21:00:54 2009 Return-Path: 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 E62521065672 for ; Sun, 10 May 2009 21:00:54 +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 A1CA38FC12 for ; Sun, 10 May 2009 21:00:53 +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 n4AL0qcZ080935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 10 May 2009 14:00:53 -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 n4AL0qvF080934; Sun, 10 May 2009 14:00:52 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA12526; Sun, 10 May 09 13:56:11 PDT Date: Sun, 10 May 2009 13:56:01 -0700 From: perryh@pluto.rain.com To: onemda@gmail.com Message-Id: <4a073f61.RrxzC7F5VdEWczgd%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> <4a070969.mYZsiV8emLhJVvVg%perryh@pluto.rain.com> <3a142e750905101247h7f01d6a4obbcbc81d3ae4b7a7@mail.gmail.com> In-Reply-To: <3a142e750905101247h7f01d6a4obbcbc81d3ae4b7a7@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 May 2009 21:00:55 -0000 "Paul B. Mahol" wrote: > On 5/10/09, perryh@pluto.rain.com wrote: ... > >> >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> >> > ad6: FAILURE - SET_MULTI status=51 > >> >> > error=4 > >> >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > >> >> > > >> >> > etc. etc. until I killed it with ^C ... > >> >> > >> >> 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. > > Try editing /boot/device.hints lines with irq or adding similar > lines ... How would I go about figuring out what to add or change? I suppose I want to move either uhci0 or atapci1 to an unused irq, but my recollection is that I don't have unlimited choice in the matter because the IRQ used by a particular PCI device -- or at least the set available for assignment -- is determined by how the motherboard is wired. Granted it's been several years since I was into PCI at this level.