Sun Netra 1280 Server
 
Sun Fire 6800 Server
 
Sun Fire E2900 Server
 
Sun Fire 3800 Server
 
Sun Fire 4810 Server
 
Sun Fire V1280 Server
 
Sun Fire 4800 Server
 
Sun Fire E4900 Server
 
Sun Fire E6900 Server
 
Sun Netra 1290 Server
 

PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Exx00
 
_Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
 

Applies to:

Goal

When OBP encounters an error during the boot sequence, 'LED write value'
messages may appear along with error messages.
Here is an example of an 'LED write value' message.

Solution

The 'LED write value' message is only for debugging purposes and has nothing to do with actual hardware LEDs.

This message is somewhat misleading and may lead to unnecessary FRU replacement.
The value in the message indicates where the OBP encountered the error.

Do not replace any HW for such errors.


This can be decoded as follows. It actually is shown twice in different
formats (hexadecimal and decimal).
The meaning of each LED value is as follows:

0x1 Environment setup
0x2 Interpretation of nvramrc
0x3 Execution of probe-all
0x41 Installation of failsafe console device
0x42 Installation of default console device
0x4 Installation of console device specified by OBP variables
0x5 Execution of banner

0x1 Environment setup
This is an early stage where OBP allocates memory and initializes variables.
If you see this LED value you may have encountered a memory-related problem.

0x2 Interpretation of nvramrc
At this stage OBP interprets and executes the contents of nvramrc. If OBP
encounters an error while interpreting and executing the contents of nvramrc,
you will see this LED value along with error messages related to nvramrc.
One possible cause is a typo in contents of nvramrc, which leads to an
'undefined word' error.
Here is an example of this LED value. In this case a devalias line is
wrongly quoted with a double quote character.
ERROR: do_interpret: no such symbol ""devalias"
ERROR: undefined word
LED write value = 0x2, 2

0x3 Execution of probe-all
At this stage OBP probes all the hardware in the domain and performs
appropriate initialization. It also creates a device node for each device
in the domain and places it in the device tree at the appropriate places.
If OBP encounters an error while probing a device you will see this LED
value along with error messages related to the probe of the device.

0x41 Installation of failsafe console device
At this stage OBP sets up console I/O with failsafe driver as a fall-back
in case the specified console cannot be opened at boot time. The failsafe
console driver actually relies on the sgcn driver's I/O interface for the Sun
Fire midrange platform. It is unlikely you will see this LED value.

0x42 Installation of default console device
At this stage OBP installs the default console driver specified by the device
alias 'def-cn' which turns to be sgcn for Sun Fire midrange platform. It is
unlikely you will see this LED value.

0x4 Installation of console device specified by OBP variables
At this stage OBP sets up console I/O by using the devices specified by the
OBP variables 'input-device' and 'output-device'. If OBP encounters an
error at this stage you will see this LED value along with error messages
relating to the devices specified as console.
The most common cause of this LED value is that a wrong device is
specified as input-device and/or output-device. For the Sun Fire midrange
platform, both input-device and output-device should be set to '/sgcn'.
For example, if they are set to 'ttya'as it is on Sun Enterprise
Servers the following error will be displayed:
install-console ERROR: no such device
LED write value = 0x4, 4

0x5 Execution of banner
At this stage OBP displays banner information. This LED value is defined
however you cannot actually see it because the banner function does not
return any error to the caller.

This solution has no attachment