Contribute
Register

DSDT Debugging/Tracing to system.log

Status
Not open for further replies.

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,805
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I know you had said my system is to old to try and troubleshoot sleep/wake/shutdown so I am giving your ACPIDebug/DSDT RMDT patching a try. I have EmlyDinesh helping me with this and he suggested to try the ACPIdebug/DSDT RMDT patch to see if we can catch anything. There are complaints on real iMacs and older MacBookPros suffering from the same conditions. After googling a bunch I have tried everything I am sure there is more to try but here is my System.log. All I get out of this is the error code for sleep which I am assuming is a kernel generated code maybe generic? I attached the System.log.

Sleep failure code 0x00000000 0x1f006700

My System is Asus G51JX-X2 i7-720QM with Nvidia GTS 360m. No problems in Yosemite. I am having a debug session with him later this morning but if you see anything from your experience in the log please let me know.

I have not tried ioio in terminal yet looking over all the messages in console.

Thanks

The RMDT patch will do nothing by itself. You must install ACPIDebug, and add debug traces to the methods you want to instrument.
 
Joined
Nov 27, 2013
Messages
51
Motherboard
Lenovo IdeaPad P500 (OpenCore 0.7.7)
CPU
2.89 GHz Dual-Core Intel Core i7-3520M/HM76
Graphics
Intel HD Graphics 4000 1536 MB, 1366x768
I pasted "\RMDT.PUSH" in my dsdt and got an error. Can you please elaborate on the third step Rehabman?
 

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,805
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I pasted "\RMDT.PUSH" in my dsdt and got an error. Can you please elaborate on the third step Rehabman?

\RMDT.PUSH is not valid. PUSH requires a single parameter. Refer to the examples in the README, and also examples in the ACPIDebug patch repo itself.

Note: Usually you will use P1, P2, P3... etc instead of PUSH due to the ease of use afforded by these helper methods.
 
Joined
Nov 27, 2013
Messages
51
Motherboard
Lenovo IdeaPad P500 (OpenCore 0.7.7)
CPU
2.89 GHz Dual-Core Intel Core i7-3520M/HM76
Graphics
Intel HD Graphics 4000 1536 MB, 1366x768
"Determining EC query methods:
- install ACPIDebug.kext
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot
- monitor system.log as you press your brightness keys"

So far I got the first two steps, the README said something about the third step I am confused about. I'm sorry but I honestly don't know where to go from here. Do i just copy the examples... "\RMDT.PUSH("Entering _WAK")output: ACPIDebug: "Entering _WAK"

\RMDT.PUSH(Local0)
example output: ACPIDebug: 0x10

\RMDT.P2("Local0", Local0)
example output: ACPIDebug: { "Local0", 0x10, }

\RMDT.P4("OSFL() returns", OSFL(), "OSVR is", OSVR)
example output: ACPIDebug: { "OSFL() returns", 0xABC, "OSVR is", 0x60, }

