To troubleshoot when an exception occurs during a test,
interpret the value in the cause register. Appendix E
describes the cause register.
Messages that do not include CUX or UEX describe
hardware errors detected by tests.
To troubleshoot when a test detects a hardware error, refer
to the next section, ‘‘Troubleshooting When a Test Reports
an Error.’’
How to Troubleshoot When a Test Reports an Error
Error messages that appear on the monitor have the form
?TFL
slot_number
/
test_name
(
description
)
slot_number
represents the slot number of the FRU that
reported the failure.
test_name
represents the name of the individual test that
failed.
description
represents a detailed description of the error.
If the slot number listed in an error message is 0, 1, or 2,
the
probable failed FRU is a TURBOchannel option module. Refer
to the
TURBOchannel Maintenance Guide
to troubleshoot.
If the slot number listed in an error message is 3,
the probable
failed FRU is in the base system hardware. The individual test
listed in the message is the test that reported the error.
Table 4-2 shows the corrective action indicated by each
error message for the base system hardware. For a detailed
explanation of these error messages, refer to the section in
Appendix D that discusses the individual test listed in the error
message.
Identifying Failed FRUs
4–15
Summary of Contents for DECstation 5000/100 Series
Page 20: ......
Page 24: ......
Page 36: ......
Page 55: ...LJ 02972 TI0 MLO 010159 Figure 2 10 System Boot ROM Switches Service Operations 2 19...
Page 140: ...LJ 02971 TI0 MLO 010159 Figure 5 7 50 MHz R4000 based CPU module 5 12 Base System FRUs...
Page 151: ...WS33M076 Figure 5 14 Removing a memory module Base System FRUs 5 23...
Page 153: ...WS33M075 Figure 5 15 Installing a memory module Base System FRUs 5 25...
Page 164: ......
Page 206: ......
Page 356: ......
Page 388: ......