From: Tim Kay <timk@advfn.com>
To: Matt_Domsch@Dell.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advanced Programmable Interrupt Controller (APIC)?
Date: Fri, 15 Mar 2002 16:18:58 +0000 [thread overview]
Message-ID: <200203151617.g2FGHKs28765@mail.advfn.com> (raw)
In-Reply-To: <71714C04806CD51193520090272892170452B462@ausxmrr502.us.dell.com>
In-Reply-To: <71714C04806CD51193520090272892170452B462@ausxmrr502.us.dell.com>
Matt,
I'll repeat this here too:
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
The above is a diagnostic from a FreeBSD box bootup, this would seem to
suggest that the motherboard rather than Linux is at fault....
Tim
On Friday 15 Mar 2002 16:06, Matt_Domsch@Dell.com wrote:
> > 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.
>
> To the best of my knowledge, BIOS and Linux work together to set up the
> APICs properly on the PowerEdge 6400 (and all our other servers too). If
> someone has proof that we don't, and what should be done instead, please
> let me know.
>
> Thanks,
> Matt
--
----------------
Tim Kay
systems administrator
Advfn.com Plc - http://www.advfn.com/
timk@advfn.com
Tel: 020 7070 0941
Fax: 020 7070 0959
next prev parent reply other threads:[~2002-03-15 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 16:06 Matt_Domsch
2002-03-15 16:18 ` Tim Kay [this message]
2002-03-15 18:45 ` Joe Korty
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 11:34 Mark Hounschell
2002-03-15 16:03 ` Tim Kay
2002-03-15 17:29 ` Mark Hounschell
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=200203151617.g2FGHKs28765@mail.advfn.com \
--to=timk@advfn.com \
--cc=Matt_Domsch@Dell.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®