Factory CD boot problem

Hi Dinar,

Thanks for your work on the installation media.

Unfortunately though, openSUSE-13.1-ppc64-NET-ppc64-Build0018-Media.iso
still fails to boot into Linux on my machine. The initrd appears to load
okay but the failure remains when loading RTAS.

The installed system continues to work fine (except it needs some
partition resizing that I was hoping to do via a reinstall), so it
doesn't sound like it's a general problem with the IBM firmware's RTAS
implementation - the firmware did not change since original installation.

Any ideas would be welcome. Maybe reduce initrd size even more?
Or is the presence of the graphics card maybe causing problems due to
OpenFirmware framebuffer size?

Regards,
Andreas

Elapsed time since release of system processors: 5 mins 35 secs

yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
Config file 'yaboot.cnf' read, 342 bytes

Welcome to openSuSE 13.1!

Type "install" to start the YaST installer on this CD/DVD
Type "slp" to start the YaST install via network
Type "rescue" to start the rescue system on this CD/DVD

Welcome to yaboot version r22.8-r1190.SuSE
booted from
'/***@800000020000003/***@2,3/***@1/***@0:1,\suseboot\yaboot.ibm'
running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
'IBM,*********', partition '06-C903E'
Enter "help" to get some basic usage information
boot: help
Press the tab key for a list of defined images.
The label marked with a "*" is the default image, press <return> to
boot it.

To boot any other label simply type its name and press <return>.
It is also possible to expand a label with the tab key.

To boot a kernel image which is not defined in the yaboot configuration
file, enter the kernel image name as [[device:[partno]],]/path, where
"device:" is the OpenFirmware device path to the disk the image
resides on, and "partno" is the partition number the image resides on.
Note that the comma (,) is only required if you specify an OpenFirmware
device, if you only specify a filename you should not start it with a ","
The shortcut '&device;' can be used to specify the OpenFirmware device
path
where yaboot was loaded from.

To load an initrd, specify its path as initrd=[[device:[partno]],]/path

