Re: OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88

[Meelis Roos]

> > > Could you try to boot with a sensible mem=xxx value to see if limiting the memory
> > > helps.
> > 
> > Like mem=256M? Will try.
> Think just a little more - I do not think this will help.

Tried it on the 2G V210. It changes the picture. With 2G RAM, it 
just hangs.

With mem=256M it produces a crash in strlen and of_alias_scan like in 
V100 with 1G.

mem=512M results in the same strlen error.

mem=1G results in a stranger error:

[    0.000000] Kernel panic - not syncing: ERROR: Failed to allocate 0x90 bytes below 0x0.
[    0.000000] 
[    0.000000] Call Trace:
[    0.000000]  [00000000007a6a28] memblock_alloc_base+0x28/0x38
[    0.000000]  [000000000079ca50] prom_early_alloc+0xc/0x60
[    0.000000]  [00000000007ae090] of_pdt_create_node.part.0+0x4/0xe0
[    0.000000]  [00000000007ae250] of_pdt_build_devicetree+0x30/0xa0
[    0.000000]  [000000000079c4a8] prom_build_devicetree+0x18/0x38
[    0.000000]  [00000000007a03c0] paging_init+0x59c/0x6bc
[    0.000000]  [000000000079be50] setup_arch+0xf8/0x108
[    0.000000]  [000000000079a4e8] start_kernel+0x78/0x30c
[    0.000000]  [00000000006a3e80] tlb_fixup_done+0x98/0xa0
[    0.000000]  [0000000000000000]           (null)

The working machines have 512M RAM, 834M RAM and 2G RAM so it's not just 
the amount of RAM.

-- 
Meelis Roos (mroos@xxxxxxxx)
--
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/