On Mon, 2007-10-29 at 15:43 -0400, Dave Jones wrote:
> On Mon, Oct 29, 2007 at 08:03:09PM +0100, Andi Kleen wrote:
> > > > But if allocating bootmem >4G doesn't work on these systems
> > > > most likely they have more problems anyways. It might be better
> > > > to find out what goes wrong exactly.
> > > Any ideas on what to instrument ?
> >
> > See what address the bootmem_alloc_high returns; check if it overlaps
> > with something etc.
> >
> > Fill the memory on the system and see if it can access all of its memory.
>
> Martin, as you have one of the affected systems, do you feel up to this?
Faking a node at 0000000000000000-000000001fff0000
Bootmem setup node 0 0000000000000000-000000001fff0000
sparse_early_mem_map_alloc: returned address ffff81000070b000
My box has 512MB of RAM.
Cheers,
Martin.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
