System Crashes in AIX 3.2


Contents

About this document
Getting the LED codes
Locate the dump
Submitting the testcase
Forcing a system dump

About this document

This document describes the steps necessary for collecting and sending system dumps in AIX 3.2. The final section of the document provides information on how to force a dump.


Getting the LED codes

Following are the steps to obtain the LED codes.

  1. Turn the key to service mode.
  2. Wait for 888 to flash.
  3. Write down LED each time Reset is pressed until 888 is displayed again. These LED codes will be required during phone contact with AIX support personnel.
  4. Power the system off and then back on. Proceed with the next section.

Locate the dump

To locate the dump issue the command:

    sysdumpdev -L 

Check the sysdumpdev -L output for a valid time-stamp. If the time-stamp matches an approximate time of the system crash, proceed to the next section. If the time-stamp does not match OR the sysdumpdev command does not result in any output, a valid dump was not captured at this time. The section, "Forcing a system dump" provides more detailed information and steps to follow for this situation.


Submitting the testcase

Decide which method will be used to send the testcase.

NOTE: Overnight and Internet submissions are recommended. VM is not a preferred shipment method.


Overnight/US Mail

The steps to send a testcase via overnight or standard mail are listed below. In the following instructions, replace /dev/rmt# with the device name for your tape drive (usually /dev/rmt0).
  1. Run the snap command to collect required files.

    To gather all of the dump including kernel and general information, run the command:

        snap -gfkD -o /dev/rmt# 
    
  2. Verify that the information is on the media.

    Use the following commands to verify that the media contain the appropriate files which are necessary to analyze a system crash/hang:

        tctl -f  /dev/rmt# rewind 
        tar -tvf /dev/rmt# 
    

    Following are the required files:

        -rw-r--r--   1 4530888 Jul 02 16:12 dump.Z 
        -rw-r--r--   1     180 Jul 02 16:11 dump.snap 
        -rw-r--r--   1 1270849 Jul 02 16:11 unix.Z 
    

    NOTE: The file dump.Z may be just dump, and the file unix.Z may be just unix. These files should also be greater than 0 in size. In this case, dump.Z = 453088 bytes and unix.Z = 1270849 bytes.

  3. Label the tape with the following information:
        <customer name> 
        <pmr #, branch #> 
         tape block_size = xxx 
        <the command used to copy the information to tape> 
    

    IMPORTANT: If the person sending in this testcase is not the person who reported the problem, be sure to include the name of the person who reported it. If the proper information is not on the package, process delays will occur.

    Acceptable tape media are 8mm, 4mm or 1/4" QIC tape.

  4. Send the media via standard mail or overnight delivery to:

    NOTE: This address may change, so please verify this address by either obtaining the latest version of this document or verifying with your IBM software support organization.

    IBM Corp. / Zip 2900 / Bldg 42
    Attn: AIX Testcase Dept. J66S
    11400 Burnet Road
    Austin, TX 78758-3493
    Extension 3-4101

    If you specify Saturday delivery you must first make special arrangements with an AIX Support specialist (1-800-225-5249 or 1-800-call-aix); otherwise there could be a delay of several days.

Internet (ftp)

If you are sending the testcase by ftp, proceed with the following steps:
  1. Create a compressed tar image of the testcase. Run:
        snap -gfkD -c 
    

    This will create a file called snap.tar.Z in the /tmp/ibmsupt directory.

  2. Verify that the compressed file contains at least the following files to analyze a system crash/hang:
        zcat /tmp/ibmsupt/snap.tar.Z | tar -tvf - 
    

    In the output there should be three lines similar to the following:

     -rw-r--r--   1 user    group   36243456 Feb 20 10:05 dump.Z 
     -rw-r--r--   1 user    group        176 Feb 20 15:13 dump.snap 
     -rw-r--r--   1 user    group     933536 Feb 20 15:13 unix.Z 
    

    NOTE: The file dump.Z may be just dump, and the file unix.Z may be just unix. These files should also be greater than 0 in size. In this case, dump.Z = 453088 bytes and unix.Z = 1270849 bytes.

  3. Sample file names for the tarred and compressed file follow:
    ad1000.tar.Z                   (item number.tar.Z)
    1x234.001.tar.Z             (problem_report_#.branch_office_#.tar.Z)
    1x234.1234567.tar.Z     (problem_report_#.customer_#.tar.Z)
     
  4. Follow these steps to ftp the file to the testcase repository:
    1. Enter ftp 198.17.57.67 (or ftp testcase.boulder.ibm.com).
    2. At the login prompt enter anonymous.
    3. At the password enter your complete email address following the formate customer@company.com.
    4. Change to binary transfer mode. Enter bin.
    5. Change into the aix directory. Enter cd aix.
    6. Use the put command to place the file. For example, put 1x234.001.tar.Z .
    7. Enter ls -l to ensure the file lists in the contents of the directory.
    8. Enter quit.

Forcing a system dump

NOTE: Do not initiate a system dump if 888 is shown on the LED display. 888 means the system has automatically initiated a system dump. If another system dump is initiated while 888 is displayed, the information in the primary dump device will be overwritten. If the system dumped automatically, go to the section "Locate the dump" earlier in this document.

If the system has not dumped automatically, choose one of the two methods below to force a system dump. Notice one of the methods only works with certain configurations.

At this point, power off/on the system and go to the section "Locate the dump" of this document.


System Crashes in AIX 3.2: howto.dump.32.cmd ITEM: FAX
Dated: 99/06/21~00:00 Category: cmd
This HTML file was generated 99/06/24~12:42:07
Comments or suggestions? Contact us