From owner-freebsd-questions@FreeBSD.ORG Sat May 9 14:46:24 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 BBF7C10656F0 for ; Sat, 9 May 2009 14:46:24 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-bw0-f165.google.com (mail-bw0-f165.google.com [209.85.218.165]) by mx1.freebsd.org (Postfix) with ESMTP id 39A9E8FC13 for ; Sat, 9 May 2009 14:46:23 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by bwz9 with SMTP id 9so1851714bwz.43 for ; Sat, 09 May 2009 07:46:23 -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=/6k8W56JgJDaXRRX85+c0QHRLOKrdMxnavJTRwrLJFc=; b=TcnwIEwbmINP5ly5TJBmqoPfpuJDpDnokaCH6m/1g4EsL4ggVKOCz95o+0XiSKAt88 6izQe8C7+yCHg0oP2AWKa34n1fiKGgLalSyJdEN4CF0A37PpAzZQKOUhgqQM74Hqbmaw RdTg2gcSK11f5bReko8bMenH1dkx7md+HcNvc= 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=OpuFR8YbFjaY99UR516/Otkd4zugp1iSV10xjbUHb88Kfmm+KPnL4LXoW7SZjuhEOK X/h6XQui3daqHyCZ/RJVWynlcsN0DCVXy8J4afgguuPtQgSG5R21NNA04cqeifSIiCYP RY4G9Dh30recfZnl93ZojN3b8pLiALHRIDdO4= MIME-Version: 1.0 Received: by 10.239.154.145 with SMTP id e17mr274101hbc.95.1241880382983; Sat, 09 May 2009 07:46:22 -0700 (PDT) In-Reply-To: <4a04702a.ZaIfHAUzw/YexVK2%perryh@pluto.rain.com> References: <4a04702a.ZaIfHAUzw/YexVK2%perryh@pluto.rain.com> Date: Sat, 9 May 2009 16:46:22 +0200 Message-ID: <3a142e750905090746g5324d8ffl1ea10645c0e5f45c@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: Sat, 09 May 2009 14:46:25 -0000 On 5/8/09, perryh@pluto.rain.com wrote: > What, exactly, is an "interrupt storm", and how do I fix it? > > I have added a 64GB Patriot flash drive to a 7.0 system, but it does > not seem to be working properly. Pertinent parts of dmesg.boot: > > FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium II/Pentium II Xeon/Celeron (449.85-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > > Features=0x183f9ff > real memory = 67100672 (63 MB) > avail memory = 51662848 (49 MB) > ... > atapci1: port > 0x1800-0x180f,0x14f0-0x14ff,0x14e0-0x14ef,0x14d0-0x14df,0x14a0-0x14bf,0x1000-0x10ff > irq 9 at device 16.0 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ... > ad6: FAILURE - SET_MULTI status=51 error=4 > ad6: 61136MB at ata3-master SATA150 > > At first things look OK, despite the "FAILURE" message: > > $ ls -l /dev/ad6* > crw-r----- 1 root operator 0, 88 May 3 20:30 /dev/ad6 > $ file -s /dev/ad6 > /dev/ad6: x86 boot sector, Microsoft Windows XP MBR, Serial 0x9e5523de > $ grep -w ad6 /usr/local/etc/mtools.conf > drive f: file="/dev/ad6" > $ mdir f: > init F: non DOS media > Cannot initialize 'F:' > > Now this seems a bit odd: file(1) says it's a Windows disk, but > mdir(1) says it isn't. (Note that there are no slices, else the > initial ls(1) should have shown them, so I suppose the drive has > a single FAT filesystem as one would expect on a floppy disk.) > Then, when I tried to investigate further by examining the contents > of the drive with "od -c /dev/ad6 | more", I got one screenful of > output followed by (on console and in dmesg): > > 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=10712 > 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? > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Output of "vmstat -i"? -- Paul