From: Martin Hicks <mort@bork.org>
To: Uher Marek <Marek.Uher@t-mobile.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with NUMA kernel on IBM xSeries 455 server
Date: Wed, 4 Feb 2004 08:21:57 -0500 [thread overview]
Message-ID: <20040204132157.GA3387@localhost> (raw)
In-Reply-To: <6D2F48AA9477864682B4078EFF1BEAF1057F0B7D@RDMKSPE02.rdm.cz>
On Wed, Feb 04, 2004 at 01:46:33PM +0100, Uher Marek wrote:
>
> Hi all,
>
> I have a problem with running Linux on my IBM xSeries 455 server (4 x Intel
> Xeon MP CPU 2.80GHz, 8 GB RAM). I have tried to compile kernel 2.6.2 with
> Summit/EXA (IBM x440) NUMA support, high memory support (64GB), NUMA memory
> allocation support, ACPI and ACPI NUMA support. When I have tried to make
> bzImage I have got this messages:
>
> drivers/built-in.o(.init.text+0x1751): In function `acpi_parse_slit':
> : undefined reference to `acpi_numa_slit_init'
> drivers/built-in.o(.init.text+0x176d): In function `acpi_parse_processor_affinit
> y':
> : undefined reference to `acpi_numa_processor_affinity_init'
> drivers/built-in.o(.init.text+0x1791): In function `acpi_parse_memory_affinity':
> : undefined reference to `acpi_numa_memory_affinity_init'
> drivers/built-in.o(.init.text+0x1850): In function `acpi_numa_init':
> : undefined reference to `acpi_numa_arch_fixup'
> make: *** [.tmp_vmlinux1] Error 1
>
> Do you have any idea? I don't know what is wrong.
According to include/linux/acpi.h these functions are platform
dependent. There are ia64 versions, but I don't see them for non-ia64
arches.
This is the problem. I don't know anything about Summit, so maybe
someone else can better help you. Perhaps there is an extra summit
patch somewhere? Or maybe you must turn off ACPI for this machine,
although that seems unlikely.
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
next prev parent reply other threads:[~2004-02-04 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 12:46 Uher Marek
2004-02-04 13:21 ` Martin Hicks [this message]
2004-02-04 16:15 ` Martin J. Bligh
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=20040204132157.GA3387@localhost \
--to=mort@bork.org \
--cc=Marek.Uher@t-mobile.cz \
--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®