From: Andrew Morton <akpm@osdl.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: y-goto@jp.fujitsu.com, mbligh@google.com, apw@shadowen.org,
linux-kernel@vger.kernel.org, 76306.1226@compuserve.com,
Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
Gerd Hoffmann <kraxel@suse.de>,
Rusty Russell <rusty@rustcorp.com.au>,
Zachary Amsden <zach@vmware.com>
Subject: Re: sparsemem panic in 2.6.17-rc5-mm1 and -mm2
Date: Tue, 6 Jun 2006 21:58:13 -0700 [thread overview]
Message-ID: <20060606215813.9bfe07af.akpm@osdl.org> (raw)
In-Reply-To: <20060607094355.b77ed883.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 7 Jun 2006 09:43:55 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Tue, 6 Jun 2006 00:27:58 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> >
> > I tried sparsemem on my little x86 box here. Boots OK, after fixing up the
> > kswapd_init() patch (below).
> >
> > I'm wondering why I have 4k of highmem:
> >
>
> Could you show /proc/iomem of your 4k HIGHMEM box ?
> Does 4k HIGHMEM exist only when SPARSEMEM is selected ?
Turns out that my 4 kbyte highmem zone (at least, as reported in
/proc/meminfo) is due to
vdso-randomize-the-i386-vdso-by-moving-it-into-a-vma.patch
vdso-randomize-the-i386-vdso-by-moving-it-into-a-vma-tidy.patch
vdso-randomize-the-i386-vdso-by-moving-it-into-a-vma-arch_vma_name-fix.patch
vdso-randomize-the-i386-vdso-by-moving-it-into-a-vma-vs-x86_64-mm-reliable-stack-trace-support-i386.patch
vdso-randomize-the-i386-vdso-by-moving-it-into-a-vma-vs-x86_64-mm-reliable-stack-trace-support-i386-2.patch
I don't think that was intended.
It'll be a screwup in the handling of MAXMEM. That patch is doing strange
things with MAXMEM. They are unchangelogged, uncommented and
possibly-hacky-looking things too, so I have no intention of fixing it.
next prev parent reply other threads:[~2006-06-07 5:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 0:51 sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Martin Bligh
2006-06-06 3:07 ` Andrew Morton
2006-06-06 5:19 ` KAMEZAWA Hiroyuki
2006-06-06 5:36 ` Yasunori Goto
2006-06-06 7:27 ` Andrew Morton
2006-06-07 0:43 ` KAMEZAWA Hiroyuki
2006-06-07 4:58 ` Andrew Morton [this message]
2006-06-07 5:36 ` Rusty Russell
2006-06-07 5:50 ` Andrew Morton
2006-06-07 6:49 ` Rusty Russell
2006-06-07 9:26 ` Andy Whitcroft
2006-06-07 16:29 ` Andrew Morton
2006-06-07 16:35 ` Andrew Morton
2006-06-07 17:50 ` Andy Whitcroft
2006-06-15 12:28 ` [PATCH] zone handle unaligned zone boundaries Andy Whitcroft
2006-06-07 17:22 ` sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Andy Whitcroft
2006-06-06 23:42 ` Andrew Morton
2006-06-07 9:16 ` Mel Gorman
2006-06-07 17:38 ` Andy Whitcroft
2006-06-07 17:41 ` Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 3:50 Chuck Ebbert
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=20060606215813.9bfe07af.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=76306.1226@compuserve.com \
--cc=apw@shadowen.org \
--cc=arjan@infradead.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=y-goto@jp.fujitsu.com \
--cc=zach@vmware.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