If you omit "device:" and "partno" yaboot will use the values of
"device=" and "partition=" in yaboot.conf, right now those are set to:
device=/***@800000020000003/***@2,3/***@1/***@0
partition=1

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/***@30000000
Preparing to boot Linux version 3.11.6-3-default (***@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 : /***@800000020000002/***@1, opening... done
Could not allocate memory for RTAS
EXIT called ok
0 >

Alexander Graf

2014-01-02 20:34:03 UTC

Post by Andreas FÃ¤rber
Hi Dinar,
Thanks for your work on the installation media.
Unfortunately though, openSUSE-13.1-ppc64-NET-ppc64-Build0018-Media.iso
still fails to boot into Linux on my machine. The initrd appears to load
okay but the failure remains when loading RTAS.
The installed system continues to work fine (except it needs some
partition resizing that I was hoping to do via a reinstall), so it
doesn't sound like it's a general problem with the IBM firmware's RTAS
implementation - the firmware did not change since original installation.
Any ideas would be welcome. Maybe reduce initrd size even more?
Or is the presence of the graphics card maybe causing problems due to
OpenFirmware framebuffer size?
Regards,
Andreas
Elapsed time since release of system processors: 5 mins 35 secs
yaboot starting: loaded at 00040000 00065a88 (0/0/02039a68; sp: 02cbffd0)
Config file 'yaboot.cnf' read, 342 bytes
Welcome to openSuSE 13.1!
Type "install" to start the YaST installer on this CD/DVD
Type "slp" to start the YaST install via network
Type "rescue" to start the rescue system on this CD/DVD
Welcome to yaboot version r22.8-r1190.SuSE
booted from
running with firmware 'IBM,SF240_284' on model 'IBM,9111-285', serial
'IBM,*********', partition '06-C903E'
Enter "help" to get some basic usage information
boot: help
Press the tab key for a list of defined images.
The label marked with a "*" is the default image, press <return> to
boot it.
To boot any other label simply type its name and press <return>.
It is also possible to expand a label with the tab key.
To boot a kernel image which is not defined in the yaboot configuration
file, enter the kernel image name as [[device:[partno]],]/path, where
"device:" is the OpenFirmware device path to the disk the image
resides on, and "partno" is the partition number the image resides on.
Note that the comma (,) is only required if you specify an OpenFirmware
device, if you only specify a filename you should not start it with a ","
The shortcut '&device;' can be used to specify the OpenFirmware device
path
where yaboot was loaded from.
To load an initrd, specify its path as initrd=[[device:[partno]],]/path
If you omit "device:" and "partno" yaboot will use the values of
partition=1
install slp rescue
boot: install
Please wait, loading kernel...
Elf64 kernel loaded...
Loading ramdisk...
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_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 00000000078d0000
alloc_top : 0000000008000000
alloc_top_hi : 0000000077000000
rmo_top : 0000000008000000
ram_top : 0000000077000000
Could not allocate memory for RTAS

Ben, do you know what this means?

Alex

Post by Andreas FÃ¤rber
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: opensuse-ppc+***@opensuse.org
To contact the owner, e-mail: opensuse-ppc+***@opensuse.org

Benjamin Herrenschmidt

2014-01-02 20:51:59 UTC

Post by Andreas FÃ¤rber
install slp rescue
boot: install
Please wait, loading kernel...
Elf64 kernel loaded...
Loading ramdisk...
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_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 00000000078d0000
alloc_top : 0000000008000000
alloc_top_hi : 0000000077000000
rmo_top : 0000000008000000
ram_top : 0000000077000000
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.

Post by Alexander Graf
Alex

Post by Andreas FÃ¤rber
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: opensuse-ppc+***@opensuse.org
To contact the owner, e-mail: opensuse-ppc+***@opensuse.org

Alexander Graf

2014-01-02 21:01:46 UTC

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.

Andreas, could you please dump /proc/device-tree from a working Linux instance and upload it somewhere or at least tell us how big the RTAS payload is? :)

So we have

48MB - ~71MB kernel
71MB - 120MB initrd

So yeah, I can see how there might be too little space left to put the RTAS blob somewhere. But why is yaboot only allocating as of 48MB?

Either way, I guess in your case the easiest solution would be to trim a few firmware blobs from the initrd. I don't think you have qlogic hbas in your system, right? :)

Post by Benjamin Herrenschmidt
It could also be that yaboot put things in less than optimal spots

Well, the only curious thing is that it starts allocation at 48MB. But I suppose that's for a good reason - OFW and yaboot have to all fit into the same tiny 128MB address space after all.

Alex

--
To unsubscribe, e-mail: opensuse-ppc+***@opensuse.org
To contact the owner, e-mail: opensuse-ppc+***@opensuse.org

Benjamin Herrenschmidt

2014-01-02 21:26:35 UTC

Post by Alexander Graf
Well, the only curious thing is that it starts allocation at 48MB. But
I suppose that's for a good reason - OFW and yaboot have to all fit
into the same tiny 128MB address space after all.

Check where OFW is ... (real-base)

Cheers,
Ben.

--
To unsubscribe, e-mail: opensuse-ppc+***@opensuse.org
To contact the owner, e-mail: opensuse-ppc+***@opensuse.org

Andreas Färber

2014-01-07 13:40:49 UTC

Check where OFW is ... (real-base)

# hexdump -C options/real-base
00000000 33 33 35 35 34 34 33 32 00 |33554432.|
00000009
# hexdump -C options/real-size
00000000 31 36 37 37 37 32 31 36 00 |16777216.|
00000009

Looks slightly odd to me...

power5:/proc/device-tree # hexdump -C options/virt-base
00000000 34 32 39 34 39 36 37 32 39 35 00 |4294967295.|
0000000b
power5:/proc/device-tree # hexdump -C options/virt-size
00000000 34 32 39 34 39 36 37 32 39 35 00 |4294967295.|
0000000b

# hexdump -C options/load-base
00000000 31 36 33 38 34 00 |16384.|
00000006

Cheers,
Andreas

Alexander Graf

2014-01-07 13:43:15 UTC

Post by Andreas FÃ¤rber

Check where OFW is ... (real-base)

# hexdump -C options/real-base
00000000 33 33 35 35 34 34 33 32 00 |33554432.|
00000009

Post by Alexander Graf
33554432 / 1024. / 1024.

32.0

Post by Andreas FÃ¤rber
# hexdump -C options/real-size
00000000 31 36 37 37 37 32 31 36 00 |16777216.|
00000009

Post by Alexander Graf
16777216 / 1024. / 1024.

16.0

Post by Andreas FÃ¤rber
Looks slightly odd to me...
power5:/proc/device-tree # hexdump -C options/virt-base
00000000 34 32 39 34 39 36 37 32 39 35 00 |4294967295.|

Post by Alexander Graf
hex(4294967295)

'0xffffffff'

Post by Andreas FÃ¤rber
0000000b
power5:/proc/device-tree # hexdump -C options/virt-size
00000000 34 32 39 34 39 36 37 32 39 35 00 |4294967295.|

Post by Alexander Graf
hex(4294967295)

'0xffffffff'

Post by Andreas FÃ¤rber
0000000b
# hexdump -C options/load-base
00000000 31 36 33 38 34 00 |16384.|

Post by Alexander Graf
hex(16384)

'0x4000'

Alex

--
To unsubscribe, e-mail: opensuse-ppc+***@opensuse.org
To contact the owner, e-mail: opensuse-ppc+***@opensuse.org

Andreas Färber

2014-01-07 13:31:11 UTC

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.

Andreas, could you please dump /proc/device-tree from a working Linux instance and upload it somewhere

Transferred a tarball to my notebook.

Post by Alexander Graf
or at least tell us how big the RTAS payload is? :)

# cd /proc/device-tree
# hexdump rtas/rtas-size
0000000 0095 c000
0000004

=> RTAS is 9.814.016 bytes if I'm reading that correctly.

Post by Alexander Graf
So we have
48MB - ~71MB kernel
71MB - 120MB initrd
So yeah, I can see how there might be too little space left to put the RTAS blob somewhere. But why is yaboot only allocating as of 48MB?
Either way, I guess in your case the easiest solution would be to trim a few firmware blobs from the initrd. I don't think you have qlogic hbas in your system, right? :)

0001:d0:01.0 SCSI storage controller: Mylex Corporation AcceleRAID
600/500/400/Sapphire support Device (rev 04)