From: William Lee Irwin III <wli@holomorphy.com>
To: neel vanan <neelvanan@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: acpi related error.....
Date: Sat, 13 Dec 2003 04:03:34 -0800 [thread overview]
Message-ID: <20031213120334.GP8039@holomorphy.com> (raw)
In-Reply-To: <20031213115733.79739.qmail@web9505.mail.yahoo.com>
On Sat, Dec 13, 2003 at 03:57:33AM -0800, neel vanan wrote:
> Currently i am working on RedHat9.0 kernel 2.4.20-8, i
> am compiling kernel 2.6.0-test11 with NUMA and SMP
> enabled. I had selected summit though i am having
> non-summit box. When i am trying to make bzImage in
> the last i get this message:
> drivers/built-in.o(.init.text+0x30cf): In function
> `acpi_parse_slit':
> : undefined reference to `acpi_numa_slit_init'
> drivers/built-in.o(.init.text+0x30f0): In function
> `acpi_parse_processor_affinity':
> : undefined reference to
> `acpi_numa_processor_affinity_init'
You are likely enabling CONFIG_NUMA on a PC subarch or trying to build
CONFIG_X86_SUMMIT without CONFIG_ACPI; this is ridiculous as PC means
non-NUMA and Summit means ACPI. I'm not sure how you selected this
combination.
Best to turn off CONFIG_NUMA unless you have an x440, x445, or NUMA-Q.
-- wli
next prev parent reply other threads:[~2003-12-13 12:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S263478AbTLEJ0s/20031205092648Z+878@vger.kernel.org>
2003-12-05 9:34 ` Kernel panic neel vanan
2003-12-05 14:19 ` William Lee Irwin III
2003-12-06 5:47 ` William Lee Irwin III
2003-12-13 11:57 ` acpi related error neel vanan
2003-12-13 12:03 ` William Lee Irwin III [this message]
2004-01-05 11:56 ` Kernel panic.. in 3.0 Enterprise Linux neel vanan
2004-01-05 12:08 ` Christophe Saout
2004-01-05 12:23 ` Rik van Riel
2004-01-05 12:33 ` Christophe Saout
2004-01-05 12:21 ` Andreas Unterkircher
2004-01-05 12:24 ` Arjan van de Ven
2004-01-05 12:43 ` Kresimir Sparavec
2004-01-06 21:18 ` Lukas Postupa
2004-01-07 7:56 ` 2.6.0 works with 3.0 Enterprise Linux or not neel vanan
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=20031213120334.GP8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neelvanan@yahoo.com \
/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.