public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Jacob Martin <martin@cs.uga.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM:  OOPSes in PREEMPT SMP for AMD Opteron Dual-Core with Memhole Mapping (non tainted kernel)
Date: 15 Jun 2005 21:51:44 +0200
Date: Wed, 15 Jun 2005 21:51:44 +0200	[thread overview]
Message-ID: <20050615195144.GA40993@muc.de> (raw)
In-Reply-To: <200506131953.16958.martin@cs.uga.edu>

On Mon, Jun 13, 2005 at 07:53:16PM +0000, Jacob Martin wrote:
> On Monday 13 June 2005 10:06 am, Andi Kleen wrote:
> > On Sun, Jun 12, 2005 at 03:29:50PM -0400, Jacob Martin wrote:
> > > Hardware memhole mapping never seems to work, or causes lockups right
> > > away.  I need to test it further though.
> > >
> > > I have discovered that with the following features enabled:
> > >
> > > 1.  Software memhole mapping
> > > 2.  Continuous,
> > >
> > > linux sees the entire 4GB of memory.  However, when things start getting
> > > requested from the upper half, there are Oopses generated.  Attached are
> > > two Oopses that occurred under the test scenario described.
> >
> > What happens when you boot with numa=off or with numa=noacpi ?
> 
> You got it!  It seems to be working just fine without it compiled into the 
> kernel.

Not compiled what in the kernel? I just wanted you to boot
the kernel with these options. 


> 
> > The system seems to believe it has memory in an area not covered
> > by mem_map.
> 
> I think you hit it right on the head.
> 
> I enabled NUMA because I had anticipated upgrading later.  So I guess if you 
> don't actually have NUMA set up hardware-wise, and enable this module, then 
> you will have problems.

No, it should work fine in theory. 

> 
> Maybe a simple update to the kernel "K8 NUMA support" Processor feature's help 
> section should be made to note this?  Or, is there something that could be 
> fixed somewhere.  I wouldn't mind helping, it was baffling me for two weeks.

It is something that must be either fixed or workarounded (if it's a bug
in your BIOS, which is quite possible) 

Can you send me the full dmesg from a numa boot again? 

-Andi

  reply	other threads:[~2005-06-15 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 22:36 PROBLEM: OOPSes in PREEMPT SMP for AMD Opteron Dual-Core with Memhole Mapping (non tainted kernel) Jacob Martin
2005-06-11 10:41 ` Andi Kleen
2005-06-11 14:31   ` Jacob Martin
2005-06-12 19:29   ` Jacob Martin
2005-06-13 10:06     ` Andi Kleen
2005-06-13 19:53       ` Jacob Martin
2005-06-15 19:51         ` Andi Kleen [this message]
2005-06-15 20:46           ` Jacob Martin
2005-06-15 22:33           ` Jacob Martin

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=20050615195144.GA40993@muc.de \
    --to=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@cs.uga.edu \
    /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