All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Tuynman, William (JSC-DT/USA)[USA]" <william.tuynman-1@nasa.gov>
Cc: linux-smp@vger.kernel.org
Subject: Re: unexpected IO-APIC, 2.4.36 SMP, AMD dual core Opteron
Date: Wed, 06 Feb 2008 19:07:16 -0500	[thread overview]
Message-ID: <47AA4BB4.1030702@tmr.com> (raw)
In-Reply-To: <E654F66E76890D4AB45E2DD0D042A46CBC5FE2@NDJSEVS21B.ndc.nasa.gov>

Tuynman, William (JSC-DT/USA)[USA] wrote:
> Hello,
> 	I have been getting this "An unexpected IO-APIC was found" message. In checking, it occurs on 2.4.34 also.
>
> 	The kernel was compiled for 32 bit execution and is running on an AMD dual core Opteron. The machine is an HP Proliant, DL 585.
>
> I'm attaching, as text, a portion of the messages file which contains all of the boot information.
>
> I would be happy to assist with providing additional information that would be helpful to you.
>
>   
The first question I have is, why are you running a 2.4 kernel on a 
modern CPU? I suspect the SMP logic in 2.4.26 is a decade older than the 
hardware. SMP was pretty unusual then, multi-core was just not an end 
user feature. I don't doubt that the IO-APIC may have unsupported features.

Might I suggest that you boot off a recent "live CD" like Fedora or 
Puppy Linux, just to see if you still see a problem. If not, you will 
have more information to evaluate your next step.


-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



  reply	other threads:[~2008-02-07  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 17:30 unexpected IO-APIC, 2.4.36 SMP, AMD dual core Opteron Tuynman, William (JSC-DT/USA)[USA]
2008-02-07  0:07 ` Bill Davidsen [this message]
2008-02-07 19:32   ` Tuynman, William (JSC-DT/USA)[USA]
2008-02-07 20:52     ` Bill Davidsen
2008-02-16  0:03       ` Tuynman, William (JSC-DT/USA)[USA]

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=47AA4BB4.1030702@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-smp@vger.kernel.org \
    --cc=william.tuynman-1@nasa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.