Re: sparsemem panic in 2.6.17-rc5-mm1 and -mm2

[Andrew Morton]

On Wed, 7 Jun 2006 09:43:55 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:

> On Tue, 6 Jun 2006 00:27:58 -0700
> Andrew Morton <akpm@xxxxxxxx> 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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/