Sun Microsystems 2500 manual Manual

TABLE 4-1Troubleshooting Procedures (Continued)

SymptomTroubleshooting

Hung or frozen workstation: No response from mouse or keyboard or any application.

1.Try to access your system from a different workstation on the network.

2.From a terminal window type: ping hostname

3.If no response, remotely log in from another system using telnet or rlogin, and ping the system again.

4.Attempt to kill processes until the system responds. (See the procedures for “Hung Application” in this table.)

If the above procedures do not work:

Caution: Only experienced system administrators should use a “Stop” command. Using any “Stop” command might cause loss of core dumps, which makes it difficult to diagnose system problems.

1.Press Stop-A. If the system responds, the system displays the ok prompt.

2.Try to force a core file dump. At the ok prompt, type this command: sync

Note: The default location for a core file deposit is: /var/crash/hostname

The Sun Service Support Center might request the core file for root cause analysis.

If the above procedures do not work:

1.Press the Power button to power off the system.

2.Wait 20 to 30 seconds and power on the system.

Note: When you power on the system again, you might need to run fsck to repair damaged links. If the system still does not function properly, contact Sun Service Support.

For more troubleshooting information see the Sun Blade 2500 Service, Diagnostics, and Troubleshooting

Manual (817-5117).

Chapter 4 Troubleshooting and Technical Support 39