mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Kay <timk@advfn.com>
To: dmarkh@cfl.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advanced Programmable Interrupt Controller (APIC)?
Date: Fri, 15 Mar 2002 16:03:46 +0000	[thread overview]
Message-ID: <200203151602.g2FG27s10703@mail.advfn.com> (raw)
In-Reply-To: <3C91DC2D.BBEF50F6@cfl.rr.com>
In-Reply-To: <3C91DC2D.BBEF50F6@cfl.rr.com>

Mark,
	we have a similar problem using PowerEdge 2450s 1550s and 6400s, all our 
machines are running with noapic in the lilo config which sounds like it 
isn't an option for you. I'd be interested where you heard about Dell 
stuffing up the setup of the APIC chip because we may be able to take this up 
with them. I've had no reply from the list for the message below (maybe it 
would be better posted to Kernel Traffic SMP but that's a very quiet list). 
Anyway maybe the BSD diagnostics will help you investigate this.

--------------------enc---------------
Hello,
just a quickie, our Dell Poweredge boxes - Serverworks motherboard - are 
continually pumping out IO-APIC errors as I've reported here before, we have 
three of the same boxes running FreeBSD (limitless file descriptors per 
process - sorry, we need it!) and I've just noticed that dmesg on these says 
that:

IO APIC - APIC_IO: Testing 8254 interrupt delivery
APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 
2 
APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 

Does this help anyone diagnose the error??

/-------------------enc------------------



On Friday 15 Mar 2002 11:34, Mark Hounschell wrote:
> 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

-- 
----------------
Tim Kay
systems administrator
Advfn.com Plc - http://www.advfn.com/
timk@advfn.com
Tel: 020 7070 0941
Fax: 020 7070 0959

  reply	other threads:[~2002-03-15 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 11:34 Mark Hounschell
2002-03-15 16:03 ` Tim Kay [this message]
2002-03-15 17:29   ` Mark Hounschell
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=200203151602.g2FG27s10703@mail.advfn.com \
    --to=timk@advfn.com \
    --cc=dmarkh@cfl.rr.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

all inboxes | Powered by JetHome®