OS2AHCI Tracing

OS2AHCI.ADD v.1.17 and later contains support for easy tracing which is very helpful (and often required) to diagnose problems. However, this procedure described here only works if the problem does not lead to a trap and occurs after the system is up and running. If this is not the case, follow the descriptions here.

To create a trace log, do the following:

• edit your config.sys and add the following parameters to os2ahci.add:

  BASEDEV=OS2AHCI.ADD /c:0 /d /d
  

  You can add up to three (at time of writing) /d's to increase verbosity. The /c:0 directs logging to the internal trace buffer.
• reboot machine
• prepare the session as far as possible before triggering the problem, i.e. if the problem occurs when starting a program from a console window, open a console window now.
• to start logging, enter the following into a command prompt window:

  type os2ahci$ > ahci.log
  

• do whatever you need to do to trigger the problem
• go back to the console where the type os2ahci$ command is running and hit Ctrl+C to stop logging
• include ahci.log in the bug report