From owner-freebsd-questions@FreeBSD.ORG Tue Jul 4 06:59:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D80C16A4DF for ; Tue, 4 Jul 2006 06:59:35 +0000 (UTC) (envelope-from nocturnal@swehack.se) Received: from mail2.swebase.com (mail2.swebase.com [82.99.44.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D54843D58 for ; Tue, 4 Jul 2006 06:59:33 +0000 (GMT) (envelope-from nocturnal@swehack.se) Received: from [82.99.47.5] by mail2.swebase.com (MDaemon.PRO.v8.1.0.R) with ESMTP id 16-md50000043341.msg for ; Tue, 04 Jul 2006 08:58:37 +0200 Message-ID: <44AA1160.70409@swehack.se> Date: Tue, 04 Jul 2006 08:57:36 +0200 From: nocturnal User-Agent: Thunderbird 1.5 (X11/20060116) MIME-Version: 1.0 To: Chuck Swiger References: <44A8D770.5060808@swehack.se> <44A8F0D6.4060307@swehack.se> <200607031306.12477.Danovitsch@vitsch.net> <200607031504.39332.nvass@teledomenet.gr> <44A90EDA.6040707@mac.com> In-Reply-To: <44A90EDA.6040707@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-Sender: nocturnal@swehack.se X-MDRemoteIP: 82.99.47.5 X-Return-Path: nocturnal@swehack.se X-MDaemon-Deliver-To: freebsd-questions@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail2 X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00 autolearn=ham version=3.0.4 X-Spam-Level: X-Spam-Processed: mail2.swebase.com, Tue, 04 Jul 2006 08:58:41 +0200 Cc: freebsd-questions@freebsd.org, Nikos Vassiliadis Subject: Re: Interrupt using all the CPU 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: Tue, 04 Jul 2006 06:59:35 -0000 Hi kern.clockrate: { hz = 100, tick = 10000, profhz = 1024, stathz = 128 } I'm going to see if it's possible to disable USB from the BIOS later today, if not, can i disable the USB devices in the kernel? Med vänliga hälsningar Stefan Midjich aka nocturnal [Swehack] http://swehack.se Chuck Swiger wrote: > Nikos Vassiliadis wrote: >> On Monday 03 July 2006 14:06, Daan Vreeken [PA4DAN] wrote: > [ ... ] >>>> interrupt total rate >>>> irq0: clk 25130235 99 >>>> irq1: atkbd0 4 0 >>>> irq6: fdc0 1 0 >>>> irq7: ppc0 1 0 >>>> irq8: rtc 288300 1 >>>> irq11: atapci1 637852 2 >>>> irq12: vr0 uhci0+ 3890833 15 >>>> irq13: npx0 1 0 >>>> irq14: ata0 54 0 >>>> Total 29947281 119 >>> Hmm.. There seems to be nothing wrong with these numbers. If you were >>> suffering from an interrupt storm I would have expected much larger >>> numbers >>> in the "rate" column. The column "rate" shows the average number of >>> interrupts / second. In total your system handles about 120 interrupts / >>> second, so that shouldn't be a problem. >> >> I have the feeling that rate is calculated like this: >> number of interrupts since boottime / seconds of uptime > > OK. > >> so, this won't help if his is having now an interrupt storm >> while most of the time the system is interrupted ~ 120 times >> per second > > An interrupt storm on what, though? > > The ~100 interrupts per second from the clock on IRQ0 are absolutely > normal with HZ=100; the only other candidate seems to be the combination > of vr0 & USB controller on IRQ 12. > > If it's possible to disable the USB controller for a bit in the BIOS, it > would be interesting to see whether that makes any difference. You can > probably kill the parallel port, too. > > It's also interesting to note that IRQ 8, the RTC, seems to be mostly > idle-- normally that fires at stathz=128...check "sysctl kern.clockrate". > >> systat -vmstat $time shows interrupts per second regarding the last >> $time seconds > > Right, although the output from "vmstat 1" would survive being pasted > into email better, I suspect. >