Re: Factory CD boot problem

On Thu, 2014-01-02 at 21:34 +0100, Alexander Graf wrote:

> > boot:
> >  install                    slp                        rescue
> > boot: install
> > Please wait, loading kernel...
> > Allocated 01700000 bytes for kernel @ 03000000
> >   Elf64 kernel loaded...
> > Loading ramdisk...
> > ramdisk loaded 031c5a55 @ 04700000
> > OF stdout device is: /vdevice/vty@30000000
> > Preparing to boot Linux version 3.11.6-3-default (geeko@buildhost) (gcc
> > version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) )
> > #1 SMP Thu Oct 24 16:23:02 UTC 2013 (0ba01b7)
> > Detected machine type: 0000000000000101
> > Max number of cores passed to firmware: 1024 (NR_CPUS = 2048)
> > Calling ibm,client-architecture-support... not implemented
> > command line: quiet sysrq=1 insmod=sym53c8xx insmod=ipr
> > memory layout at init:
> >  memory_limit : 0000000000000000 (16 MB aligned)
> >  alloc_bottom : 00000000078d0000
> >  alloc_top    : 0000000008000000
> >  alloc_top_hi : 0000000077000000
> >  rmo_top      : 0000000008000000
> >  ram_top      : 0000000077000000
> > found display   : /pci@800000020000002/display@1, opening... done
> > Could not allocate memory for RTAS
> 
> Ben, do you know what this means?

Yes, it means what the message says ... prom_init.c couldn't find a big
enough free spot of RAM in the RMA to put RTAS in.

Usually that means a too big ramdisk...

Remember pHyp hands out really tiny RMAs, in this case, 128M, that's it
and that's all OFW can use. Look at RTAS size in the device-tree,
so based on where the kernel is loaded, where the ramdisk is
loaded, the reserved area to keep for the kernel etc... you may not
have enough room left for RTAS.

It could also be that yaboot put things in less than optimal spots

Cheers,
Ben.
> 
> Alex
> 
> > EXIT called ok
> > 0 >
> > 
> > 
> > -- 
> > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]