mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Adam J. Richter" <adam@yggdrasil.com>, gone@us.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64bk5: X86_PC + HIGHMEM boot failure
Date: Sun, 09 Mar 2003 22:27:31 -0800	[thread overview]
Message-ID: <73890000.1047277650@[10.10.2.4]> (raw)
In-Reply-To: <200303092305.PAA02985@adam.yggdrasil.com>

> 	Under linux-2.5.64bk5, CONFIG_X86_PC sets CONFIG_NUMA,
> which sets CONFIG_DISCONTIGMEM.  This causes the version of
> set_max_mapnr_init in arch/i386/mm/discontig.c to be compiled
> in (instead of the one from arch/i386/mm/init.c):
>
> Err, I meant 2.5.64bk4. 

Hmmm ... well I don't see bk4 on ftp.kernel.org, but the same
changes are in my tree ...  I've just checked it, and it doesn't 
do that for me. It should *allow* you to turn on CONFIG_NUMA 
(and that might be broken for PCs still) but it shouldn't be on 
by default ... could you check that you can still disable it?
Works for me ...

M.


config NUMA
        bool "Numa Memory Allocation Support"
        depends on (HIGHMEM64G && (X86_NUMAQ || (X86_SUMMIT && ACPI && !ACPI_HT_
ONLY))) || X86_PC


  reply	other threads:[~2003-03-10  6:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 23:05 Adam J. Richter
2003-03-10  6:27 ` Martin J. Bligh [this message]
2003-03-09 23:08 Adam J. Richter
2003-03-10  8:46 Adam J. Richter
2003-03-10  8:57 ` William Lee Irwin III
2003-03-10 15:14 ` Martin J. Bligh
2003-03-10 17:08 Adam J. Richter
2003-03-10 19:22 Adam J. Richter
2003-03-10 19:18 ` Martin J. Bligh
2003-03-10 19:39 Adam J. Richter

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='73890000.1047277650@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=adam@yggdrasil.com \
    --cc=gone@us.ibm.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®