From owner-freebsd-questions@FreeBSD.ORG Sun May 10 19:47:52 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 6BBFE10656B8 for ; Sun, 10 May 2009 19:47:52 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-fx0-f216.google.com (mail-fx0-f216.google.com [209.85.220.216]) by mx1.freebsd.org (Postfix) with ESMTP id EAC358FC0A for ; Sun, 10 May 2009 19:47:51 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by fxm12 with SMTP id 12so2336191fxm.43 for ; Sun, 10 May 2009 12:47:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hZPERRxz9UdAusnFopDm9SUNXVBzcIPKindeXYtZrxM=; b=MkzBcjgu+auNfVSw/LbQnFw0m9xMyGlR5hwH42ENr7/KBDTK8FTAAx0EeJsJuvdYeA kliQIWgstXzRPEzg2lV7CxMeH+MS7QsUxTNqygRXR21JIwnxs8diYVc018h3YlNrPVLF rLXjOLXE65IIgtPZGwZqNoQxdrNTzPyyh8Isg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GfsEWH03OeA+uOlEIvsur9dtIpWQXOTfRwPtlCqYABIrqkMaSi12ynQn9OysNd2fNQ qrQLlkU2GvcbHIjx3krL5eQeBd+tPCXt6Qd0+GClCJ19VcqaXKHZj/S19C9jEj8yGeRp sZwrBQL+qDUMpLclWvppaIcOnV3vI9IyrBwxU= MIME-Version: 1.0 Received: by 10.239.154.145 with SMTP id e17mr351724hbc.95.1241984870649; Sun, 10 May 2009 12:47:50 -0700 (PDT) In-Reply-To: <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> <4a070969.mYZsiV8emLhJVvVg%perryh@pluto.rain.com> Date: Sun, 10 May 2009 21:47:50 +0200 Message-ID: <3a142e750905101247h7f01d6a4obbcbc81d3ae4b7a7@mail.gmail.com> From: "Paul B. Mahol" To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 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 19:47:52 -0000 On 5/10/09, perryh@pluto.rain.com wrote: > "Paul B. Mahol" wrote: >> On 5/9/09, perryh@pluto.rain.com wrote: >> > "Paul B. Mahol" wrote: >> >> On 5/8/09, 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 >> >> > error=4 >> >> > 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. Try editing /boot/device.hints lines with irq or adding similar lines ... > >> It could be bad configuration, bug or hardware problem. > -- Paul