A.l.2. Non-Critical Errors From Self Test - Sun Microsystems Sun Workstation 100U System Manager's Manual

Power-up and Bootstrap
Sun 100/150 Installation Manual
• With a Sun-1/100U, these LEDs can be glimpsed through the cooling slots on the left
side of the monitor base. If your screen remains dark, and you see more than one LED
on in the middle of some board in the card cage, you'll probably have to slide the
drawer out of your Sun-1/100U to really see the error code in the LEDs.
• With a Sun-l/150U or Sun-2/170, you can see the LEDs by opening the front door of
the card cage enclosure.
• With a Sun-2/120, pull off the front plastic panel of the pedestal; the row of 8 LEDs is
on the front edge of a card in the middle of the card cage.
When power is first applied to the workstation, all eight LEDs light, then each lights
quickly in sequence. Following this 'lamp test', the lights blink rapidly as each test is
passed. The lights slow down as memory is tested; each of the two memory tests takes a
few seconds per megabyte. Finally, three LEDs on the end light momentarily, then all the
LEDs go off except for a middle LED which blinks about once a second. If your worksta-
tion follows this sequence, self-test has not found a critical problem. (Once
UNIX
or other
programs have gained control of the system, they can use the LEDs in other ways. This
description only applies to the power-on
sequen~e.)
If at some point in the above sequence, the lights freeze (keep the same pattern for more
than a minute), or the sequence restarts from the beginning, there is a critical hardware
problem with the workstation. The appropriate thing to do in this case is to contact Sun
Microsystems Field Se"ice or your local Field Service organiza.tion. Copy down the pat-
tern of lights (as well as you can, if it is repeating over and over); they contain important
diagnostic information for Field Se"ice.
A.l.2. Non-Critical Errors trom Selt Test
Non-critical errors result in a display like the following:
Self Test found a problem in ,ometAing
Wrote wdtdo at address oddr, but read rdoto.
Damage found, damage,
-->
Give the above information to your se"ice-person
Sun Workstation, Model model_number, ,we_of_keyboard.
ROM Rev N, ,ome_number_MB memory installed
Serial *,ome_number, Ethernet address n:n:n:n:n:n
Auto-boot in progress ...
,ometAing shows what part of the system was most recently found to be malfunctioning.
(If more than one error occurs, a summary of all errors is given in the damage.
section, and details about the last error are reported here.)
wdoto
is the data that was written into part of the system, or which was expected to
be there if the system was functioning normally.
addr is the address where the data was read and/or written. For memory errors,
this is a physical memory address; for other errors, the interpretation of the
address depends on .ometA;ng.
rdoto is the data that was read back from oJdr and was found to be invalid because
it was not the same as wdata.
A-2 Revision H of
12
March
Ul84