Error log example
The first part of all error logs is similar to the
following example:
----- EVENT INFORMATION -----
EVENT CLASS
OPERATIONAL EVENT
OS EVENT TYPE
300.
SYSTEM STARTUP
SEQUENCE NUMBER
0.
OPERATING SYSTEM
ULTRIX 32
OCCURRED/LOGGED ON
Tue Oct 24 09:06:16 1989
OCCURRED ON SYSTEM
GRANITE
SYSTEM ID
x82020120
HW REV: x20
FW REV: x1
CPU TYPE: R4000
PROCESSOR TYPE
KN04/R4000
The fields of the first part of an error log, as shown in the
preceding example, are as follows:
EVENT CLASS lists the general category of the error log.
The two EVENT CLASS categories are operational events
and error events.
Operational events are changes in system operation
that are not errors.
Error events are actual errors in system operation.
OS EVENT TYPE describes the type of error or event
recorded in the log. Table 3-2 lists the operating system
event types and their codes.
SEQUENCE NUMBER lists the order in which the system
logged the event.
OPERATING SYSTEM lists the system’s version of
ULTRIX.
OCCURRED/LOGGED ON lists when the error occurred.
OCCURRED ON SYSTEM lists the individual system that
reported the error.
SYSTEM ID includes several listings:
The first number to the right of SYSTEM ID is the
system ID.
HW REV lists the system hardware revision number.
FW REV lists the system firmware revision number.
CPU TYPE lists the type of CPU used in the system.
Troubleshooting Tools
3–11
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: ......