frankiee Posted February 2, 2014 Share Posted February 2, 2014 Well after compiling AICPUPMI from source it shows all the states now. Now I need to figure out why C3_RESIDENCY is 0x0. Balamut, can I have your compiled kext for testing? I also have C3_RESIDENCY=0 and the same CPU as you. And are you still using the same SSDT you posted? Still the one who works best for me, but maybe it is improved meanwhile? Thanks a lot! Link to comment Share on other sites More sharing options...
shilohhh Posted February 2, 2014 Share Posted February 2, 2014 Thanks omni, I guess I start playing with Mac Pro 5,1 again. I have reliable AGPM workin there. Although I just got it working in 6,1 too. Link to comment Share on other sites More sharing options...
frankiee Posted February 2, 2014 Share Posted February 2, 2014 OK, I managed to compile it myself, and now I also get much more P_States: Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: logMSRs............................: 1 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: logIGPU............................: 0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: logCStates.........................: 1 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: logIPGStyle........................: 1 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MWAIT C-States.....................: 4384 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC10F0012200 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x403 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x464742A770 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0x44D9A2261D Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xE0000 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x23DE00002400 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2400 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88360000 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2424242425252527 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2104005B Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x69F40005A9F40 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x1A14030E Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x14149480001FFF Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x80000000 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x1230AC12 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x1A42D0BB4A Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x1409CEEF68 Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3400 MHz Feb 2 21:15:03 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3900 MHz Feb 2 21:15:04 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 28 36 ] Feb 2 21:15:04 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C3-Cores [ 2 3 4 5 ] Feb 2 21:15:04 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 6 7 ] Feb 2 21:15:05 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ 12 18 28 (34) 36 ] Feb 2 21:15:05 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C3-Cores [ 1 2 3 4 5 6 7 ] Feb 2 21:15:05 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 9 10 11 ] Feb 2 21:15:05 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 28 30 34 36 ] Feb 2 21:15:05 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ] Feb 2 21:15:06 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] Feb 2 21:15:07 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 21 28 30 34 36 ] Feb 2 21:15:08 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 21 28 30 34 36 ] Feb 2 21:15:09 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 21 23 28 30 34 36 ] Feb 2 21:15:10 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 21 23 28 30 32 34 36 ] Feb 2 21:15:11 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 21 23 28 30 31 32 34 36 ] Feb 2 21:15:13 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 20 21 23 28 30 31 32 34 36 ] Feb 2 21:15:14 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 18 19 20 21 23 28 30 31 32 34 35 36 ] Feb 2 21:15:16 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 23 28 30 31 32 34 35 36 ] Feb 2 21:15:17 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 23 28 30 31 32 33 34 35 36 ] Feb 2 21:15:19 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 28 30 31 32 33 34 35 36 ] Feb 2 21:15:22 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 25 28 30 31 32 33 34 35 36 ] Feb 2 21:15:24 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 25 26 28 30 31 32 33 34 35 36 ] Feb 2 21:15:28 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 24 25 26 28 30 31 32 33 34 35 36 ] Feb 2 21:15:35 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 24 25 26 27 28 30 31 32 33 34 35 36 ] Feb 2 21:15:36 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 ] Feb 2 21:15:41 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ 12 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (37) ] Feb 2 21:15:55 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ (12) 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 ] Feb 2 21:16:21 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ 12 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 (37) 38 ] Feb 2 21:17:17 Tests-Mac-Pro kernel[0]: AICPUPMI: CPU P-States [ 12 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 (39) ] MSR_PKGC3_IRTL, MSR_PKGC6_IRTL and MSR_PKG_C3_RESIDENCY still at zero, though 1 Link to comment Share on other sites More sharing options...
magnifico Posted February 2, 2014 Share Posted February 2, 2014 Thanks omni, I guess I start playing with Mac Pro 5,1 again. I have reliable AGPM workin there. Although I just got it working in 6,1 too. Me too With Mac Pro 6.1 , i dont see video you tube ...whyle with 5.1 work perfect Link to comment Share on other sites More sharing options...
omni Posted February 2, 2014 Author Share Posted February 2, 2014 New version of MSRpatcher.dylib has been posted, please read the notes next to it so you know which one to test and use. Link to comment Share on other sites More sharing options...
Balamut Posted February 3, 2014 Share Posted February 3, 2014 New version of MSRpatcher.dylib has been posted, please read the notes next to it so you know which one to test and use. Anyway to do this for Cover? Link to comment Share on other sites More sharing options...
omni Posted February 3, 2014 Author Share Posted February 3, 2014 Probably, but we need to test whether changing these values actually helps before adding support for another boot loader. Link to comment Share on other sites More sharing options...
yangshun1029 Posted February 3, 2014 Share Posted February 3, 2014 Useing the MSRpatcher_002 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: v3.3 Copyright © 2012-2014 Pike R. Alpha. All rights reserved 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: logMSRs............................: 1 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: logIGPU............................: 0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: logCStates.........................: 1 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: logIPGStyle........................: 1 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MWAIT C-States.....................: 135456 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT......(0x35) : 0x40008 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012400 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000407 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_MPERF.................(0xE7) : 0x11BBD62198 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_APERF.................(0xE8) : 0xC80A5B655 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_FLEX_RATIO.............(0x194) : 0xC0000 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS.......(0x198) : 0x273B00002400 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL......(0x199) : 0x2400 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_CLOCK_MODULATION......(0x19A) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_THERM_STATUS..........(0x19C) : 0x88380000 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_MISC_ENABLES..........(0x1A0) : 0x850089 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2525252525252626 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_POWER_CTL..............(0x1FC) : 0x2504005B 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT........(0x610) : 0x68960005AFFFF 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS......(0x611) : 0x34190C7 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKGC3_IRTL.............(0x60a) : 0x8842 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKGC6_IRTL.............(0x60b) : 0x886A 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKGC7_IRTL.............(0x60c) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x14149480000640 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT........(0x638) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS......(0x639) : 0x24CB1B2 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PP0_POLICY.............(0x63a) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU Low Frequency Mode.............: 1200 MHz 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU Maximum non-Turbo Frequency....: 3600 MHz 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU Maximum Turbo Frequency........: 3800 MHz 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 35 36 ] 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU P-States [ 12 33 35 (36) ] 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 29 33 35 36 ] 14-2-3 14:18:43.000 kernel[0]: AICPUPMI: CPU P-States [ 12 29 32 33 35 (36) ] 14-2-3 14:18:46.000 kernel[0]: AICPUPMI: CPU P-States [ 12 29 32 33 35 36 (37) ] 14-2-3 14:18:46.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 4 5 ] 14-2-3 14:18:46.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 2 3 4 5 ] 14-2-3 14:18:47.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 ] 14-2-3 14:18:47.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 1 2 3 4 5 6 ] 14-2-3 14:18:48.000 kernel[0]: AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 ] 14-2-3 14:18:48.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 7 ] 14-2-3 14:18:49.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 22 29 32 33 35 36 37 ] 14-2-3 14:18:49.000 kernel[0]: AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 ] 14-2-3 14:18:50.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 22 29 32 33 35 36 37 ] 14-2-3 14:18:50.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 22 27 29 32 33 35 36 37 ] 14-2-3 14:18:51.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 18 22 27 29 32 33 35 36 37 (38) ] 14-2-3 14:18:52.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 18 22 27 29 31 32 33 35 36 (37) 38 ] 14-2-3 14:18:56.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 18 22 (24) 27 29 31 32 33 35 36 37 38 ] 14-2-3 14:18:57.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 22 24 27 29 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:03.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 22 24 25 27 29 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:03.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 18 20 22 24 25 27 29 31 32 33 34 35 36 (37) 38 ] 14-2-3 14:19:04.000 kernel[0]: AICPUPMI: CPU P-States [ 12 13 18 20 22 (24) 25 27 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:06.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 20 22 24 25 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:07.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 18 20 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:07.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 18 19 20 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:11.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 17 18 19 20 22 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:14.000 kernel[0]: AICPUPMI: CPU P-States [ (12) 13 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:14.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:19:20.000 kernel[0]: AICPUPMI: CPU P-States [ 12 (13) 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 ] 14-2-3 14:21:01.000 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 ] 14-2-3 14:21:03.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 ] MSR_PKG_Cx_RESIDENCY still 0x0 Link to comment Share on other sites More sharing options...
Klonkrieger2 Posted February 3, 2014 Share Posted February 3, 2014 using msr_patch v003 on xeon e5-2690 v2 after startup: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000401 a few seconds later: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x401 then again AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000401 so it just toggles around... but according to intel's documents 0x1EXXXXX isn't even valid for xeon e5 v2. Package Residencies all at 0x0 Link to comment Share on other sites More sharing options...
frankiee Posted February 3, 2014 Share Posted February 3, 2014 Maybe this is actually another bug in AICPUPM? PStates also weren't reported before a recent patch. So I would look at IPG to see if PM actually works. Link to comment Share on other sites More sharing options...
omni Posted February 3, 2014 Author Share Posted February 3, 2014 0x1Ennnnn is supposed to toggle C3/C6 bits but seems like AICPM just turns them off. Blasted ! Although MSRpatcher v003 is supposed to set 0xE2 to 0x1E000403, I don't know where that ...401 is coming from? This Cx RESIDENCY not activating is puzzling, as it works for me on my Xeon v1. One would think that with Xeon v2 it should work OOB. Link to comment Share on other sites More sharing options...
Pike R. Alpha Posted February 4, 2014 Share Posted February 4, 2014 0x1Ennnnn is supposed to toggle C3/C6 bits but seems like AICPM just turns them off. Blasted ! Although MSRpatcher v003 is supposed to set 0xE2 to 0x1E000403, I don't know where that ...401 is coming from? This Cx RESIDENCY not activating is puzzling, as it works for me on my Xeon v1. One would think that with Xeon v2 it should work OOB. I presume that MSRpatcher is loaded after AppleIntelCPUPowerManagement.kext Correct? Check the _CST/ACST object when you get a different value, because it may be missing certain C-States. Like in this case C3, C6 and C7. And while the Intel documentations lists bits 16-64 as reserved... they get changed. Without a reboot so it appears to be acceptable otherwise you would get a reboot. Also note that the MacPro6,1 has C1, C3 and C6 in the ACST objects, which means that C3 is supported to work as well. Even when the Intel documentations states otherwise. Link to comment Share on other sites More sharing options...
magnifico Posted February 4, 2014 Share Posted February 4, 2014 Please...if try to put SSDT( from generation pike script) why have this in kernel log? Failed to find sleep policy for this platform! Disabling deep sleep. Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 GeForceSensors (pci1): chipset: GK106 (NVE6) bios: 80.06.28.00 GeForceSensors (pci1): started IOPPF: AppleIntelCPUPowerManagement mode ErP Timer is not specified! Defaulting to 0x3840 X86PlatformShim::sendStepper - Stepper dictionary from plist is NULL! X86PlatformShim::start - Failed to send stepper Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 VM Swap Subsystem is ON Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 And dont have AGPM in kernel log.. Link to comment Share on other sites More sharing options...
omni Posted February 4, 2014 Author Share Posted February 4, 2014 @fabiosun We are looking at initialized Cx_RESIDENCY values as well as C3/C6 -Cores and P-States values, just like you have in your latest dump. That configuration you have should technically work, do some benches and see the results? @Pike MSRpatcher is a Chameleon boot loader plugin. It loads ahead of everything and changes the 0xE2 as well as the Cx_IRTL MSRs. Loading after AICPM would not do much since AICPM changes all those values? @magnifico, Because you are using Macpro5,1 or some other ACPI_SMC* based platform? You have to make sure X86Platform* is loaded...we've gone through this already. Link to comment Share on other sites More sharing options...
magnifico Posted February 4, 2014 Share Posted February 4, 2014 @magnifico, Because you are using Macpro5,1 or some other ACPI_SMC* based platform? You have to make sure X86Platform* is loaded...we've gone through this already. Yes i use 5,1 and X86 there is not in Ioreg Link to comment Share on other sites More sharing options...
kundica Posted February 4, 2014 Share Posted February 4, 2014 Yes i use 5,1 and X86 there is not in Ioreg that's the issue. You need to use the new Mac Pro or another ivy bridge plist. Link to comment Share on other sites More sharing options...
magnifico Posted February 4, 2014 Share Posted February 4, 2014 that's the issue. You need to use the new Mac Pro or another ivy bridge plist. Sure..where is ..i dont see ..mhmm Link to comment Share on other sites More sharing options...
omni Posted February 5, 2014 Author Share Posted February 5, 2014 plugin-type = 1 in your CPU0, I think I said this about half a dozen times already...getting tired of it. Link to comment Share on other sites More sharing options...
magnifico Posted February 5, 2014 Share Posted February 5, 2014 plugin-type = 1 in your CPU0, I think I said this about half a dozen times already...getting tired of it. Omni trusted i have this in SSDT Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { Store ("Method P000._DSM Called", Debug) If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x02) { "plugin-type", One }) } } But i have also this spam in kernel log DSMOS has arrived hfs: mounted DatiMac on device disk4s2 Failed to find sleep policy for this platform! Disabling deep sleep. Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 Standby delay is not specified! Defaulting to 0x1068 ErP Timer is not specified! Defaulting to 0x3840 GeForceSensors (pci1): chipset: GK106 (NVE6) bios: 80.06.28.00 GeForceSensors (pci1): started Link to comment Share on other sites More sharing options...
yangshun1029 Posted February 5, 2014 Share Posted February 5, 2014 Method (_DSM, 4, NotSerialized) { Store ("Writing plugin-type to Registry!", Debug) Store (Package (0x02) { "plugin-type", One }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } Like this. Link to comment Share on other sites More sharing options...
Balamut Posted February 7, 2014 Share Posted February 7, 2014 Build 13C53 is up. Link to comment Share on other sites More sharing options...
yangshun1029 Posted February 7, 2014 Share Posted February 7, 2014 Sleep issue needs help! 14-2-7 18:51:49.000 kernel[0]: Wake reason: EUSB USBE 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 1: 0x00000002c0df9868, delta 0x2b141cdc0 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 2: 0x00000002c12e6860, delta 0x2b141cdb8 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 3: 0x00000002c15bb2ec, delta 0x2b141cd90 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 4: 0x00000002c1a9fb38, delta 0x2b141cdec 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 5: 0x00000002c1d768ad, delta 0x2b141cdc4 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 6: 0x00000002c22564b1, delta 0x2b141cdfa 14-2-7 18:51:48.000 kernel[0]: Unsynchronized TSC for cpu 7: 0x00000002c252c325, delta 0x2b141cdee If i try to wake up the system it will freez because of the Unsynchronized TSC for cpu. I try to use VoodooTSCSync.kext to fix it ,it actually works,but after wake up, the frequency of cpu will stuck at the hign frequency and never go down. Confused! Any suggestion? Link to comment Share on other sites More sharing options...
Riley Freeman Posted February 7, 2014 Share Posted February 7, 2014 Build 13C53 is up. AICPUPM binary is still unchanged so omni's patched version still works. Link to comment Share on other sites More sharing options...
yangshun1029 Posted February 9, 2014 Share Posted February 9, 2014 Yes, The VoodooTSCSync only affect C001 Maybe wo can try add some snippet eliminate the need to use VoodooTSCSync.kext Link to comment Share on other sites More sharing options...
xelanaiznac Posted February 13, 2014 Share Posted February 13, 2014 any news on 13c59? Link to comment Share on other sites More sharing options...
Recommended Posts