shilohhh Posted January 28, 2014 Share Posted January 28, 2014 I just did a fresh install of 10.9.2 with MacPro5,1 SMBIOS. Replaced the AICPUPM binary with omni's patched SB one and I'm getting the same behaviour here with my 3930k. HWMonitor shows the CPU fluctuating between 12x, 32x and 38x but the Intel Power Gadget shows various speed states (and nothing close to 32x or 38x). Using my stock SSDT and Chameleon. I'd be inclined to trust IPG as I assume it's reading the hardware directly. But perhaps someone can prove this is the case. Also, HWMonitor's CPU voltage reading matches IPG's. So while the CPU states might be getting reported incorrectly, it looks like the CPU is speedstepping correctly. I think IPG and HWmonitor are guessing multipliers based on wattage. I wouldn't trust that you're actually reaching the states they show. Also I think AICPUPM is varying wattage based on CPU load causing those tools to think the CPU is reaching states it isn't. I may be wrong but that makes the most sense to me based on my observations. I believe that's all you'll get with 3930k when you OC. I only get 2 unless I run stock, in which case, I also get 32 and states for each turbo multiplier that's not 38. IPG works differently than AICPUPMI so don't expect them to yield the same exact results.I get 12 32 and 44 in AICPUPMI Link to comment Share on other sites More sharing options...
kundica Posted January 28, 2014 Share Posted January 28, 2014 I get 12 32 and 44 in AICPUPMI Ah... I just checked with MacPro6,1 and I get the same, except 12 32 and 40. My mistake. I've been testing different SMBios types. Link to comment Share on other sites More sharing options...
magnifico Posted January 29, 2014 Share Posted January 29, 2014 Shilo which version have you ? New or old ACPMI because with new rev ACPMI , i have a kernel panic Please? Link to comment Share on other sites More sharing options...
omni Posted January 29, 2014 Author Share Posted January 29, 2014 I wouldn't say that NullCPUPM gives the same results as this patch, else I would not have bothered doing it at all. With NullCPUPM there's no Turbo Boost and there's no apparent stepping down when idle as far as I can tell. Maybe HWMonitor is lying to me, but I can't run IPG since I have a dual CPU setup. Apple will not release an AICPM for SB-E(P) since those are now older processors - they've moved past IB already into Haswell on the desktop and are only using IB-EP in the Trashcan Pro. So the choices are: - keep patching AICPM to get it working, - buy IB-E(P) to replace SB-E(P) and hope it all works without patching, - write our own AICPM. In any case, I wrote a simple Chameleon plugin that sets up some Cx state values in MSRs. This was suggested by Pike in one of his blog posts and it worked for another person who reported more states initialized. I'm going to post the plugin soon, just need to add a check for C7 availability, else it would hang your machine if you don't have it... EDIT: Ok, well call me crazy, but Pike has changed something in his latest AICPMI because I see way more P-States than I used to. I suggest everyone gets this new version because it appears he might have fixed some bug that prevented display of all reached P-States. I mean this: AICPUPMI: CPU P-States [ 12 20 21 22 23 24 25 26 27 28 29 30 31 32 33 (34) 36 ] looks so much better than: AICPUPMI: CPU P-States [ 12 23 26 29 33 34 (35) 36 ] Link to comment Share on other sites More sharing options...
Riley Freeman Posted January 29, 2014 Share Posted January 29, 2014 True, there's no Turbo with NullCPUPM. I didn't factor that in as I haven't used it. But the CPU does step down with NullCPUPM once C1E is enabled in the BIOS. I've been using this since I built this X79. I know the goal is to get things working as much as possible. I just wanted to confirm that stepping works on SB-E with just the patched binary. Link to comment Share on other sites More sharing options...
omni Posted January 29, 2014 Author Share Posted January 29, 2014 I've posted the MSRpatcher.dylib plugin for Chameleon to the OP - place it in your /Extra/modules/ folder. What it does is initializes MSR_PKGC3_IRTL, MSR_PKGC6_IRTL and MSR_PKGC7_IRTL (if C7 is available) with some default values. This was suggested by Pike in a comment to one of his blog posts at http://pikeralpha.wordpress.com/2013/12/29/appleintelcpupowermanagementinfo-kext/ I might actually expand the MSRpatcher to include a config file that will arbitrarily patch user defined MSRs, once I get around to it. 1 Link to comment Share on other sites More sharing options...
omni Posted January 29, 2014 Author Share Posted January 29, 2014 Riley, you are actually right about NullCPUPM. I've ran couple of quick tests and even with with and using Pike's latest version of AICPMI most of the P-States get initialized, except for the Turbo Boost. I'd postulate that we could just take NullCPUPM and write couple of additional methods to it that will report Turbo states back when asked for, and we'll have a working PM. No patching or anything else. The question is why is this happening and my suspicion is that because EIST is enabled (MSR 0x1AA bit 0 is 1 for all the AICPMI dumps I see in this thread) so SpeedStep is not handled by OS X but by the CPU(s). So, I'm going to disable it with my module and see what happens when I run NullCPUPM and AICPM. Stay tuned... Real Macs have it enabled too, so it can't be it. Link to comment Share on other sites More sharing options...
shilohhh Posted January 29, 2014 Share Posted January 29, 2014 Riley, you are actually right about NullCPUPM. I've ran couple of quick tests and even with with and using Pike's latest version of AICPMI most of the P-States get initialized, except for the Turbo Boost. I'd postulate that we could just take NullCPUPM and write couple of additional methods to it that will report Turbo states back when asked for, and we'll have a working PM. No patching or anything else. The question is why is this happening and my suspicion is that because EIST is enabled (MSR 0x1AA bit 0 is 1 for all the AICPMI dumps I see in this thread) so SpeedStep is not handled by OS X but by the CPU(s). So, I'm going to disable it with my module and see what happens when I run NullCPUPM and AICPM. Stay tuned... A note about NullCPUPM C1E=enabled. Power consumption stays above 10w but with the patched AICPUPM I get 5w. Also turbo works in BIOS 4206 which was the last one optimized for SB-E on the R4E before they started adding support for IB-E CPUs Link to comment Share on other sites More sharing options...
yangshun1029 Posted January 29, 2014 Share Posted January 29, 2014 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: logMSRs............................: 1 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: logIGPU............................: 0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: logCStates.........................: 1 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: logIPGStyle........................: 1 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MWAIT C-States.....................: 135456 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012400 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000407 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x1269CD1164 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xD2F4CF254 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xC0000 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x273B00002400 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2400 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x883B0000 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2525252525252626 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2504005B 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x68960005AFFFF 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x3698515 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8842 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x886A 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x14149480000640 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x2684A62 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3600 MHz 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3800 MHz 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 33 36 ] 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 33 34 36 ] 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 32 33 34 36 ] 14-1-30 01:04:09.000 kernel[0]: AICPUPMI: CPU P-States [ 12 30 32 33 34 (36) ] 14-1-30 01:04:10.000 kernel[0]: AICPUPMI: CPU P-States [ 12 30 32 33 34 35 (36) ] 14-1-30 01:04:12.000 kernel[0]: AICPUPMI: CPU P-States [ 12 30 32 33 34 35 36 (37) ] 14-1-30 01:04:12.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 5 6 7 ] 14-1-30 01:04:13.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 25 30 32 33 34 35 36 37 ] 14-1-30 01:04:13.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 2 3 4 7 ] 14-1-30 01:04:13.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 4 5 6 7 ] 14-1-30 01:04:14.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 25 30 31 32 33 34 35 36 (37) ] 14-1-30 01:04:14.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 2 3 4 5 6 7 ] 14-1-30 01:04:14.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 (24) 25 30 31 32 33 34 35 36 37 ] 14-1-30 01:04:14.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 2 3 4 5 6 7 ] 14-1-30 01:04:15.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ] 14-1-30 01:04:15.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 21 24 25 30 31 32 33 34 35 36 37 ] 14-1-30 01:04:15.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ] 14-1-30 01:04:18.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 21 24 25 30 31 32 33 34 35 36 37 (38) ] 14-1-30 01:04:22.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 21 24 25 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:24.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 21 24 25 27 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:30.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 21 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:31.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:32.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 16 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:32.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 16 18 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:34.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 16 18 19 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:35.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 16 18 19 20 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:39.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 16 17 18 19 20 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:47.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 14 16 17 18 19 20 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:04:53.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 23 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-1-30 01:05:07.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 31 32 33 34 35 (36) 37 38 ] 14-1-30 01:06:24.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] Yes,MSRpatcher module adds two values,but MSR_PKG_Cx_RESIDENCY still 0x0 Link to comment Share on other sites More sharing options...
magnifico Posted January 29, 2014 Share Posted January 29, 2014 ok now i have this in kernel log so for me work perfect...or not? i wait news please...i am very confused Last login: Wed Jan 29 11:29:38 on console pro-di-carmine:~ carmine$ cd desktop pro-di-carmine:desktop carmine$ sudo sh Password: sh-3.2# sudo chown -R root:wheel AppleIntelCPUPowerManagementInfo.kext sh-3.2# sudo chmod -R 755 AppleIntelCPUPowerManagementInfo.kext sh-3.2# sudo touch desktop sh-3.2# sudo -k sh-3.2# kextload AppleIntelCPUPowerManagementInfo.kext sh-3.2# cat /var/log/system.log | grep "AICPUPMI:" Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: v3.2 Copyright © 2012-2014 Pike R. Alpha. All rights reserved Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: logMSRs............................: 1 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: logIGPU............................: 0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: logCStates.........................: 1 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: logIPGStyle........................: 1 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MWAIT C-States.....................: 135456 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012000 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E008400 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x20414 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x7C9A68F9CC Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xA9FF4B6066 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x2BE000002F00 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2F00 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x883F0008 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850081 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2F2F2F2F2F2F Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2104005F Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x8006FFFF00C8FFFF Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x7BF37368 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8850 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8868 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x886D Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x80001FFF Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x80000000 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0xED6C784C Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3200 MHz Jan 29 12:06:25 pro-di-carmine kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 4700 MHz Jan 29 12:06:26 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 44 47 ] Jan 29 12:06:26 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 6 7 ] Jan 29 12:06:27 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 44 47 ] Jan 29 12:06:27 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 4 5 6 7 9 10 ] Jan 29 12:06:27 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 36 44 47 ] Jan 29 12:06:27 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 3 4 5 6 7 9 10 ] Jan 29 12:06:28 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 36 44 47 ] Jan 29 12:06:28 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 9 10 ] Jan 29 12:06:29 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 9 10 11 ] Jan 29 12:06:29 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 36 44 45 47 ] Jan 29 12:06:30 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 36 37 44 45 47 ] Jan 29 12:06:30 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 33 36 37 44 45 47 ] Jan 29 12:06:30 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] Jan 29 12:06:31 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 33 35 36 37 44 45 47 ] Jan 29 12:06:32 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 33 35 36 37 39 44 45 47 ] Jan 29 12:06:36 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 30 32 33 35 36 37 39 44 45 47 ] Jan 29 12:06:37 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 12 29 30 32 33 35 36 37 39 44 45 46 (47) ] Jan 29 12:06:38 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 24 29 30 32 33 35 36 37 39 44 45 46 47 ] Jan 29 12:06:39 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 24 28 29 30 32 33 35 36 37 39 44 45 46 47 ] Jan 29 12:06:40 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 24 28 29 30 32 33 35 36 37 39 43 44 45 46 47 ] Jan 29 12:06:41 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 24 28 29 30 32 33 35 36 37 38 39 43 44 45 46 47 ] sh-3.2# Link to comment Share on other sites More sharing options...
Riley Freeman Posted January 29, 2014 Share Posted January 29, 2014 omni: It's C1E that allows stepping when using NullCPUPM. EIST is ignored so you could even disable it. AFAIK all NullCPUPM does is blocks AICPUPM from loading, allowing C1E to control the stepping. However, following up from shilohhh's comment I can confirm that your patched AICPUPM does allow for turbo and lower idle power draw. So it's much better in that regard. I was just looking at the prospects of having to patch/rollback a system kext every update. Now if it was possible to use some kind of injector kext that would be an ideal solution. Link to comment Share on other sites More sharing options...
omni Posted January 29, 2014 Author Share Posted January 29, 2014 @fabiosun, That's good but I'm still concerned that you do not have Cx_RESIDENCY values and so I do not see your C3 states. Please update your post and include a full output of AICPMI so we can see the registers. @yangshun1029, I will update the link in the OP with a mirror soon, please stand by. @magnifico, You don't have Cx_RESIDENCY either, but I also see that your 0xE2 MSR is locked and there are no C-States enabled as well. Did you disable/limit them in your BIOS perhaps? @Riley Freeman, Since this is still a test we need to establish that this works, and then a patcher of some kind would probably be possible. Link to comment Share on other sites More sharing options...
magnifico Posted January 29, 2014 Share Posted January 29, 2014 Another try Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: v3.2 Copyright © 2012-2014 Pike R. Alpha. All rights reserved Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: logMSRs............................: 1 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: logIGPU............................: 0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: logCStates.........................: 1 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: logIPGStyle........................: 1 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MWAIT C-States.....................: 135456 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012000 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E008400 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x20414 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x7AEF0CB58 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xB0F843383 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x2BE000002F00 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x3900 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x883D0008 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850081 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x393939393939 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2104005F Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x8006FFFF00C8FFFF Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x4BDA1F74 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8850 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x8868 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x886D Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x80001FFF Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x80000000 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x3916585F Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3200 MHz Jan 29 18:27:13 pro-di-carmine kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 5700 MHz Jan 29 18:27:14 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 44 (47) ] Jan 29 18:27:14 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 3 4 5 6 8 9 10 ] Jan 29 18:27:15 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 3 4 5 6 8 9 10 11 ] Jan 29 18:27:15 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 44 46 (47) ] Jan 29 18:27:15 pro-di-carmine kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] Jan 29 18:27:18 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 44 46 47 ] Jan 29 18:27:19 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 12 37 44 46 (47) ] Jan 29 18:27:19 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 37 44 46 47 ] Jan 29 18:27:20 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 12 29 33 37 44 46 (47) ] Jan 29 18:27:20 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 33 37 41 44 46 47 ] Jan 29 18:27:21 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 33 37 40 41 44 46 47 ] Jan 29 18:27:21 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 12 29 33 37 38 40 41 44 46 (47) ] Jan 29 18:27:23 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ 12 29 33 37 38 40 41 43 44 46 (47) ] Jan 29 18:27:24 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 33 35 37 38 40 41 43 44 46 47 ] Jan 29 18:27:25 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 32 33 35 37 38 40 41 43 44 46 47 ] Jan 29 18:27:25 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 31 32 33 35 37 38 40 41 43 44 46 47 ] Jan 29 18:27:27 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 31 32 33 35 37 38 40 41 43 44 45 46 47 ] Jan 29 18:27:28 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 31 32 33 35 36 37 38 40 41 43 44 45 46 47 ] Jan 29 18:27:30 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 29 31 32 33 35 36 37 38 40 41 42 43 44 45 46 47 ] Jan 29 18:27:31 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 27 29 31 32 33 35 36 37 38 40 41 42 43 44 45 46 47 ] Jan 29 18:27:31 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 27 29 31 32 33 34 35 36 37 38 40 41 42 43 44 45 46 47 ] Jan 29 18:27:39 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 27 29 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:06 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:32 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 25 27 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:32 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:51 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 22 25 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:51 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 22 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:28:55 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:29:10 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 20 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:29:12 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:24 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 18 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:25 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 18 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:26 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 18 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:27 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 18 19 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:28 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 15 18 19 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:30:30 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] Jan 29 18:56:31 pro-di-carmine kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 ] sh-3.2# AICPUPMI: CPU Maximum Turbo Frequency........: 5700 MHz OMGdo I need another screen ... the numbers coming out of the screen Link to comment Share on other sites More sharing options...
magnifico Posted January 29, 2014 Share Posted January 29, 2014 Fabio please use code [ code] [/code] fabio want to thank you for the great help you gave me Link to comment Share on other sites More sharing options...
omni Posted January 29, 2014 Author Share Posted January 29, 2014 I posted a new version of MSRpatcher, please try it. (mirrored to various hosts) It is for everyone who has MSR 0xE2 set to 0xNNNNN400 meaning that your C-States are disabled. It will forcefully write +3 into it so you get 0xNNNNN403 instead. Obviously, this will ONLY work if you have MSR 0xE2 unlocked. For example: magnifico has a locked MSR 0xE2 so this will not update his 0xE2. fabiosun does not have a locked 0xE2 but he also has a value of 0x401 there, so it won't do anything either. I might change this behaviour in the future to force 0x403 regardless of what your last two bits are. Ultimately the module should have a config file so you can write your own values in there. Link to comment Share on other sites More sharing options...
Balamut Posted January 30, 2014 Share Posted January 30, 2014 @omni: Stupid question whats 0x404 (on OG ACPM, 0x403 on patched), which I have ? Link to comment Share on other sites More sharing options...
Balamut Posted January 30, 2014 Share Posted January 30, 2014 Can any of you with xcode do me a huge favor and compile this? https://github.com/Piker-Alpha/RevoBoot/tree/clang/i386/libsaio/cpu/tools/PMinfo/AppleIntelCPUPowerManagementInfo V3.3 Link to comment Share on other sites More sharing options...
omni Posted January 30, 2014 Author Share Posted January 30, 2014 @omni: Stupid question whats 0x404 (on OG ACPM, 0x403 on patched), which I have ? 0x404 is C7 only, according to the Intel docs (first three bits: 2, 1 and 0): 000b: C0 (no package C-sate support) 001b: C1 (Behavior is the same as 000b) 010b: C3 011b: C6 100b: C7 101b and 110b: Reserved 111: No package C-state limit. Link to comment Share on other sites More sharing options...
yangshun1029 Posted January 30, 2014 Share Posted January 30, 2014 Can any of you with xcode do me a huge favor and compile this? https://github.com/Piker-Alpha/RevoBoot/tree/clang/i386/libsaio/cpu/tools/PMinfo/AppleIntelCPUPowerManagementInfo V3.3 https://github.com/Piker-Alpha/RevoBoot DownloadZIP Just open the AppleIntelCPUPowerManagementInfo.xcodeproj with you Xcode, then just choose “Build” in the "Product",after it run,use the Finder go to the path ~/Library/Developer/Xcode/DerivedData/ The AppleIntelCPUPowerManagementInfo.kexts in the ~/Library/Developer/Xcode/DerivedData/AppleIntelCPUPowerManagementInfo-xxxxxxxxxxxxxxxxxxxxxxxxxxx/Build/Products/Debug/ You will get you won AppleIntelCPUPowerManagementInfo.kexts, if you get KP when the system on,use the "-f". For me it works,you may have a try. Link to comment Share on other sites More sharing options...
magnifico Posted January 30, 2014 Share Posted January 30, 2014 @magnifico, You don't have Cx_RESIDENCY either, but I also see that your 0xE2 MSR is locked and there are no C-States enabled as well. Did you disable/limit them in your BIOS perhaps? No ..i have all C enabled in bios I posted a new version of MSRpatcher, please try it. (mirrored to various hosts) It is for everyone who has MSR 0xE2 set to 0xNNNNN400 meaning that your C-States are disabled. It will forcefully write +3 into it so you get 0xNNNNN403 instead. Obviously, this will ONLY work if you have MSR 0xE2 unlocked. For example: magnifico has a locked MSR 0xE2 so this will not update his 0xE2. fabiosun does not have a locked 0xE2 but he also has a value of 0x401 there, so it won't do anything either. I might change this behaviour in the future to force 0x403 regardless of what your last two bits are. Ultimately the module should have a config file so you can write your own values in there. Omni listen me...but this MSRpatcher is specific for those who use Chameleon boot? or I'm saying stupid? Link to comment Share on other sites More sharing options...
stinga11 Posted January 30, 2014 Share Posted January 30, 2014 Hey Omni I patch the AICPM 13C44 using this patch 842f01 to 852f01 3e753a to 3e9090 845f01 to 855f01 7410b9 to eb10b9 7507b9 to eb07b9 fc0274 to fc02eb 017458 to 01eb58 It is working but I do not know is correctly? Link to comment Share on other sites More sharing options...
Balamut Posted January 30, 2014 Share Posted January 30, 2014 Well after compiling AICPUPMI from source it shows all the states now. Now I need to figure out why C3_RESIDENCY is 0x0. 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: logMSRs............................: 1 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: logIGPU............................: 0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: logCStates.........................: 1 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: logIPGStyle........................: 1 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC10F0012200 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x403 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0xDF3413E981 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xBBC6527B9A 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x271200002700 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2700 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x883E0000 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2424272727272727 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2104005B 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x69F40005A9F40 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x69F36D13 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x14149480001FFF 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x80000000 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x3F807266 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x9A6822130C 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x11098D70F3C 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3400 MHz 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3900 MHz 1/30/14 1:32:43.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 35 39 ] 1/30/14 1:32:43.000 PM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 2 3 5 6 7 9 11 ] 1/30/14 1:32:43.000 PM kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 7 8 9 11 ] 1/30/14 1:32:43.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 28 35 39 ] 1/30/14 1:32:43.000 PM kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 11 ] 1/30/14 1:32:44.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 28 29 35 39 ] 1/30/14 1:32:44.000 PM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 2 3 5 6 7 8 9 11 ] 1/30/14 1:32:44.000 PM kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] 1/30/14 1:32:44.000 PM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 2 3 4 5 6 7 8 9 11 ] 1/30/14 1:32:45.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 22 28 29 35 39 ] 1/30/14 1:32:45.000 PM kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] 1/30/14 1:32:45.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 22 28 29 35 39 ] 1/30/14 1:32:46.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 22 28 29 33 35 39 ] 1/30/14 1:32:46.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 22 28 29 33 35 36 39 ] 1/30/14 1:32:47.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 22 28 29 33 34 35 36 39 ] 1/30/14 1:32:47.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 22 24 28 29 33 34 35 36 39 ] 1/30/14 1:32:48.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 19 22 24 28 29 33 34 35 36 39 ] 1/30/14 1:32:49.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 19 22 24 28 29 30 33 34 35 36 39 ] 1/30/14 1:32:50.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 17 19 20 22 24 28 29 30 33 34 35 36 39 ] 1/30/14 1:32:50.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 19 20 22 24 28 29 30 33 34 35 36 39 ] 1/30/14 1:32:51.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 19 20 22 24 25 28 29 30 33 34 35 36 39 ] 1/30/14 1:32:54.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 19 20 22 24 25 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:32:55.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 18 19 20 22 24 25 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:32:57.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 18 19 20 22 23 24 25 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:32:58.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 18 19 20 22 23 24 25 27 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:33:01.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 22 23 24 25 27 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:33:02.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 21 22 23 24 25 27 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:33:08.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 32 33 34 35 36 39 ] 1/30/14 1:33:16.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 32 33 34 35 36 38 39 ] 1/30/14 1:33:21.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 38 39 ] 1/30/14 1:33:24.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 38 39 ] 1/30/14 1:33:55.000 PM kernel[0]: AICPUPMI: CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 38 39 ] Link to comment Share on other sites More sharing options...
omni Posted January 30, 2014 Author Share Posted January 30, 2014 @magnifico It's for Chameleon right now since that's what I run, but if it proves worth while it could be made for Clover as well. @stinga11 No idea - you are on your own, or use my patched binary for now. Link to comment Share on other sites More sharing options...
Riley Freeman Posted January 31, 2014 Share Posted January 31, 2014 The AICPUPM binary in the new 13C48 update is unchanged from 13C44. Link to comment Share on other sites More sharing options...
Pike R. Alpha Posted January 31, 2014 Share Posted January 31, 2014 Well after compiling AICPUPMI from source it shows all the states now. Now I need to figure out why C3_RESIDENCY is 0x0. 1/30/14 1:32:42.000 PM kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x403 That is because bit-27 in MSR 0xE2 isn't set. 1 Link to comment Share on other sites More sharing options...
Recommended Posts