From owner-freebsd-hackers Tue Oct 24 02:34:09 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA01858 for hackers-outgoing; Tue, 24 Oct 1995 02:34:09 -0700 Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id CAA01844 for ; Tue, 24 Oct 1995 02:33:58 -0700 Received: by Sysiphos id AA20734 (5.67b/IDA-1.5 for hackers@freebsd.org); Tue, 24 Oct 1995 10:32:35 +0100 Message-Id: <199510240932.AA20734@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 24 Oct 1995 10:32:34 +0100 In-Reply-To: guido@gvr.win.tue.nl (Guido van Rooij) "clk interrupts > 150/sec???" (Oct 23, 22:59) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: guido@gvr.win.tue.nl (Guido van Rooij) Subject: Re: clk interrupts > 150/sec??? Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk On Oct 23, 22:59, Guido van Rooij wrote: } Subject: clk interrupts > 150/sec??? } How can this be explained: } } [~] guido@iaehv> vmstat -i } interrupt total rate } clk0 irq0 3884051 156 } ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ } rtc0 irq8 3173264 128 } fdc0 irq6 1 0 } sc0 irq1 2462 0 } ed0 irq5 3667585 147 } } I always thought clk0 should have a rate of 100/sec. Well, you got PCI devices in your system ? Don't ask for details :-) Just substract 100 from clk0 to find out the accumulated rate of PCI interrupts ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/staff/esser/esser.html