4 using the persistent memory feature – Artesyn MVME2502 Installation and Use (April 2015) User Manual
Page 139

Boot System
MVME2502 Installation and Use (6806800R96E)
139
setenv ipaddr <IP address of MVME2502>
setenv serverip <IP address of TFTP server>
setenv gatewayip <gateway IP>
setenv netmask <netmask>
setenv vxboot 'tftpboot $vxbootfile && setenv bootargs
$vxbootargs && bootvx'
setenv vxbootfile <VxWorks_image>
setenv vxbootargs 'motetsec(0,0)<IP address of TFTP
server>:VxWorks h=<IP address of TFTP server> e=<IP address of
MVME2502>:ffffff00 b=<unused IP> u=vxworks pw=vxworks f=0x80'
saveenv
3. TFTP the files from the server to local memory, then boot:
run vxboot
6.4
Using the Persistent Memory Feature
The persistent memory means that the RAM's memory is not deleted during a reset. Power
cycling, or by temporarily removing the power and then powering up the blade again, will
delete the memory content. The persistent memory feature is enabled by default.
This feature is used in many situations, which includes:
Analyzing kernel logs after a Linux kernel panic
Defining a particular memory region for the persistent storage of application specific data
Analyzing Kernel Log Files after a Kernel Panic
When a board that is running the Linux OS indicates a kernel panic, issue a reset (for example,
through the faceplate button) to analyze the cause, then subsequently analyze kernel log files.
The persistent memory feature keeps the log files available in the memory.
To analyze the kernel log files:
1. Issue a reset.
2. Connect to U-Boot. For more information, see
3. Enter the following command to obtain memory addresses of the kernel log
files:.locate_kernel_log (1)
- MVME2502 Installation and Use (August 2014) MVME2500 Installation and Use Manual (February 2014) MVME2500 ECC Installation and Use (August 2014) MVME2500 Installation and Use (April 2015) MVME2500 Installation and Use Manual (March 2015) MVME2502 Installation and Use (April 2014) MVME2502 Installation and Use (December 2014)