public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Allan Sandfeld <linux@sneulv.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Idiot-proof APIC?
Date: Wed, 20 Feb 2002 14:49:52 -0800	[thread overview]
Message-ID: <20020220224952.GB20060@matchmail.com> (raw)
In-Reply-To: <E16dc5j-0000CB-00@Princess>
In-Reply-To: <E16dc5j-0000CB-00@Princess>

On Wed, Feb 20, 2002 at 08:07:47PM +0100, Allan Sandfeld wrote:
> Hi, I just want to share some of my stupidity and my experience with it with 
> you. 
> I recently had the misfortune to try to put two celerons on an SMP-board. The 
> bios correctly ignored the second cpu, but the linux-kernel(2.4.17). Would 
> boot almost normally then emit two APIC-errors to the console(error 2 and 
> 6?), and shortly after freeze completely. After one of the celerons was 
> removed linux was completely stable. Something inside makes me question 
> whether or not the APIC people have taken idiots into consideration. The 
> kernel should detect two cpu, detect they are not SMP and then operate using 
> just one. Not very importent, but correct behavior.
> Anyway for specs the board it was an Acorp 6A815EPD. Proberbly the one of the 
> only SMP i815 mortherboards in the world.
> 

Actually, with the correct adapters, celerons can be made SMP safe.

I would immagine that it is hard to detect if there is a adapter operating
correctly from the APIC code...

Mike

  reply	other threads:[~2002-02-20 22:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 19:07 Idiot-proof APIC? Allan Sandfeld
2002-02-20 22:49 ` Mike Fedyk [this message]
2002-02-21  0:19   ` Mark Cooke
2002-02-21  9:48 ` Andrey Panin
2002-02-21 10:05 ` Maciej W. Rozycki

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=20020220224952.GB20060@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@sneulv.dk \
    /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