Changes between Version 12 and Version 13 of Debugging Guide


Ignore:
Timestamp:
Feb 15, 2014, 11:27:51 PM (10 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Debugging Guide

    v12 v13  
    11= Debugging Guide =
    22
    3 If you open a ticket, additional information will almost always be necessary. The two most common things are a testlog log file and a formatted trace.  The testlog log file is always required unless your system traps or won't boot. You can save a lot of time by attaching the testlog log file to your ticket when you open it, rather than waiting for the developer to ask for it. Only attach a formatted trace file if the developer asks for it.
     3Things to check before opening a ticket if you have problems
     4* Make sure you are using the latest version of a supported driver. Official supported drivers are built by David Azarewicz and are available either on the main wiki page, or from the eCS !BetaZone. Any other builds from other sources are not supported.
     5* Make sure you are using an official supported IBM kernel. Only the official IBM 14.104a debug, 14.105 and 14.106 kernels are supported.
     6* Make sure you are using an official supported IBM loader that goes with the official IBM kernel you are using.
     7* If you have a PSD installed, make sure it is the latest version and that you are not using any unnecessary switches.
     8
     9If you open a ticket, please attach a testlog log file when you open your ticket. A formatted trace file is usually not necessary and is useless unless captured correctly at the correct time. Only attach a formatted trace file if the developer asks for it.
    410
    511If you cannot create a testlog log, at a minimum you must include the bldlevel output for the driver you are using.  Also, include the PCI Vendor ID and Device ID of your hardware in the ticket (ie. the section from PCI.EXE that relates to your NIC). If the driver traps, please, include the trap screen.