Name(TEST, Buffer() { 128, 255, 10, 127 }
\RMDT.P1(TEST)
example output: ACPIDebug: { 0x80, 0xFF, 0x0A, 0x7F, }

Name(TEST, Package() { Package() { 128, 255 }, Package() { 1, 2, 3, 10 }) example output: ACPIDebug: { { 0x80, 0xFF }, { 0x1, 0x2, 0x3, 0xA }, }"

...to the dsdt patch? So far i installed the "ioio" and no PS2 code generated. Installed ACPIDebug.kext, copied debug.txt to DSDT.
 

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,805
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
"Determining EC query methods:
- install ACPIDebug.kext
- add the ACPIDebug repo to MaciASL "Sources" per README
- apply ""Add DSDT Debug Methods"
- apply "Instrument EC Queries"
- reboot
- monitor system.log as you press your brightness keys"

So far I got the first two steps, the README said something about the third step I am confused about. I'm sorry but I honestly don't know where to go from here. Do i just copy the examples... "\RMDT.PUSH("Entering _WAK")output: ACPIDebug: "Entering _WAK"

The "Instrument EC Queries" patch adds the necessary RMDT code to give you the information regarding brightness keys. No additional manual steps needed.

See guide: http://www.tonymacx86.com/el-capita...ching-dsdt-ssdt-laptop-backlight-control.html
 
Joined
Oct 25, 2013
Messages
124
Motherboard
MSI X299 SLI Plus
CPU
i7-7820X
Graphics
RX580 + GTX1070 + GT710
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hi Rehabman.

Is there something special I should be aware of when trying this in 10.12?

I tried in 10.10, and it worked just fine:
Code:
$ grep -i acpidebug /Volumes/OSX/private/var/log/*.log
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: Version 0.1.4 starting on OS X Darwin 14.5.
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 enter"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 exit"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 enter"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 exit"

I used your default DSDT patches to insert hooks for your ACPI debug method.

But in 10.12 (same binary kext, so no compilation) I can't find the file the messages get output to. I can see some
ACPIDebug: "EC _Q20 enter"
messages on the screen when I boot in verbose mode, but grepping /privar/var/log comes out empty.

dmesg shows something though:
Code:
$ sudo dmesg | grep -i acpidebug
ACPIDebug: "EC _Q20 enter"
ACPIDebug: "EC _Q20 exit"

but I don't know which file dmesg corresponds to. I thought it was system.log or kernel.log, but it can't find anything in either of them.

Could you point me to where the acpi debug kext is outputting to in 10.12?

Thanks,

Paulo
 

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,805
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi Rehabman.

Is there something special I should be aware of when trying this in 10.12?

I tried in 10.10, and it worked just fine:
Code:
$ grep -i acpidebug /Volumes/OSX/private/var/log/*.log
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: Version 0.1.4 starting on OS X Darwin 14.5.
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 enter"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 exit"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 enter"
/Volumes/OSX/private/var/log/system.log:Nov 28 17:51:13 localhost kernel[0]: ACPIDebug: "EC _Q20 exit"

I used your default DSDT patches to insert hooks for your ACPI debug method.

But in 10.12 (same binary kext, so no compilation) I can't find the file the messages get output to. I can see some
ACPIDebug: "EC _Q20 enter"
messages on the screen when I boot in verbose mode, but grepping /privar/var/log comes out empty.

dmesg shows something though:
Code:
$ sudo dmesg | grep -i acpidebug
ACPIDebug: "EC _Q20 enter"
ACPIDebug: "EC _Q20 exit"

but I don't know which file dmesg corresponds to. I thought it was system.log or kernel.log, but it can't find anything in either of them.

Could you point me to where the acpi debug kext is outputting to in 10.12?

Thanks,

Paulo

10.12 has a new log reporting mechanism. Read about it at developer.apple.com.
 
Joined
Oct 25, 2013
Messages
124
Motherboard
MSI X299 SLI Plus
CPU
i7-7820X
Graphics
RX580 + GTX1070 + GT710
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Thanks!
https://developer.apple.com/reference/os/1891852-logging

Code:
$ log show | grep -i acpidebug
2016-11-29 19:29:39.475383+0000 0xc0       Default     0x0                  0      kernel: (kernel) ACPIDebug: Version 0.1.4 starting on OS X Darwin 16.0.
2016-11-29 19:29:39.607105+0000 0xfd       Default     0x0                  0      kernel: (kernel) ACPIDebug: "EC _Q20 enter"
2016-11-29 19:29:39.614496+0000 0xfd       Default     0x0                  0      kernel: (kernel) ACPIDebug: "EC _Q20 exit"

Now to the debug itself, and why the laptop sleeps in 10.10 but not in 10.12... :banghead:

Thanks again!
 

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,805
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Now to the debug itself, and why the laptop sleeps in 10.10 but not in 10.12... :banghead:

Thanks again!

Off-topic. Open separate thread in appropriate laptop forum.
 
Joined
Dec 4, 2016
Messages
57
Motherboard
Gigabyte GA-Z170X-Gaming 7 ATX LGA1151
CPU
Intel Core i7-6700K
Graphics
EVGA GeForce GTX 970 4GB SSC ACX 2.0+
Hi RehabMan,

First of all, thanks so much for all you've done & posted in this forum to help noobs like myself create their own hackintosh. Your expert knowledge is amazing and we all owe so much to people like you & tonymacx86 & slim.jim.

I built my first desktop hack and managed to install OS Sierra 10.12.1, and read/followed a few of your guides via other semi-successful builds such as this one by JVMacIV using very similar HW as myself (My System config is OS Sierra 10.12.1, Gigabyte GA-Z170x-Gaming 7, i7-6700K 4.0GHz, GeForce GTX 970 SSC ACX2.0+, 32GB DDR4 Crucial Ballistix RAM 2400MHz, Corsair Power Supply ATX760, Samsung 1TB EVO 850 SSD for OS Sierra + Micron 128GB M.2 (via SATA III) SSD for Windows).

After more than a week of installing/re-installing/testing on my hack, I am at the point of getting to an OK system (Working OS Sierra Installed with iMac17,1 in SMBIOS, Working Nvidia Webdriver Graphics card, Working USB2.0 & USB3.0 port, Working Audio, Working App Store, Shutdown working) except for 2 nagging issues I can't seem to fix:

- Issue 1: My display screen freezes after WAKE (which only works pushing my power on button, not via keyboard or mouse).
- Issue 2: I have suboptimal Power Management for my CPU looking at Intel Power Gadget (Idle CPU Hovers too high around 2.0-2.5GHz with up and downs spikes to 4GHz in lieu of being around 1.5GHz for i6700K using default PM after clean tonymacx86 install with SMBIOS set at iMac14,2) after trying to optimize CPU Power Management using my own SSDR.aml generated patch & the patches by JVMacIV which has the same MotherBoard, CPU as myself.

I've detailed my issue in post #21 here. And I just don't know what else to do.

I created my own SSDT.aml file using ssdtPRGen.sh, and put it in ACPI patched folder in relevant EFI mount. And followed JVMacIV's procedure.

Can I use your DSTD Debugging and Tracing tool to show you the trace logs I get & you help me see what's wrong with my system's ACPI tables? Or is there another tool I should use?

Thank you so much for your suggestions. I can upload any file you think you want to see or type any command in Terminal. If this is not the right thread, just let me know where I should post it (I just didn't know where) & I will delete this post. Thank YOU.
 
Last edited:
Status
Not open for further replies.
Top