From owner-freebsd-questions@FreeBSD.ORG Mon Jul 3 12:07:15 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 6047816A403 for ; Mon, 3 Jul 2006 12:07:15 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from matrix.teledomenet.gr (dns1.teledomenet.gr [213.142.128.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 106BB43D96 for ; Mon, 3 Jul 2006 12:07:09 +0000 (GMT) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by matrix.teledomenet.gr (8.12.10/8.12.10) with ESMTP id k63C77EY022036; Mon, 3 Jul 2006 15:07:07 +0300 From: Nikos Vassiliadis To: freebsd-questions@freebsd.org Date: Mon, 3 Jul 2006 15:04:38 +0300 User-Agent: KMail/1.9.1 References: <44A8D770.5060808@swehack.se> <44A8F0D6.4060307@swehack.se> <200607031306.12477.Danovitsch@vitsch.net> In-Reply-To: <200607031306.12477.Danovitsch@vitsch.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607031504.39332.nvass@teledomenet.gr> Cc: "Daan Vreeken \[PA4DAN\]" , nocturnal 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: Mon, 03 Jul 2006 12:07:15 -0000 On Monday 03 July 2006 14:06, Daan Vreeken [PA4DAN] wrote: > On Monday 03 July 2006 12:26, nocturnal wrote: > > Hi > > > > The clock? > > > > 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 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 systat -vmstat $time shows interrupts per second regarding the last $time seconds