SCO OpenServer Enterprise System Release 5.0.0, 5.0.2, 5.0.4, 5.0.5, 5.0.6, 
5.0.7 
          SCO OpenServer Host System Release 5.0.0, 5.0.2, 5.0.4, 5.0.5, 5.0.6, 
5.0.7 
          SCO OpenServer Desktop System Release 5.0.0, 5.0.2, 5.0.4, 5.0.5, 
5.0.6, 5.0.7 
          SCO OpenServer Internet FastStart Release 5.0.4 
          SCO Internet FastStart Release 1.0.0, 1.1.0 

          I have an SCO OpenServer 5.0.x system that is experiencing panics
          (crashes) and/or hangs.  What information needs to be gathered to
          assist with determining the cause of the problem?

          What follows is not a full list of items. There will be more
          information that may need to be gathered (on a case-by-case basis)
          but the following can serve as a starting point:

          - Has anything (software, hardware, configuration) changed
          between the time the system was running fine and the time it
          started to panic or hang?

          - Is the panic and/or hang random or can it be re-created by
          following a series of steps?

          - What is the make and model of the computer?

          - A hardware listing:

              # /etc/hwconfig -hc > /tmp/hwconfig.txt

          - On OpenServer 5.0.4 and 5.0.5 systems (this command is
            not on 5.0.0 and 5.0.2 systems):

              # /etc/hw -v > /tmp/hw.txt

          - A software listing:

              # /usr/bin/swconfig > /tmp/swconfig.txt

          - Any errors or warning messages that are appearing on the screen.

          - Any error/warning messages in the following files:

              # /usr/adm/messages
              # /usr/adm/syslog

          When the system panics, save the dump (if one is created) and
          then run the crash utility against it, then send in the output
          text file.  For information on saving a crash dump and running the
          crash utility against it, see Technical Article 105619, "Panic/Crash Analysis if a
          dump is available."

          For best results, gather 3 crash dumps and run the crash utility
          against each one.  Then compare them to see if a consistent reason
          for a system crashing can be determined.

          As a standard set of steps, check the filesystem integrity and
          check for discrepancies within the operating system.  To check the
          filesystem integrity, perform the following commands in single user
          mode (for a more thorough explanation of this process, see Technical Article 105411
          "Filesystem Repair Utilities for SCO OpenServer 5.0.0, 5.0.2, and
          5.0.4."):

          IMPORTANT: The following needs to be done in single-user mode.

              # /etc/fsck -ofull    <Enter>
              # /tcb/bin/integrity -em > /tmp/integ.rpt    <Enter>
              # /etc/tcbck    <Enter>
              # /tcb/bin/authck -a -v    <Enter>
              # /etc/fixmog -v    <Enter>

          Once you have completed the above, check the operating system
          for discrepancies:

              # /etc/custom

          Once the Software Manager (custom) has started, select "Software"
          -> "Verify System" -> "Normal System State (Thorough) and
          then "Continue".

          After the software has been checked you will likely be prompted
          to fix some discrepancies that were found.  A system restart is
          not necessary after this step. However, if you have scripts that
          did not start due to file permission problems and so on, and
          they were corrected by the System Verification, it would be
          advisable to shut down and restart the system.

          Technical Article 105619, "Panic/Crash Analysis if a dump is available."

          Technical Article 105411, "Filesystem Repair Utilities for SCO OpenServer 5.0.0,
          5.0.2 and 5.0.4"