Topic
  • 3 replies
  • Latest Post - ‏2013-02-06T01:24:10Z by andrew_l
andrew_l
andrew_l
2 Posts

Pinned topic System fails to load boot order and gets error Base of Data Stack corrupted!!! Restored deadbeef.

‏2013-01-30T15:08:10Z |
 Hey guys,
I manage a lot of ppc systems and this is a new error message for me. I have already restored all the factory settings back to factory and can't seem to get any where with this. Might it be possible that this server has bad hardware? This system is a ppc64 blade with no lpars
Here is the output I get
 
   Memory      Keyboard     Network     SCSI     Speaker
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 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 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 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 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 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 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 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 IBM IBM     STARTING SOFTWARE       IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM        PLEASE WAIT...       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 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 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 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 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 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
\
Base of Data Stack corrupted!!! Restored deadbeef.
Call History
------------
get-first-header  - a63590
find-part  - a63a64
get-part  - a63afc
shrink-variable-partitions  - a64a8c
(poplocals)  - a3c9e8
purge-net-parameter-settings  - a64cb8
(poplocals)  - a3c9e8
add2part  - a64e64
(poplocals)  - a3c9e8
maybe-expand-common  - a65164
(poplocals)  - a3c9e8
go  - a85e9c
boot  - a863f0
evaluate  - a4c66c
invalid pointer - e44b95
invalid pointer - 15
invalid pointer - 15
catch  - a3aff0
attempt-sequence  - bca0ec
(poplocals)  - a3c9e8
Continue with execution (c), Abort execution (a), or Pseudo-prompt (p) ?:

 0 > boot network2 Unable to use memory at load-base
Call History
------------
throw  - a3b044
$abort  - a46d20
map-load-addr  - a840f4
$load  - a84534
(poplocals)  - a3c9e8
(load)  - a84d20
boot|load  - a85ce8
boot  - a863cc
evaluate  - a4c66c
invalid pointer - e44945
invalid pointer - 7
invalid pointer - 7
quit  - a4cd4c
quit  - a4cb40

My Fix Pt Regs:
 00 0000000000000000 0000000000000000 00000000deadbeef 0000000000a46d1c
 04 0000000000000021 0000000000a840cd 0000000000a13f58 0000000000a05010
 08 0000000010000000 6000000000000000 0000000000000001 0000000000000000
 0c 80003fbff9004000 0000000000a19100 0000000000a1a000 0000000001ac6d68
 10 0000000000ec5d60 0000000000ec5d08 0000000000a46d14 0000000000a46d20
 14 fffffffffffffffe 0000000000004000 0000000000000000 0000000000000000
 18 0000000000a15000 0000000000a3a000 0000000000a16fc0 0000000000a18fc0
 1c 0000000000a22000 0000000000a420e8 0000000000a13f90 0000000000a12ff8
Special Regs:
    %IV: 00000900     %CR: 82808002    %XER: 20000010  %DSISR: 00000000
  %SRR0: 0000000000a40ea8   %SRR1: 800000000000b002
    %LR: 0000000000a488a8    %CTR: 0000000000000004
   %DAR: 0000000000000000
 ok
0 > printenv
-------------- Partition: of-config -------- Signature: 0x50 ---------------
ibm,fw-dc-select         100                 0
ibm,fw-default-mac-address? false            false
ibm,fw-forced-boot                         
ibm,fw-n-bc              255.255.255.255     255.255.255.255
ibm,fw-n-dbfp            00000000            00000000
ibm,fw-n-dafp            00000000            00000000
ibm,fw-n-rc              A                   A
ibm,fw-n-ru              Y                   Y
-------------- Partition: common -------- Signature: 0x70 ---------------
little-endian?           false               false
real-mode?               true                true
auto-boot?               true                true
diag-switch?             false               false
fcode-debug?             true                true
oem-banner?              false               false
oem-logo?                false               false
use-nvramrc?             true                false
ibm,fw-tty-language      1                   1
ibm,fw-new-mem-def       true                true
ibm,fw-show-true-pcie?   false               false
ibm,fw-force-ior         false               false
ibm,fw-oflite-dbg        false               false
ibm,fw-prev-boot-vpd     00000000: 08 06 07 07 07 ff 07 07 07 07 07 07 07 07 07 07  |................|
                                           
