From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Interrupt saturation
Date: Sun, 28 Feb 2010 11:55:04 +0200 [thread overview]
Message-ID: <49e12aa4c1953073c3a6e3aee67a6998@proxima.alt.za> (raw)
The workstation I'm using presently seems to trigger as many
interrupts as stats(1) can display, while the syscall graph is also
extremely busy.
I presume this is anomalous. Killing the single instance of
timesync(1) does not seem to make any difference at all.
Any suggestions to where I should look? I'm not running anything that
would make me suspicious, but I'm going to restart the system just to
check.
++L
next reply other threads:[~2010-02-28 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 9:55 lucio [this message]
2010-02-28 14:50 ` erik quanstrom
2010-03-01 3:13 ` ron minnich
2010-03-01 17:39 ` lucio
2010-03-01 18:00 ` erik quanstrom
2010-03-01 19:12 ` lucio
2010-03-01 22:50 ` erik quanstrom
2010-03-02 4:01 ` lucio
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=49e12aa4c1953073c3a6e3aee67a6998@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).