ACPI daemon, PowerMan, WinSendMsg

[Steven Levine]

Kernel debugging is relatively easy to set up:  See Michal's

  http://www.os2museum.com/wp/kernel-debugging-with-virtualbox/

Virtualbox also has it's own GUI debugger

  https://www.virtualbox.org/manual/ch12.html#ts_debugger

Although probably not all that useful for this endeavor, pmmerge implements a trace facility.

From my notes:

  Pmmerge implements the function.

    PMTrace(mask, force, requestlevel, filename, lineno, messsage)

      Formats and writes records to FFST and COM port depending on settings.

  Output is controlled by PM_DEBUG environment variable.

  Format is

    SET PM_DEBUG=gbllevel,level0,...level31

      Level values are 1 to 15
      Levels are limits
      Output occurs if request less than or equal limit

      gbllevel applies to all
      level0 applies if bit 0 set in mask, etc.

    Generally SET PM_DEBUG=15 is sufficient.

[Lars]

Hi Steve,

thanks for the hint. Unfortunately, using FFST seems to be not straightforward.
I have the necessary deamon running to support FFST and I tried to use "FFST Setup" to add PMMERGE to the "Probe Control Table" but I don't know what to enter for "Vendor Tag", "Tag","Revision","Prove Id" (I guess "Module" would be PMMERGE).
I can never see anything showing up in the "System Log".

Or does this only work with the old/outdated version of FFST (and not the one that comes with eCS/AN) ?

[Lars]

I now tried:
"Vendor Tag" = IBM-PSP
"Tag" = OS/2 PM Controls
"Revision" = 1.00
"Module" = PMMERGE.DLL
"Probe Id" = 1

but to no avail (those strings I found within PMMERGE.DLL, I guessed Probe Id). "Syslog" will not display anything. But maybe I am misunderstanding FFST.

[Steven Levine]

Hi Lars,

As I read the docs, you should not need to add a Probe Control Table entry. The table exists to allow the default behavior to be overridden without the need rebuild the binaries.  Without a PCT entry, the default behavior will apply.

Are you getting any syslog entries written?  If not, check that syslog is enabled (i.e. syslog /r).  I recently ran into a system where syslog was unexpectedly disabled.

If syslog is working and you are still not getting pmmerge syslog entries this may be working as expected.  While there are a large number of calls to PMTrace, all the calls I have seen are to report errors.  There are a couple of calls to FFSTProbe and these too are to report errors.

There are couple of DLLs (syslogd.dll and ffstapi.dll) which are supposed to implement REXX interfaces the FFST APIs, but I've not yet tracked down copies.  This would make building a testcase easier.

[Lars]

Hi Steve,

I myself had used "FFSTProbe" in the past (as part of a debug component) and that worked perfectly ok. I am not seeing any entries in syslog for PMMERGE even though I ran syslog /r.

I think you are right. PMMERGE seems to only write to the syslog for errors and not for debug purposes. Too bad.