Hi, On Sun, 18 Feb 2007, Kars de Jong wrote:
pa=0xfffc0000 va=0x3fc0000 I think that's where it should have stopped, however: pa=0x0 va=0x4000000 [new pointer 00001800][new table]
[..]
pa=0x65fc0000 va=0x69fc0000 pa=0x66000000 va=0x6a000000 [new pointer 003c7e00][new table]<1>low bootmem alloc of 4096 bytes failed! Kernel panic - not syncing: Out of low memory Er... huh? My machine has a single chunk of memory starting at 0xfc000000, 64 MB in size. The bootloader says: Found 1 block of memory: Block 0: 0xFC000000 to 0x0xFFFFFFFE (65535K).
That's weird. map_node() in arch/m68k/mm/motorola.c directly works with the size value, so it can't be some pointer problem, which might have wrapped. Could you add a print to check the m68k_memory values? bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
