From owner-freebsd-current@FreeBSD.ORG Fri Nov 12 20:30:40 2004 Return-Path: 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 D03D416A4FF for ; Fri, 12 Nov 2004 20:30:40 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F5AA43D45 for ; Fri, 12 Nov 2004 20:30:40 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30365 invoked from network); 12 Nov 2004 20:30:40 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 12 Nov 2004 20:30:39 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iACKUJo4053969; Fri, 12 Nov 2004 15:30:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Michal Mertl Date: Fri, 12 Nov 2004 13:54:21 -0500 User-Agent: KMail/1.6.2 References: <4194BF4C.5090007@traveller.cz> In-Reply-To: <4194BF4C.5090007@traveller.cz> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411121354.21409.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: "Wilkinson, Alex" Subject: Re: dealing with interupt storms ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 12 Nov 2004 20:30:41 -0000 On Friday 12 November 2004 08:49 am, Michal Mertl wrote: > Alext Wilkinson wrote: > > Hi all, > > > > How does one stop an interrupt storm in RELENG_5 ? > > > >> >From top(1) > > > > CPU states: 10.9% user, 0.0% nice, 3.9% system, 85.3% interrupt, 0.0% > > idle > > > > >From vmstat(1) > > > > total rate > > ----- ---- > > irq18: uhci2 bt0++ 9187313 426 > > Answer to your question might be to modify sysctl hw.intr_storm_threshold. > > I can confirm, there is a problem in bktr(4) generating interrupt storms. > For several months I was seeing messages about interrupt storms and system > run fine (I haven't been using bktr for long time so I didn't care). I > tried to roll the bktr sources as far back as possible (that is to the time > before phk changed dev_t to struct cdev *) to no avail, so I suspect the > problem is caused by something outside of the driver. After latest changes > to interrupt throttling (rev. 1.117 of src/sys/kern_intr.c by jhb) the > system performance is pretty affected until I unload bktr driver because > bktr now seems to be doing some 120000 interrupts/second and not getting > throttled). This sounds like the bktr(4) driver doesn't properly program the device to turn off interrupts when it detaches if I've parsed this correctly. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org