From: Jens Gecius <jens@gecius.de>
To: linux-kernel@vger.kernel.org
Subject: /proc/interrupts on 2.4.13-1
Date: 17 Oct 2001 22:11:03 -0400 [thread overview]
Message-ID: <87n12pbsug.fsf@maniac.gecius.de> (raw)
Hi folks!
/proc/interrupts shows
CPU0 CPU1
0: 6700068 6617178 IO-APIC-edge timer
1: 15716 15044 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
3: 0 1 IO-APIC-edge serial
8: 1 1 IO-APIC-edge rtc
9: 788995 790370 IO-APIC-level eth0
10: 93412 93466 IO-APIC-level aic7xxx, Ensoniq AudioPCI
11: 3476219 3482580 IO-APIC-level nvidia
12: 31650 31277 IO-APIC-level usb-uhci, usb-uhci
14: 505063 501971 IO-APIC-edge ide0
15: 10 0 IO-APIC-edge ide1
NMI: 0 0
LOC: 13315157 13315147
ERR: 0
MIS: 3690
Especially the last makes me curious: does MIS mean "missed"? And:
might this be related to esd running here having some trouble to keep
playing without short little "breaks"? The count on MIS is actually
growing steadily, the uptime is currently only 37 hours.
The box is used most time with two niced seti-processes. Other than
that, cpu stat is hardly at 10%.
--
Tschoe, http://gecius.de/gpg-key.txt - Fingerprint:
Jens 1AAB 67A2 1068 77CA 6B0A 41A4 18D4 A89B 28D0 F097
next reply other threads:[~2001-10-18 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 2:11 Jens Gecius [this message]
2001-10-18 4:06 ` /proc/interrupts on 2.4.13-1 Mark Hahn
2001-10-18 9:56 ` Jens Gecius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n12pbsug.fsf@maniac.gecius.de \
--to=jens@gecius.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.