Changes between Version 1 and Version 2 of Troubleshooting


Ignore:
Timestamp:
Jul 18, 2013, 8:07:53 PM (12 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Troubleshooting

    v1 v2  
    77== Capturing A testlog log file ==
    88
    9 Download the testlog log file creator here
     9If you don't already have the current version of testlog.cmd, you can download it here: [http://88watts.net/download/testlog-2.05.zip testlog-2.05.zip]
    1010
    11 open a command window and execute the testlog command
     11Open a command window and execute the testlog command
    1212   {{{
    1313testlog usb
    … …  
    1717
    1818== Capturing a Startup Trace file ==
     19
    1920A startup trace file is for a problem that occurs on startup, rather than for a problem that occurs after the system has been running for a while.
    2021
    2122To create a startup trace file, do the following:
     23
     241) Add the following line to your config.sys:
     25{{{
     26  TRACEBUF=512 /M=NOWRAP,QUEUED,NODTI /D=ALL
     27}}}
     282) Add the appropriate "TRACE=ON <trace code>" line to your config.sys.
     29  For USBUHCD.SYS the trace code is 224
     30  For USBOHCD.SYS the trace code is 225
     31  For USBEHCD.SYS the trace code is 226
     32  For example, to trace the USBEHCD.SYS driver you would add the following line:
     33{{{
     34  TRACE=ON 226
     35}}}
     36  To trace both the USBEHCD.SYS driver and the USBUHCD.SYS driver, you would
     37  add the following line:
     38{{{
     39  TRACE=ON 224,226
     40}}}
     41  To trace both the USBEHCD.SYS driver and the USBOHCD.SYS driver, you would
     42  add the following line:
     43{{{
     44  TRACE=ON 225,226
     45}}}
     46
     473) Reboot to enable tracing.
     48
     494) To capture the trace dump, open a command window and type:
     50{{{
     51   TRACEFMT
     52}}}
     53From the file menu choose Save Formatted... and save the trace to a file of your choice.
     54
     555) Attach file you created to your ticket.
    2256
    2357== Capturing a Runtime Trace file ==
    … …  
    2761To create a runtime trace file, do the following:
    2862
     631) Add the following line to your config.sys:
     64{{{
     65  TRACEBUF=512 /M=WRAP,QUEUED,NODTI /D=ALL
     66}}}
     672) Add the appropriate "TRACE=ON <trace code>" line to your config.sys.
     68  For USBUHCD.SYS the trace code is 224
     69  For USBOHCD.SYS the trace code is 225
     70  For USBEHCD.SYS the trace code is 226
     71  For example, to trace the USBEHCD.SYS driver you would add the following line:
     72{{{
     73  TRACE=ON 226
     74}}}
     75  To trace both the USBEHCD.SYS driver and the USBUHCD.SYS driver, you would
     76  add the following line:
     77{{{
     78  TRACE=ON 224,226
     79}}}
     80  To trace both the USBEHCD.SYS driver and the USBOHCD.SYS driver, you would
     81  add the following line:
     82{{{
     83  TRACE=ON 225,226
     84}}}
     85
     863) Reboot to enable tracing.
     87
     884) To capture the trace dump, open a command window and type:
     89{{{
     90   TRACEFMT
     91}}}
     92From the file menu choose Save Formatted... and save the trace to a file of your choice.
     93
     945) Attach file you created to your ticket.
     95
    2996== Creating a Trap Dump ==
    3097