IBM Support

"Could not allocate memory for RTAS" before GRUB or YABOOT on PPCBE

Troubleshooting


Problem

During reboot of a Linux partition, A failure might occur during reboot or installation of a Linux partition indicating:

Could not allocate memory for RTAS

Or

No memory for flatten_device_tree (no room)

This failure can also occur after switching kernels.

Symptom

The following output can be seen on the console of the partition, with the key messages being shown at the end:

Elapsed time since release of system processors: 45 mins 32 secs
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.10.0-514.el7.ppc64 (mockbuild@ppc-021.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:30:41 EDT 2016
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/vmlinuz-0-rescue-5b44b8e692ad4502afd3021524129f10 root=UUID=2eaa3129-c2b7-4775-b09a-2d6c3c8c4cbe ro crashkernel=auto
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 000000000ee50000
alloc_top : 0000000010000000
alloc_top_hi : 0000000010000000
rmo_top : 0000000010000000
ram_top : 0000000010000000
Could not allocate memory for RTAS
EXIT called ok
0 >

Cause

Memory fragmentation can prevent the load of modules needed by the boot loader or the OS.  This error can prevent the boot loader menu from being displayed.

Environment

This document could apply to all Power PC POWER7, POWER8, or POWER9 Linux® installations.

Diagnosing The Problem

1.  Validate that the error being seen is a match to this document.

Elapsed time since release of system processors: 45 mins 32 secs
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.10.0-514.el7.ppc64 (mockbuild@ppc-021.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:30:41 EDT 2016
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/vmlinuz-0-rescue-5b44b8e692ad4502afd3021524129f10 root=UUID=2eaa3129-c2b7-4775-b09a-2d6c3c8c4cbe ro crashkernel=auto
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 000000000ee50000
alloc_top : 0000000010000000
alloc_top_hi : 0000000010000000
rmo_top : 0000000010000000
ram_top : 0000000010000000
Could not allocate memory for RTAS
EXIT called ok
0 >

Verify that the statement "Could not allocate memory for RTAS" is present.

  • Record the range of text from the failing server partition.
  • Enter the command "printenv" and record the output. This command provides information on the server partition non-volatile storage variables.
  • Enter the command "dev /memory@0", then enter the command ".properties" (noticing the period ahead of the command properties), and record the output. This command provides information on the memory layout that is present.

Resolving The Problem

1.  Attempt to clear partition NVRAM to recover.

  • Enter "reset-all" to reset the partition.
  • Watch for the boot options banner screen and enter "8" to request stop at Open Firmware prompt. (Note, it is different than the prompt seen).
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
 
1 = SMS Menu 5 = Default Boot List
8 = Open Firmware Prompt 6 = Stored Boot List
  • Enter the following in order at the Open Firmware prompt:
    (1) dev nvram
    (2) wipe-nvram

The output looks like the following when entered:
0 > dev nvram ok
0 > wipe-nvram 

Rebooting partition now to rebuild partition's NVRAM...

If the partition reboots now, the partition environment NVRAM is rebuilt. If there were changes to the partition NVRAM done by the user, they can need to be done again. If the partition fails to reboot and fails with the same symptom, proceed to the next step.

2.  If the same failure re-occurs, then attempt to re-create the partition again.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"HW1A1","label":"IBM Power Systems"},"Component":"GRUB","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"HW1A1","label":"IBM Power Systems"},"Component":"GRUB","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGDMMD","label":"Power System AC922 Server (8335-GTC)"},"Component":"GRUB","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STHMCM","label":"IBM Elastic Storage Server"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
07 December 2021

UID

ibm10732319

Page Feedback