From: Paul Jackson <pj@sgi.com>
To: hawkes@sgi.com
Cc: tony.luck@gmail.com, akpm@osdl.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, steiner@sgi.com, djh@sgi.com,
hawkes@sgi.com, jh@sgi.com, edwardsg@sgi.com
Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024
Date: Wed, 11 Jan 2006 16:09:37 -0800 [thread overview]
Message-ID: <20060111160937.921a719d.pj@sgi.com> (raw)
In-Reply-To: <20060105213948.11412.45463.sendpatchset@tomahawk.engr.sgi.com>
When I tried to build a 2.6.15-mm2 kernel with NR_CPUS 1024, and turned
on some of the LOCK DEBUG options:
1160c1160
< # CONFIG_DEBUG_SLAB is not set
---
> CONFIG_DEBUG_SLAB=y
1163,1164c1163,1164
< # CONFIG_DEBUG_SPINLOCK is not set
< # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
---
> CONFIG_DEBUG_SPINLOCK=y
> CONFIG_DEBUG_SPINLOCK_SLEEP=y
then the build failed:
LD .tmp_vmlinux1
arch/ia64/kernel/built-in.o(.init.text+0x68b2): In function `topology_init':
arch/ia64/kernel/ivt.S:1465: undefined reference to `__you_cannot_kmalloc_that_much'
make: *** [.tmp_vmlinux1] Error 1
Backing off to 512 CPUs built ok.
There are a couple of kmalloc() calls in topology_init(). I didn't try
to figure out which one blew up, nor did I try to investigate further.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-01-12 0:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 21:39 [PATCH] ia64: change defconfig to NR_CPUS==1024 hawkes
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-06 17:06 ` John Hawkes
2006-01-06 8:38 ` Arjan van de Ven
2006-01-12 0:09 ` Paul Jackson [this message]
2006-01-12 19:04 ` Christoph Lameter
-- strict thread matches above, loose matches on Subject: below --
2006-01-06 17:19 Luck, Tony
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:26 ` Matthew Wilcox
2006-01-06 17:45 Luck, Tony
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:37 ` Christoph Lameter
2006-01-06 18:59 ` Arjan van de Ven
2006-01-06 20:17 ` Alan Cox
2006-01-06 20:18 ` Randy.Dunlap
2006-01-06 20:42 ` Rohit Seth
2006-01-06 21:00 ` Dave Jones
2006-01-06 18:25 ` Adrian Bunk
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=20060111160937.921a719d.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=djh@sgi.com \
--cc=edwardsg@sgi.com \
--cc=hawkes@sgi.com \
--cc=jh@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tony.luck@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox