From owner-freebsd-questions@FreeBSD.ORG Mon Apr 14 10:11:23 2008 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 C29C1106564A for ; Mon, 14 Apr 2008 10:11:23 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 60BC68FC0C for ; Mon, 14 Apr 2008 10:11:23 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 438371CC91; Mon, 14 Apr 2008 02:11:22 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Mon, 14 Apr 2008 12:11:16 +0200 User-Agent: KMail/1.9.7 References: <480325AB.3010909@janh.de> In-Reply-To: <480325AB.3010909@janh.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200804141211.18956.fbsd.questions@rachie.is-a-geek.net> Cc: Jan Henrik Sylvester , lysergius2001 , ix260@yahoo.co.uk Subject: Re: Interrupt storm with 7.0 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: Mon, 14 Apr 2008 10:11:23 -0000 On Monday 14 April 2008 11:36:43 Jan Henrik Sylvester wrote: > lysergius2001 wrote: > > Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and > > now have a continuous interrupt storm on IRQ17. This is a shared IRQ for > > ath0 and echi0. Never saw this on 6.3??? Any suggestions? > > Just another contribution to the collection of interrupt storms maybe > related to ath: > > Whenever I plug in my ath1 on cardbus0, I get exactly one storm: > interrupt storm detected on "irq10:"; throttling interrupt source > > ath1: mem 0xd0220000-0xd022ffff irq 10 at device 0.0 on > cardbus0 > > Anyhow, I am not sure, if it is really ath causing this. During boot, I > get one storm, too, that is on irq 10, but my ath0 on pci2 is on irq 9: > > ath0: mem 0xd0200000-0xd020ffff irq 9 at device 4.0 on pci2 > [...] > interrupt storm detected on "irq10:"; throttling interrupt source > > I do not get interrupt storms on irq 9 and I have already had that storm > before I replaced my minipci iwi0 with ath0: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078684.html > > The reply to that posting was that it is probably related to USB: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078687.html > > Moreover, I have a bunch of other devices sharing irq 10: > > vgapci0: port 0x3000-0x30ff mem > 0xd8000000-0xdfffffff,0xd0100000-0xd010ffff irq 10 at device 0.0 on pci1 > uhci0: port 0x1800-0x181f > irq 10 at device 29.0 on pci0 > uhci2: port 0x1840-0x185f > irq 10 at device 29.2 on pci0 > ehci0: mem > 0xd0000000-0xd00003ff irq 10 at device 29.7 on pci0 > fwohci0: mem > 0xd0218000-0xd02187ff,0xd0210000-0xd0213fff irq 10 at device 7.0 on pci2 > pcm0: port 0x1c00-0x1cff,0x18c0-0x18ff mem > 0xd0000c00-0xd0000dff,0xd0000800-0xd00008ff irq 10 at device 31.5 on pci0 > > On our problematic irq, we both have got echi0. Thus, the second storm I > get upon attaching ath1 might not be directly caused by ath. > > No suggestions, just more data. I dug through daily security runs and \o/ the machine got rebooted one time, so I got a dmesg: +uhci0: port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 +uhci0: [GIANT-LOCKED] +ath0: mem 0x88000000-0x8800ffff irq 11 at device 0.0 on cardbus0 +ath0: Ethernet address: 00:11:95:69:1d:eb +ath0: mac 7.9 phy 4.5 radio 5.6 Not ehci, but uhci. Still... I can't find if it had cpufreq. The kernel config I still have and it had it compiled in, but it doesn't show in the dmesg. Only power/sleep button, lid switch and thermal zone. A typical storm session looks like this: +ath0: link state changed to DOWN +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +interrupt storm detected on "irq11:"; throttling interrupt source +ath0: link state changed to UP -- Mel Problem with today's modular software: they start with the modules and never get to the software part.