From: adamm@galacticasoftware.com
To: linux-kernel@vger.kernel.org
Subject: Promise Ultra100 TX2 driver problems
Date: Mon, 11 Nov 2002 13:26:48 -0600 [thread overview]
Message-ID: <20021111192648.GA31966@galacticasoftware.com> (raw)
Hi all,
There seems to be a major problem with the promise drivers.
It is detected and seems to work, but there is a very
large number of interrupts being generated:
adamm@polaris:/proc$ cat interrupts
CPU0 CPU1
0: 2727665 2683676 IO-APIC-edge timer
1: 1 1 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
5: 1137650 1130539 IO-APIC-level eth0
7: 0 0 IO-APIC-edge soundblaster
8: 1812 1790 IO-APIC-edge rtc
9: 711977 709641 IO-APIC-level sym53c8xx, eth1
10: 2097584287 2097514818 IO-APIC-level ide2, ide3
NMI: 0 0
LOC: 5411428 5411427
ERR: 0
MIS: 3013
adamm@polaris:/proc$ uptime
12:57:30 up 15:01, 1 user, load average: 0.36, 0.35, 0.40
Or a staggering ~40000 interrupts per second!
This is a dual PPro machine and it is using 30% cpu time
just to handle the interrupts.
Anyone know what is going on?
Thanks,
Adam
next reply other threads:[~2002-11-11 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 19:26 adamm [this message]
2002-11-11 22:38 ` Promise Ultra100 TX2 driver problems Alan Cox
2002-11-11 22:17 ` Gabor Z. Papp
2002-11-11 23:11 ` Adam Majer
2002-12-13 19:19 ` Adam Majer
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=20021111192648.GA31966@galacticasoftware.com \
--to=adamm@galacticasoftware.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox