Jump to content

ACPIDebug.kext and _PTS logging.


Kuebeker
 Share

2 posts in this topic

Recommended Posts

Hi 

 

I added the following to _PTS

        \RMDT.PUSH("Entering _PTS")
        \RMDT.P2("Arg0 = ", Arg0)
and to _WAK
        \RMDT.PUSH("Entering _WAK")
        \RMDT.P2("Arg0 = ", Arg0)
 
 

When I wake the system from sleep the _PTS gets logged at the same time as _WAK. 

I thought that _PTS gets called before the system goes to sleep, or is it that _PST gets logged on file only after the system wakes up? 

2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb83ecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb3becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f28becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f2cbecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering _PTS"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "_PTS Arg0 = ", 0x3, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering PTS"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "PTS Arg0 = ", 0x3, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb3becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb83ecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f2cbecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f28becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering _WAK"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "_WAK Arg0 = ", 0xffffff7f808d4c50, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering WAK"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "WAK Arg0 = ", 0x808d4c50, }

Link to comment
Share on other sites

 

Hi 

 

I added the following to _PTS

        \RMDT.PUSH("Entering _PTS")
        \RMDT.P2("Arg0 = ", Arg0)
and to _WAK
        \RMDT.PUSH("Entering _WAK")
        \RMDT.P2("Arg0 = ", Arg0)
 
 

When I wake the system from sleep the _PTS gets logged at the same time as _WAK. 

I thought that _PTS gets called before the system goes to sleep, or is it that _PST gets logged on file only after the system wakes up? 

2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb83ecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb3becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f28becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f2cbecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering _PTS"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "_PTS Arg0 = ", 0x3, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering PTS"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "PTS Arg0 = ", 0x3, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb3becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807eb83ecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f2cbecc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug::message(-536707056, 0xffffff800a818f00, 0xffffff807f28becc)
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering _WAK"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "_WAK Arg0 = ", 0xffffff7f808d4c50, }
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: "Entering WAK"
2/13/14 5:21:58.000 PM kernel[0]: ACPIDebug: { "WAK Arg0 = ", 0x808d4c50, }

_PTS is called before sleep, but ACPIDebug.kext may not output the logs until after sleep due to the way the kext works.  Read the readme and/or code so you understand how it works.

Link to comment
Share on other sites

 Share

×
×
  • Create New...