On zo, 2007-02-18 at 16:55 +0100, Roman Zippel wrote:
Hi,
On Sun, 18 Feb 2007, Kars de Jong wrote:
On za, 2007-02-17 at 23:23 +0100, Kars de Jong wrote:
I think I'll add an early serial console to see if I can debug it.
Which gives the following output:
ABCGHIJK
Linux version 2.6.20-m68k-hp300 (turrican@kars) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #6 Sun Feb 18 15:12:50 CET 2007
Detected HP9000 model 425t
HP300: early console registered
low bootmem alloc of 4096 bytes failed!
Kernel panic - not syncing: Out of low memory
It seems the call to hp300_setup_serial_console() is happen too early, at
this point no allocator is ready yet.
That may be, but in the kernel that produced this output there is no
call to hp300_setup_serial_console() at all. I hacked up a quick console
using CONFIG_EARLY_PRINTK instead.
I enabled DEBUG in arch/m68k/mm/motorola.c, which gave the following
interesting output (intermediate lines snipped):
ABCGHIJK
Linux version 2.6.20-m68k-hp300 (turrican@kars) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #7 Sun Feb 18 17:50:01 CET 2007
Detected HP9000 model 425t
HP300: early console registered
start of paging_init (00001000, fc252000)
pa=0xfc000000 va=0x0
pa=0xfc040000 va=0x40000
pa=0xfc080000 va=0x80000
pa=0xfc0c0000 va=0xc0000
pa=0xfc100000 va=0x100000
pa=0xfc140000 va=0x140000
pa=0xfc180000 va=0x180000
pa=0xfc1c0000 va=0x1c0000
pa=0xfc200000 va=0x200000
pa=0xfc240000 va=0x240000
pa=0xfc280000 va=0x280000
pa=0xfc2c0000 va=0x2c0000
pa=0xfc300000 va=0x300000
pa=0xfc340000 va=0x340000
pa=0xfc380000 va=0x380000
pa=0xfc3c0000 va=0x3c0000
pa=0xfc400000 va=0x400000 [new table]
...
pa=0xffc00000 va=0x3c00000 [new table]
pa=0xffc40000 va=0x3c40000
pa=0xffc80000 va=0x3c80000
pa=0xffcc0000 va=0x3cc0000
pa=0xffd00000 va=0x3d00000
pa=0xffd40000 va=0x3d40000
pa=0xffd80000 va=0x3d80000
pa=0xffdc0000 va=0x3dc0000
pa=0xffe00000 va=0x3e00000
pa=0xffe40000 va=0x3e40000
pa=0xffe80000 va=0x3e80000
pa=0xffec0000 va=0x3ec0000
pa=0xfff00000 va=0x3f00000
pa=0xfff40000 va=0x3f40000
pa=0xfff80000 va=0x3f80000
pa=0xfffc0000 va=0x3fc0000
I think that's where it should have stopped, however:
pa=0x0 va=0x4000000 [new pointer 00001800][new table]
pa=0x40000 va=0x4040000
pa=0x80000 va=0x4080000
pa=0xc0000 va=0x40c0000
pa=0x100000 va=0x4100000
pa=0x140000 va=0x4140000
pa=0x180000 va=0x4180000
pa=0x1c0000 va=0x41c0000
pa=0x200000 va=0x4200000
pa=0x240000 va=0x4240000
pa=0x280000 va=0x4280000
pa=0x2c0000 va=0x42c0000
pa=0x300000 va=0x4300000
pa=0x340000 va=0x4340000
pa=0x380000 va=0x4380000
pa=0x3c0000 va=0x43c0000
pa=0x400000 va=0x4400000 [new table]
...
pa=0x65c00000 va=0x69c00000 [new table]
pa=0x65c40000 va=0x69c40000
pa=0x65c80000 va=0x69c80000
pa=0x65cc0000 va=0x69cc0000
pa=0x65d00000 va=0x69d00000
pa=0x65d40000 va=0x69d40000
pa=0x65d80000 va=0x69d80000
pa=0x65dc0000 va=0x69dc0000
pa=0x65e00000 va=0x69e00000
pa=0x65e40000 va=0x69e40000
pa=0x65e80000 va=0x69e80000
pa=0x65ec0000 va=0x69ec0000
pa=0x65f00000 va=0x69f00000
pa=0x65f40000 va=0x69f40000
pa=0x65f80000 va=0x69f80000
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).
Any ideas?
-
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
