public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is needed to boot 2.6 on opteron dual core
Date: Wed, 18 May 2005 17:39:14 -0400	[thread overview]
Message-ID: <428BB602.2040909@tmr.com> (raw)
In-Reply-To: <m1br7a804l.fsf@muc.de>

Andi Kleen wrote:
> "Cabaniols, Sebastien" <sebastien.cabaniols@hp.com> writes:
> 
> 
>>Hello lkml,
>>
>>I am trying to boot a dual core Opteron box with linux 2.6 and it is
>>crashing very early (swapper process dies, backtrace shows SMP_boot....
>>Stuff) and I was wondering what patches are needed to boot a 2.6 kernel
>>on a dual core machine.
> 
> 
> It should work with most kernels. Just the level of tuning
> during runtime varies (with more tuning the newer the kernel) 
> Certainly does for me at least on the AMD reference motherboards/BIOS.

Could you clarify that? I have to install one when it comes in to the 
owner, and I'm not sure how you would do "runtime tuning" if it doesn't 
boot. Did you mean boot parameters, BIOS diddling, or ???

I didn't order the unit, but I believe it's an IBM rack mounted 2U case, 
whatever that might be.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  reply	other threads:[~2005-05-18 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 11:48 What is needed to boot 2.6 on opteron dual core Cabaniols, Sebastien
2005-05-17 13:15 ` Andi Kleen
2005-05-18 21:39   ` Bill Davidsen [this message]
2005-05-18 22:01     ` Andi Kleen
2005-05-23 20:24       ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2005-05-24 12:22 Cabaniols, Sebastien

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=428BB602.2040909@tmr.com \
    --to=davidsen@tmr.com \
    --cc=ak@muc.de \
    --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