From: Mark Hounschell <dmarkh@cfl.rr.com>
To: linux-kernel@vger.kernel.org
Cc: markh@compro.net
Subject: Advanced Programmable Interrupt Controller (APIC)?
Date: Fri, 15 Mar 2002 06:34:05 -0500 [thread overview]
Message-ID: <3C91DC2D.BBEF50F6@cfl.rr.com> (raw)
We have a number of DELL boxes in house. The most recent a 6400 (quad p4 box). Also a couple
of dual boxes. They all lock up intermittantly when APIC is enabled. There seems to be no solid way of reproducing the
hangs they just hang randomly. With APIC disabled they do not.
The app that we have to run on these boxes requires that APIC is enabled for irq affinity.
It is a soft real-time app that cannot tollerate the jitter. It will run but interrupt latency
is unexceptable without the irq affinity set. I've read on many lists that if you have random
lockups that you should disableapic. I've also got a number of NON-DELL boxes that don't exibit this lockup. Now I've
also heard that DELL does not properly setup the APIC chip in
the bios because MS os's don't use it. Have no idea if this is true or not. We are using
vanilla kernels (2.4.16) with some process affinity patches applied. I've also noticed that
on the quad boxes (6400) that irqs 0,1,2 cannot be directed to or from a particular processor.
This is also a problem with our app. Mostly it's the lockups that occur with APIC enabled that
is our roadblock for using these nice DELL boxes for our app. Can anyone shed some light on
this.
Thanks in advance
and regards
--
Mark Hounschell
dmarkh@cfl.rr.com
next reply other threads:[~2002-03-15 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 11:34 Mark Hounschell [this message]
2002-03-15 16:03 ` Advanced Programmable Interrupt Controller (APIC)? Tim Kay
2002-03-15 17:29 ` Mark Hounschell
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 16:06 Matt_Domsch
2002-03-15 16:18 ` Tim Kay
2002-03-15 18:45 ` Joe Korty
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=3C91DC2D.BBEF50F6@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.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