fluxus123 Posted March 27, 2017 Share Posted March 27, 2017 Hi peeps, I don't know what I've done to be honest, the last thing I did was installing an atheros card. Worked great once properly set up, but soon after, the machine developed kernel panics. 1 out of 10 times it would boot. Please see screenshots attached. What I've done to no avail: Reset bios to defaults Take out wifi card Tried last working dsdt and clover config Downloaded the latest fakeSMC Any help would be greatly appreciated Link to comment Share on other sites More sharing options...
artur_pt Posted March 27, 2017 Share Posted March 27, 2017 hello try with this fakesmc http://www.insanelymac.com/forum/index.php?app=core&module=attach§ion=attach&attach_id=214932 good hack Link to comment Share on other sites More sharing options...
fluxus123 Posted March 27, 2017 Author Share Posted March 27, 2017 Hi artur, Thanks for this! Just on my way home from work. Will give it a try shortly. Out of curiosity, what could have caused this error to emerge? And what is different in this fakeSMC compared to the latest found in rehab man repo? I'm always keen to learn instead of copy and paste things if you know what I mean Link to comment Share on other sites More sharing options...
MaLd0n Posted March 27, 2017 Share Posted March 27, 2017 for me the best is... http://www.hwsensors.com/releases i never have a problem 1 Link to comment Share on other sites More sharing options...
duffs Posted March 27, 2017 Share Posted March 27, 2017 Don't steel Mac OS X error. check your smbios, serial.... Link to comment Share on other sites More sharing options...
fluxus123 Posted March 27, 2017 Author Share Posted March 27, 2017 Do you think they blacklisted my serial? I vaguely remember removing the FaceTime block on little snitch so that might have caused it :/ Link to comment Share on other sites More sharing options...
TheRacerMaster Posted March 27, 2017 Share Posted March 27, 2017 It has nothing to do with that, DSMOS.kext is probably failing to read OSK0/OSK1 (through AppleSMC) due to FakeSMC not working properly. 1 Link to comment Share on other sites More sharing options...
fluxus123 Posted March 28, 2017 Author Share Posted March 28, 2017 It boots fine from usb with the latest fakeSMC. After putting that into the ESP of my hard drive it booted fine 1st time around and then after that KPs again. The other thing I remember that started before developing KPs is this mystery: I turned hyper threading off in BIOS to see how it affects bench score and this caused half of my devices to disappear from DCPI manager and IOReg at least - 25 of them! After turning it back on, they all showed up again, but after the next restart they were all gone again. I don't know what's happening here, something seems to be really screwed? Link to comment Share on other sites More sharing options...
fluxus123 Posted April 10, 2017 Author Share Posted April 10, 2017 so I created another partition and reinstalled a fresh copy of Sierra onto it. I am using the same ESP and clover config. The fresh copy boots without problem with the same fakesmc, but the other doesn't. Any other suggestions of what to try? I think it is safe to assume it has nothing to do with fakeSMC, BIOS, clover.config... Link to comment Share on other sites More sharing options...
fluxus123 Posted April 14, 2017 Author Share Posted April 14, 2017 fixing permissions in S/L/E and rebuilding kernelcache remotely from the new partition fixed the issues. Now able to boot into my old partition again. Thanks for all the suggestions though! Link to comment Share on other sites More sharing options...
fluxus123 Posted April 28, 2017 Author Share Posted April 28, 2017 So my last comment can go straight in the bin. Finally did a restart since (I know I am terrible) and back to the same problem. What I did notice is this: Booting from my rescue stick with generic SMBios (macbook1.1) without custom DSDT let's me boot fine. So I decided to do a fresh install of clover on my ESP and grab a FakeSMC from the usual places (HWSensors/Rehabman) Again, default settings with a "known to work config" (macbook1,1) and without custom DSDT and SSDT for power management let's me boot my main Sierra partition with -v npci=0x3000 (the npci flag wasn't necessary before ever since I started using Piker's ssdtPRGen, but now it is again?) The moment I put my custom DSDT (that MaLd0n kindly helped me with all through another thread) and SSDT in patched folder and pick my old config file the system gives me the same KP Interestingly, I wanted to know if it is OS-X-Update-depending, because my original Sierra Partition booted fine up until 12.2 or 12.3, I can't remember which. So, I updated my Sierra 12.1 that I installed on the same drive, which booted fine with my DSDT and SSDT, to 12.4 and this now too gives me the same KP. Now I am wondering if Apple changed/implemented something to weed out the hacks? Any one else run into this problem yet and has a solution, or is it just me? Maybe I just have to go back to the last version that worked? Picture of KP attached. Link to comment Share on other sites More sharing options...
MaLd0n Posted April 28, 2017 Share Posted April 28, 2017 U can post ur full Clover Folder? What Clover version u use? Clover_v2.4k_r4064.pkg.zip Link to comment Share on other sites More sharing options...
fluxus123 Posted April 29, 2017 Author Share Posted April 29, 2017 sorry for delay. hectic at work past few days. efi folder attached. EFI.zip Link to comment Share on other sites More sharing options...
fluxus123 Posted April 29, 2017 Author Share Posted April 29, 2017 IOReg attached IoReg.zip Link to comment Share on other sites More sharing options...
MaLd0n Posted April 29, 2017 Share Posted April 29, 2017 Generate SSDT PM with Pike script Link to comment Share on other sites More sharing options...
fluxus123 Posted April 29, 2017 Author Share Posted April 29, 2017 I do have the SSDT it just wasn't in the efi folder as the efi folder I sent was from my USB stick. Link to comment Share on other sites More sharing options...
MaLd0n Posted April 29, 2017 Share Posted April 29, 2017 Good Check if generate is good with Pike kext Link to comment Share on other sites More sharing options...
fluxus123 Posted May 3, 2017 Author Share Posted May 3, 2017 so a couple of things: booting with your edited dsdt and config.plist helped to boot the system again. Thanks! Now, I generated new serial, synced board serial and generated new uuid. imessage and facetime all working again. But I have a couple of things not playing ball: 1. config.plist now requires Kernel PM patch, which I didn't need before. If I don't tick the box, then boot hangs at +++++++++ What do you think could have changed that? Did you change anything relating in dsdt? 2. shutdown stopped working: now hangs after initiating unmount on drives. Any idea what might cause this? 3. sleep issues: either waking instantly once going into hibernation, or not waking from sleep. Or maybe it does wake from sleep but just loses video signal? hard to tell Re PM: I generated Pike's ssdt again. sysctl mchdep info and AppleIntelInfo output below. machdep.user_idle_level: 0 machdep.cpu.tsc_ccc.denominator: 0 machdep.cpu.tsc_ccc.numerator: 0 machdep.cpu.thread_count: 24 machdep.cpu.core_count: 12 machdep.cpu.address_bits.virtual: 48 machdep.cpu.address_bits.physical: 46 machdep.cpu.tlb.shared: 1024 machdep.cpu.tlb.data.small_level1: 64 machdep.cpu.tlb.data.small: 64 machdep.cpu.tlb.inst.large: 8 machdep.cpu.cache.size: 256 machdep.cpu.cache.L2_associativity: 8 machdep.cpu.cache.linesize: 64 machdep.cpu.arch_perf.fixed_width: 48 machdep.cpu.arch_perf.fixed_number: 3 machdep.cpu.arch_perf.events: 0 machdep.cpu.arch_perf.events_number: 7 machdep.cpu.arch_perf.width: 48 machdep.cpu.arch_perf.number: 4 machdep.cpu.arch_perf.version: 3 machdep.cpu.xsave.extended_state1: 1 0 0 0 machdep.cpu.xsave.extended_state: 7 832 832 0 machdep.cpu.thermal.energy_policy: 1 machdep.cpu.thermal.hardware_feedback: 0 machdep.cpu.thermal.package_thermal_intr: 1 machdep.cpu.thermal.fine_grain_clock_mod: 1 machdep.cpu.thermal.core_power_limits: 1 machdep.cpu.thermal.ACNT_MCNT: 1 machdep.cpu.thermal.thresholds: 2 machdep.cpu.thermal.invariant_APIC_timer: 1 machdep.cpu.thermal.dynamic_acceleration: 1 machdep.cpu.thermal.sensor: 1 machdep.cpu.mwait.sub_Cstates: 8480 machdep.cpu.mwait.extensions: 3 machdep.cpu.mwait.linesize_max: 64 machdep.cpu.mwait.linesize_min: 64 machdep.cpu.processor_flag: 0 machdep.cpu.microcode_version: 20 machdep.cpu.cores_per_package: 16 machdep.cpu.logical_per_package: 32 machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT RDTSCP TSCI machdep.cpu.leaf7_features: SMEP ERMS RDWRFSGS TSC_THREAD_OFFSET BMI1 HLE AVX2 BMI2 INVPCID RTM PQM FPU_CSDS machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C machdep.cpu.brand: 0 machdep.cpu.signature: 198385 machdep.cpu.extfeature_bits: 142473169152 machdep.cpu.leaf7_feature_bits: 16315 machdep.cpu.feature_bits: 9223086162756500479 machdep.cpu.stepping: 1 machdep.cpu.extfamily: 0 machdep.cpu.extmodel: 3 machdep.cpu.model: 63 machdep.cpu.family: 6 machdep.cpu.brand_string: Genuine Intel® CPU @ 2.00GHz machdep.cpu.vendor: GenuineIntel machdep.cpu.max_ext: 2147483656 machdep.cpu.max_basic: 15 machdep.x86_fp_simd_isr_uses: 0 machdep.eager_timer_evaluation_max: 5865107 machdep.eager_timer_evaluations: 13980 machdep.xcpm.epp_override: 0 machdep.xcpm.io_epp_boost_enabled: 0 machdep.xcpm.ring_boost_enabled: 0 machdep.xcpm.io_cst_control_enabled: 0 machdep.xcpm.io_filtered_reads: 0 machdep.xcpm.io_control_disengages: 1 machdep.xcpm.io_control_engages: 0 machdep.xcpm.io_thermal_level: 0 machdep.xcpm.gpu_thermal_level: 0 machdep.xcpm.cpu_thermal_level: 0 machdep.xcpm.deep_idle_total_stats: n/a machdep.xcpm.deep_idle_last_stats: n/a machdep.xcpm.deep_idle_count: 0 machdep.xcpm.qos_txfr: 1 machdep.xcpm.deep_idle_log: 0 machdep.xcpm.forced_idle_period: 30000000 machdep.xcpm.forced_idle_ratio: 100 machdep.xcpm.mbd_relaxations: 0 machdep.xcpm.mbd_applications: 0 machdep.xcpm.mbd_mode: 1 machdep.xcpm.maxintdelay: 0 machdep.xcpm.maxbusdelay: 0 machdep.xcpm.ratio_changes_total: 412111 machdep.xcpm.ratio_change_ratelimit_ns: 500000 machdep.xcpm.vectors_loaded_count: 1 machdep.xcpm.tuib_ns: 0 machdep.xcpm.bootpst: 26 machdep.xcpm.bootplim: 0 machdep.xcpm.power_source: 0 machdep.xcpm.tuib_enabled: 0 machdep.xcpm.tuib_plimit_min_100mhz_ratio: 8 machdep.xcpm.tuib_plimit_max_100mhz_ratio: 26 machdep.xcpm.soft_plimit_min_100mhz_ratio: 8 machdep.xcpm.soft_plimit_max_100mhz_ratio: 26 machdep.xcpm.hard_plimit_min_100mhz_ratio: 8 machdep.xcpm.hard_plimit_max_100mhz_ratio: 26 machdep.xcpm.mode: 1 machdep.misc.nmis: 0 machdep.misc.timer_queue_trace: machdep.misc.interrupt_latency_max: 0x0 0xde 0x6ae5d0 machdep.misc.panic_restart_timeout: 1266874889 machdep.misc.fast_uexc_support: 1 machdep.tsc.nanotime.generation: 2 machdep.tsc.nanotime.shift: 0 machdep.tsc.nanotime.scale: 2152174398 machdep.tsc.nanotime.ns_base: 0 machdep.tsc.nanotime.tsc_base: 272608270316 machdep.tsc.rebase_abs_time: 135601864339 machdep.tsc.at_boot: 1995640932 machdep.tsc.deep_idle_rebase: 1 machdep.tsc.frequency: 1995640920 machdep.memmap.Other: 0 machdep.memmap.Unusable: 0 machdep.memmap.Reserved: 68661248 machdep.memmap.PalCode: 0 machdep.memmap.ACPINVS: 15998976 machdep.memmap.ACPIReclaim: 593920 machdep.memmap.RuntimeServices: 0 machdep.memmap.Conventional: 68600573952 machdep.pmap.kern_pv_reserve: 16000 machdep.pmap.kernel_text_ps: 2097152 machdep.pmap.hashmax: 16 machdep.pmap.hashcnts: 1655952 machdep.pmap.hashwalks: 1537447 machdep.vectors.IPI: 222 machdep.vectors.timer: 221 xcpm looks like it's working just before with ratio_changes_total showing plenty changes and vectors_loaded_count showing 1 What's confusing is it's saying machdep.cpu.microcode_version: 20 machdep.cpu.cores_per_package: 16 machdep.cpu.logical_per_package: 32 This makes me wonder if it's linked to the error in clover boot log saying cpu number out of control? It dows give the correct core and thread count further up though? Also, Microcode version 20? My Bios says it's using microcode revision 14, which I verified by extracting with UBUtool. Is Mac OS X using their own microcode? Is this where things get messy? Below is AppleIntelInfo output. AppleIntelInfo.kext v2.1 Copyright © 2012-2017 Pike R. Alpha. All rights reserved enableHWP................................: 0 Settings: ------------------------------------------ logMSRs..................................: 1 logIGPU..................................: 0 logCStates...............................: 1 logIPGStyle..............................: 1 InitialTSC...............................: 0x7e5eb0008a (27 MHz) MWAIT C-States...........................: 8480 Processor Brandstring....................: Genuine Intel® CPU @ 2.00GHz Processor Signature..................... : 0x306F1 ------------------------------------------ - Family............................... : 6 - Stepping............................. : 1 - Model................................ : 0x3F (63) Model Specific Registers (MSRs) ------------------------------------------ MSR_CORE_THREAD_COUNT............(0x35) : 0xFFFFFF80AB99EC00 ------------------------------------------ - Core Count........................... : 12 - Thread Count......................... : 24 MSR_PLATFORM_INFO................(0xCE) : 0x80C33FB811400 ------------------------------------------ - Maximum Non-Turbo Ratio.............. : 0x14 (2000 MHz) - Ratio Limit for Turbo Mode........... : 1 (programmable) - TDP Limit for Turbo Mode............. : 1 (programmable) - Low Power Mode Support............... : 1 (LPM supported) - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available) - Maximum Efficiency Ratio............. : 12 - Minimum Operating Ratio.............. : 8 MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x8403 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 1 (enabled, IO read of MSR(0xE4) mapped to MWAIT) - CFG Lock............................. : 1 (MSR locked until next reset) - C3 State Auto Demotion............... : 0 (disabled/unsupported) - C1 State Auto Demotion............... : 0 (disabled/unsupported) - C3 State Undemotion.................. : 0 (disabled/unsupported) - C1 State Undemotion.................. : 0 (disabled/unsupported) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) MSR_PMG_IO_CAPTURE_BASE..........(0xE4) : 0x10414 ------------------------------------------ - LVL_2 Base Address................... : 0x414 - C-state Range........................ : 1 (C6 is the max C-State to include) IA32_MPERF.......................(0xE7) : 0x790BBCA4E IA32_APERF.......................(0xE8) : 0x855A0B263 MSR_FLEX_RATIO...................(0x194) : 0x0 ------------------------------------------ MSR_IA32_PERF_STATUS.............(0x198) : 0x1BDA00001800 ------------------------------------------ - Current Performance State Value...... : 0x1800 (2400 MHz) MSR_IA32_PERF_CONTROL............(0x199) : 0xFF00 ------------------------------------------ - Target performance State Value....... : 0xFF00 (25500 MHz) - Intel Dynamic Acceleration........... : 0 (IDA engaged) IA32_CLOCK_MODULATION............(0x19A) : 0x0 IA32_THERM_INTERRUPT.............(0x19B) : 0x0 IA32_THERM_STATUS................(0x19C) : 0x883C0000 ------------------------------------------ - Thermal Status....................... : 0 - Thermal Log.......................... : 0 - PROCHOT # or FORCEPR# event.......... : 0 - PROCHOT # or FORCEPR# log............ : 0 - Critical Temperature Status.......... : 0 - Critical Temperature log............. : 0 - Thermal Threshold #1 Status.......... : 0 - Thermal Threshold #1 log............. : 0 - Thermal Threshold #2 Status.......... : 0 - Thermal Threshold #2 log............. : 0 - Power Limitation Status.............. : 0 - Power Limitation log................. : 0 - Current Limit Status................. : 0 - Current Limit log.................... : 0 - Cross Domain Limit Status............ : 0 - Cross Domain Limit log............... : 0 - Digital Readout...................... : 60 - Resolution in Degrees Celsius........ : 1 - Reading Valid........................ : 1 (valid) MSR_THERM2_CTL...................(0x19D) : 0x0 IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - Fast-Strings......................... : 1 (enabled) - FOPCODE compatibility mode Enable.... : 0 - Automatic Thermal Control Circuit.... : 1 (enabled) - Split-lock Disable................... : 0 - Performance Monitoring............... : 1 (available) - Bus Lock On Cache Line Splits Disable : 0 - Hardware prefetch Disable............ : 0 - Processor Event Based Sampling....... : 0 (PEBS supported) - GV1/2 legacy Enable.................. : 0 - Enhanced Intel SpeedStep Technology.. : 1 (enabled) - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported) - Adjacent sector prefetch Disable..... : 0 - CFG Lock............................. : 0 (MSR not locked) - xTPR Message Disable................. : 1 (disabled) MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x5D0A00 ------------------------------------------ - Turbo Attenuation Units.............. : 0 - Temperature Target................... : 93 - TCC Activation Offset................ : 0 MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000 ------------------------------------------ - EIST Hardware Coordination........... : 0 (hardware coordination enabled) - Energy/Performance Bias support...... : 1 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software) - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores) MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x171717171718191A ------------------------------------------ - Maximum Ratio Limit for C01.......... : 1A (2600 MHz) - Maximum Ratio Limit for C02.......... : 19 (2500 MHz) - Maximum Ratio Limit for C03.......... : 18 (2400 MHz) - Maximum Ratio Limit for C04.......... : 17 (2300 MHz) - Maximum Ratio Limit for C05.......... : 17 (2300 MHz) - Maximum Ratio Limit for C06.......... : 17 (2300 MHz) - Maximum Ratio Limit for C07.......... : 17 (2300 MHz) - Maximum Ratio Limit for C08.......... : 17 (2300 MHz) MSR_TURBO_RATIO_LIMIT1...........(0x1AE) : 0x1717171717171717 ------------------------------------------ - Maximum Ratio Limit for C09.......... : 17 (2300 MHz) - Maximum Ratio Limit for C10.......... : 17 (2300 MHz) - Maximum Ratio Limit for C11.......... : 17 (2300 MHz) - Maximum Ratio Limit for C12.......... : 17 (2300 MHz) IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x1 ------------------------------------------ - Power Policy Preference...............: 1 (highest performance) MSR_POWER_CTL....................(0x1FC) : 0x2904005B ------------------------------------------ - Bi-Directional Processor Hot..........: 1 (enabled) - C1E Enable............................: 1 (enabled) MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03 ------------------------------------------ - Power Units.......................... : 3 (1/8 Watt) - Energy Status Units.................. : 14 (61 micro-Joules) - Time Units .......................... : 10 (976.6 micro-Seconds) MSR_PKG_POWER_LIMIT..............(0x610) : 0x783F000158348 ------------------------------------------ - Package Power Limit #1............... : 105 Watt - Enable Power Limit #1................ : 1 (enabled) - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1) - Time Window for Power Limit #1....... : 10 (2560 milli-Seconds) - Package Power Limit #2............... : 126 Watt - Enable Power Limit #2................ : 1 (enabled) - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2) - Time Window for Power Limit #2....... : 3 (20 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PKG_ENERGY_STATUS............(0x611) : 0x4E2201B ------------------------------------------ - Total Energy Consumed................ : 5000 Joules (Watt = Joules / seconds) MSR_PKG_POWER_INFO...............(0x614) : 0x2F069001D00348 ------------------------------------------ - Thermal Spec Power................... : 105 Watt - Minimum Power........................ : 0 - Maximum Power........................ : 210 - Maximum Time Window.................. : 0 MSR_PP0_POWER_LIMIT..............(0x638) : 0x0 MSR_PP0_ENERGY_STATUS............(0x639) : 0x0 MSR_TURBO_ACTIVATION_RATIO.......(0x64C) : 0x0 MSR_CONFIG_TDP_NOMINAL...........(0x648) : 0x14 MSR_CONFIG_TDP_LEVEL1............(0x649) : 0xE8069000120348 MSR_CONFIG_TDP_LEVEL2............(0x64a) : 0xE8069000000000 MSR_CONFIG_TDP_CONTROL...........(0x64b) : 0x0 MSR_TURBO_ACTIVATION_RATIO.......(0x64c) : 0x0 MSR_PKGC6_IRTL...................(0x60b) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x1F439C6DAC MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x14DD53EC IA32_TSC_DEADLINE................(0x6E0) : 0x7E618CFB8A CPU Ratio Info: ------------------------------------------ Base Clock Frequency (BLCK)............. : 100 MHz Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz) Maximum non-Turbo Ratio/Frequency........: 20 (2000 MHz) Maximum Turbo Ratio/Frequency............: 26 (2600 MHz) P-State ratio * 100 = Frequency in MHz ------------------------------------------ CPU P-States [ 19 23 (26) ] CPU C6-Cores [ 1 2 5 6 8 11 14 22 ] CPU P-States [ 19 23 24 (25) 26 ] CPU C6-Cores [ 1 2 4 5 6 8 10 11 14 16 21 22 ] CPU C6-Cores [ 0 1 2 4 5 6 8 9 10 11 12 14 16 18 20 21 22 ] CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 16 18 20 21 22 ] CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 16 18 20 21 22 ] CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 16 18 20 21 22 ] CPU P-States [ 19 22 23 24 25 (26) ] CPU C6-Cores [ 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15 16 18 19 20 21 22 23 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 19 20 21 22 23 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 19 20 21 22 23 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 ] CPU P-States [ 18 19 22 (23) 24 25 26 ] CPU P-States [ (12) 18 19 22 23 24 25 26 ] Link to comment Share on other sites More sharing options...
TheRacerMaster Posted May 3, 2017 Share Posted May 3, 2017 What's confusing is it's saying machdep.cpu.microcode_version: 20 machdep.cpu.cores_per_package: 16 machdep.cpu.logical_per_package: 32 This makes me wonder if it's linked to the error in clover boot log saying cpu number out of control? It dows give the correct core and thread count further up though? Also, Microcode version 20? My Bios says it's using microcode revision 14, which I verified by extracting with UBUtool. Is Mac OS X using their own microcode? Is this where things get messy? 0x14 = 20. 1 Link to comment Share on other sites More sharing options...
fluxus123 Posted May 3, 2017 Author Share Posted May 3, 2017 0x14 = 20. duh! of course it's hex! Thanks for pointing out.. I've been a plonker. do you know what the cores per package and logical per package is supposed to be? seems different to the cores and threads? Link to comment Share on other sites More sharing options...
Recommended Posts