From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:37:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 310D816A41F for ; Mon, 28 Nov 2005 21:37:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6207443DA3 for ; Mon, 28 Nov 2005 21:37:10 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2756543 for multiple; Mon, 28 Nov 2005 16:37:13 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASLaw2Q063566; Mon, 28 Nov 2005 16:36:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 28 Nov 2005 16:25:52 -0500 User-Agent: KMail/1.8.2 References: <002801c5f081$f01ff200$642a15ac@smiley> <20051124071405.GA15743@pit.databus.com> <4387EC9E.5040709@elischer.org> In-Reply-To: <4387EC9E.5040709@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281625.53629.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Julian Elischer Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 21:37:24 -0000 On Saturday 26 November 2005 12:03 am, Julian Elischer wrote: > So I haven't been paying too much attention to this thread and now > suddenly I find that > I may have a variant of this problem. > > I have been tasked with adding a 4 port intel (em) based card into a > Dell 2850 based system. > It is based on the intel E7525 chipset and running 4.11. > > I have noticed that this system has irq's in use from 16 down (Maybe in > -current it may use higher) > but that some interrupt counts seem to move together, as if they are > wired to gether. > > I also have the problem that the system seems to get completely wedged > sometimes > as it seems to get into the em driver interupt routine and never get out > again, > or if it does get out it gets called right back in again. > > Can someone who was following this tell me if this is the same problem? > > I can get into the kernel debugger and it usually shows the > amr interrupt handler, having been interrupted by the em driver, (and > that interrupted by > the keyboard interrupt handler for the KDB entry.) > > It seems that no matter how hard it tries or how often it is called the em > driver is unable to clear this interrupt. > > > Am I reading this correctly in that it seems to be the same problem as was > being discussed here? It could be. 4.x handles interrupt storms much more poorly (more prone to deadlock) than 5.x and later, and it still masks level-triggerred interrupts in the APIC while it waits for the handler to run. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org