ibm,fw-keyboard          1                   1
ibm,fw-override-cas      false               false
ibm,fw-nbr-reboots       0                   0
real-base                a00000              a00000
virt-base                ffffffff            ffffffff
real-size                1000000             1000000
virt-size                ffffffff            ffffffff
load-base                4000                4000
screen-#columns          64                  64
screen-#rows             28                  28
selftest-#megs           0                   0
boot-device              /pci@800000020000208/pci1014,02BD@1/sas/disk@20000 network1:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 network:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
boot-file                                  
diag-device              /pci@800000020000208/pci1014,02BD@1/sas/disk@20000 network1:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512 network:speed=auto,duplex=auto,000.000.000.000,,000.000.000.000,000.000.000.000,5,5,000.000.000.000,512
diag-file                diag                diag
output-device            /vdevice/vty        /vdevice/vty
input-device             /vdevice/vty        /vdevice/vty
oem-banner                                 
oem-logo
 
Any help would be great thanks
Updated on 2013-02-06T01:24:10Z at 2013-02-06T01:24:10Z by andrew_l
  • Storix
    Storix
    9 Posts

    Re: System fails to load boot order and gets error Base of Data Stack corrupted!!! Restored deadbeef.

    ‏2013-02-04T20:51:35Z  
    We have seen similar errors when the size of the boot image is too large for the Open Firmware to support.

    To resolve this go to the Open Firmware prompt and change the "real-base" size:

    0 > setenv real-base 2000000
    0 > reset-all

    The system will reboot with the new "real-base" size.

    To display the value of "real-base":

    0 > printenv real-base

    *Note depending on the kernel that is being booted, "real-base" may need to be adjusted larger or smaller.
     
    Give this a shot. This may resolve the issue. We have seen this before in our development.
  • willschm
    willschm
    47 Posts

    Re: System fails to load boot order and gets error Base of Data Stack corrupted!!! Restored deadbeef.

    ‏2013-02-04T21:14:15Z  
    Hi,  

    Was the system working before?  if so, any feel for what change may have introduced the problem?
     
    >  I have already restored all the factory settings back to factory ...
    Resetting factory settings (via service processor) may not include wiping the associated OFW settings for the fullsystem lpar...   Try resetting nvram if you have not already:
    When the "Memory Keyboard Network ...." message is being displayed, press '8' for Open Firmware Prompt.
    and from the 0> prompt,  type 
       dev nvram 
       wipe-nvram 
     
    FW should then reboot with a clean slate.  Fingers crossed, it will 'just work'. 
     
    If not..  
     
    >>  0 > boot network2 Unable to use memory at load-base
    Once I see firmware throw an error message, i usually do not trust anything else to function.  :-)
    I'd recommend a 'reset-all' from the OFW prompt (this triggers a firmware restart), and then using '1'=SMS or '8'=OFW during the boot and attempting a network boot directly from SMS or the OFW prompt, before it tries (and fails) to boot from disk. 
     
     
     
  • andrew_l
    andrew_l
    2 Posts

    Re: System fails to load boot order and gets error Base of Data Stack corrupted!!! Restored deadbeef.

    ‏2013-02-06T01:24:10Z  
    • willschm
    • ‏2013-02-04T21:14:15Z
    Hi,  

    Was the system working before?  if so, any feel for what change may have introduced the problem?
     
    >  I have already restored all the factory settings back to factory ...
    Resetting factory settings (via service processor) may not include wiping the associated OFW settings for the fullsystem lpar...   Try resetting nvram if you have not already:
    When the "Memory Keyboard Network ...." message is being displayed, press '8' for Open Firmware Prompt.
    and from the 0> prompt,  type 
       dev nvram 
       wipe-nvram 
     
    FW should then reboot with a clean slate.  Fingers crossed, it will 'just work'. 
     
    If not..  
     
    >>  0 > boot network2 Unable to use memory at load-base
    Once I see firmware throw an error message, i usually do not trust anything else to function.  :-)
    I'd recommend a 'reset-all' from the OFW prompt (this triggers a firmware restart), and then using '1'=SMS or '8'=OFW during the boot and attempting a network boot directly from SMS or the OFW prompt, before it tries (and fails) to boot from disk. 
     
     
     
     willschm,
     
    That fixed it thanks again, So it looked like the nvram got really corrupt. Now I know what to do in the future