HP Model 745 - VME Workstation Owner's Manual page 163

If the problem reappears on the device or if the hardware failure appears to
be associated with an interface card or an internal component of the system
module, you should refer the problem to your HP service representative.
Proceed to Step 3, Rebooting Your System|.
Step 2b: Recovering from a File System Problem
If the panic message indicates a problem with one of your file systems, you
will need to run the file system checker fsck to check and correct the prob-
lem(s). This is normally done automatically at boot time (from the /etc/rc
file) so you should proceed to Step 4 (Rebooting Your System). Follow all
directions that fsck gives you especially if it is your root file system (the one
with the "/" directory) that has the problem. It is important to use the "-n"
(HP-UX) option to the reboot command if requested to do so by fsck during
any subsequent reboot.
Step 2c: Recovering from a LAN Communication Problem
If the panic messages indicates a problem with LAN communication (such
as when a diskless cluster client node is prevented from communication for
too long), check all LAN cable connections to ensure the following:
• All connectors are tightly fastened to the LAN cable and the media access
units (MAUs).
• LAN is assembled correctly and does not exceed recommended lengths.
If you use an AUI, the LAN must be connected directly to the MAU with
no intervening length of cable between the MAU on your board computer
and the LAN tee.
• Your LAN is properly terminated.
Proceed to Step 3, Rebooting Your System.
Step 2d: Recovering from Other Situations
When you suspect the problem was something other than the above (or when
you do not know where to classify it), proceed to Step 3, Rebooting Your
System. In this case, it is especially important that you write down the exact
text of the panic message, just in case you need it for future troubleshooting
or help from HP service personnel.
Dealing With Problems
Recovering from a System Panic
9-9