Digital Equipment DECstation 5000/100 Series, Maintenance Manual

Page: 98 / 392

Example: R3000 Console exception message
This is a sample
R3000 console exception message:
? PC: 0x451<vtr=nrml>
? CR: 0x810<ce=0,ip4,exc=AdEL>
? SR: 0x30030000<cu1,cu0,cm,ipl=8>
? VA: 0x451
? ER: 0x100003f0
? MER: 0x2000
The last term in the second line is the exception code, ("exc=")
The exception code describes what type of exception occurred.
If the exception code is MOD, TLBL, or TLBS , an address used
in a console command was probably invalid. The value that
follows
? VA
is the virtual address that caused the exception.
To correct the exception, always use addresses 80000000 to
9fffffff or a0000000 to bfffffff only.
If the exception code is AdEL or AdES , a console command
probably attempted access on a boundary that was not a word.
The
? VA
value is the virtual address used in the console
command. To correct these types of exceptions,
1.
Retry the command with an address that starts on a word
boundary.
2.
If access still fails, turn the system unit power off and then
on again to restart console mode.
3.
If an exception still occurs, type test and press Return.
Interpret any errors that the test script reports to isolate
the problem hardware.
If the exception code is IBE or DBE , a bus error occurred. The
bus error is either a memory error or a timeout.
If MER bits 16, 15, and 11 through 8 are clear, a timeout
occurred.
If MER bits 16, 15, or 11 through 8 are set, a memory error
occurred.
If a timeout occurred , use the following procedure:
1.
Find the number that follows
? ER
in the messsage. This is
the address where the exception occurred.
4–20 Identifying Failed FRUs