3 ms·
Had the exact same problem (minus the spilled tea, but I'm often running my computer very hot so I'm not surprised) on OS 10.8 on a 2011 (?) MBP, and did exactl
by btown 13y ago
Had the exact same problem (minus the spilled tea, but I'm often running my computer very hot so I'm not surprised) on OS 10.8 on a 2011 (?) MBP, and did exactly this to fix it. I verified that the problem was with some sort of IntelACPI... [sic] module using a DTrace script (been a while but I can try to find it if anyone wants... basically that module was using up a large amount of CPU whenever there was load, such as when I launched a game. Long story short, the step-by-step to fix it is here:
http://www.rdoxenham.com/?p=259 http://www.rdoxenham.com/?p=259 (cached: http://webcache.googleusercontent.com/search?q=cache:UPanIg_jwKQJ:www.rdoxenham.com/%3Fp%3D259&hl=en&gl=us&strip=1 http://webcache.googleusercontent.com/search?q=cache:UPanIg_... )
Been working like a charm for about 13 months now, and it's survived multiple minor 10.8.x upgrades since then. YMMV may vary with 10.9, and since they supposedly changed power management, I wouldn't touch that upgrade with a [Mac OS] 10 foot pole.
- code_duck 13y agoThe fix for me was to simply delete the power profile from my MacBook model in a kext config directory. Everything was fine until I upgraded to 10.8.5, and then to my system would not boot at all – feeling with the kernel panic very early in booth that had something to do with AppleIntelCpuPowerManagement.kext. I completely reinstalled and install Mavericks, and then repeated the original fix. It worked fine and my system is doing great running Mavericks.
- code_duck 13y agoUh, "feeling with the kernel panic very early in booth" meaning, boot failed with a kernel panic. I was kind of confused by what I read about power management having been changed in Mavericks, but it turned out that whatever is relevant to this issue has not changed. As I noted the same solution fixed the same problem.