TABLE OF CONTENTS System hangs are among the most frustrating problems for a system administrator. Unlike a system panic, there is little or no immediate evidence to guide troubleshooting efforts. The focus shifts to determining what the system is doing and why it is not responding in the expected manner, and then determining the appropriate course of action to resolve the problem. In most cases, it's not possible to recover from a hang cleanly or even to gather much information while the system is hung. A reboot is usually required to alleviate the hung condition. Unfortunately, this destroys the "live" evidence on the system, making troubleshooting more difficult. Some evidence can be preserved by forcing a crash dump before rebooting the system. The resulting crash dump files contain the contents of physical memory at the time of the hang, providing a snapshot of conditions at that instant.
Not all hangs are created equal. From a user's point of view, a hang can be any condition in which the system is not responding. This could be caused by an application not responding, a network connection problem, or a system that is truly hung (i.e., not executing at all). Users tend to be an impatient lot; a system or application that is actually responding very slowly may be reported to be hung. As such, the first step in troubleshooting a hang is to determine the severity of the hang, a process that is discussed in section 5.3.1.
Most hangs are not cleanly...
