
MultiPort/LT User Reference
Page 95
MultiPort/LT Gateway Code Commands
0x0010
PPHEAD
Controls p_printing in gw.c - obsolete
0x0020
PPALL
Likewise
0x0100
HIST
Enables history on Lance packets
0x1000
PANIC
Go to the MultiPort/LT gateway code
command mode after panic, else restart.
Note that the only useful one here is the PANIC flag. The rest of the flags aren't
listed here. Reference to the listing is required for their use.
3.4.
MultiPort/LT Gateway Code Panics
A "PANIC!" is a condition from which the MultiPort/LT gateway code cannot
recover cleanly. These are very infrequent but can be caused by severe
misconfiguration, hardware failure or corruptions in the the MultiPort/LT
gateway code program file. Other Panic messages are leftovers from the
MultiPort/LT gateway code debugging - they were put there to catch illegal
conditions.
After a PANIC, the MultiPort/LT gateway code will restart unless the "d1000"
flag is set. A Panic message appears:
PANIC! <message describing reason for panic>
trapsp 000000 from 000000 sr 0000
abregs[00..] 00000000 00000000 00000000 00000000
abregs[04..] 00000000 00000000 00000000 00000000
abregs[08..] 00000000 00000000 00000000 00000000
abregs[12..] 00000000 00000000 00000000 00000000
The CPU light on the front panel flashes red once during a Panic. If the Debug
Panic flag is set, the CPU light will flash green as an indication that the
MultiPort/LT is waiting for operator intervention.
Some of the possible panic messages are:
operator
Response to "P" command.
watchdog timer
The MultiPort/LT gateway code failed to run the idle process for
100 seconds.
EEprom partial xsum error
Hardware EEprom failed or corrupted.