initrd allocation

[Paul Nasrat]

On Thu, 2006-01-12 at 22:54 -0600, Nathan Lynch wrote:
> Hi-
> 
> I have a system where claim is failing for an initrd only slightly
> larger than 4096K.  The initial 4MB allocation succeeds, but when we
> try to grab another 4MB, the claim fails.  However, yaboot doesn't
> seem to handle this case properly and continues to boot the kernel
> with a truncated initrd.
> 
> This is with a vendor version of yaboot based on 1.3.12, but looks
> like upstream would have the same problem.
> 
> second/yaboot.c:
> <snip>
> #define INITRD_CHUNKSIZE 0x400000
> 1) Is there some historical reason for INITRD_CHUNKSIZE to be as large
>    as it is?  I have worked around the issue by defining it to
>    0x100000.

Commited

> 
> 2) If a "secondary" claim fails, shouldn't we assert/prom_pause or
>    something?

Commited.

Paul