Contribute
Register

SpeedStep worked good in ML, get stucked in high step in Mavericks

Status
Not open for further replies.
hackatos

hackatos

Joined
Jun 1, 2013
Messages
84
Motherboard
HP ProBook 4540s
CPU
Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
Graphics
Intel HD 4000
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. Android
  2. iOS
Hi guys,

Maybe somebody have the same problem as me.
Generated SSDT with ProBook Installer, SMBIOS MacBookPro9,2 and MacBookPro10,2 tested with same results.
My CPU shows all the time 2.18 GHz (x22) in HWMonitor, even when am not doing anything from a long time it never goes back to 1.19 GHz (x12) (lower step), it reaches higher steps and turbo boost. :crazy:

Specs:
HP ProBook 4540s, i5-3230M CPU @ 2.60GHz.

I don't know what else to do, I am a little bit disappointed of this update.

P.D.
As I said in ML SpeedStep was working perfectly with both SMBIOS definitions.
 
HWMonitor has problems with Mavericks, sometimes it gets stuck at x22. Switching to other HWMonitor version can fix this, but I recommend using MSRDumper to check your PStates.
 
hackatos said:
Hi guys,

Maybe somebody have the same problem as me.
Generated SSDT with ProBook Installer, SMBIOS MacBookPro9,2 and MacBookPro10,2 tested with same results.
My CPU shows all the time 2.18 GHz (x22) in HWMonitor, even when am not doing anything from a long time it never goes back to 1.19 GHz (x12) (lower step), it reaches higher steps and turbo boost. :crazy:

Specs:
HP ProBook 4540s, i5-3230M CPU @ 2.60GHz.

I don't know what else to do, I am a little bit disappointed of this update.

P.D.
As I said in ML SpeedStep was working perfectly with both SMBIOS definitions.
Click to expand...

HwMonitor cannot be trusted. Check your states with DPCIManager, MSRDumper.kext, or AppleIntelCPUPowerManagementInfo.kext.
 
This is what shows MSRDumper:

HTML: 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30

Looks like in a loop from 12 to 22
 
hackatos said:
This is what shows MSRDumper:

HTML: 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:08.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:09.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:10.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper CoreMulti(22) 
10/27/13 5:26:11.000 PM kernel[0]: MSRDumper PStatesReached: 12 22 26 29 30

Looks like in a loop from 12 to 22
Click to expand...

Check in Activity Monitor. Something is using CPU resources... If this is early after your install/upgrade, then it is normal, there is lots of things OS X must do.
 
DPCIManager shows also the same behavior.

Mavericks is already running a few hours.
 
hackatos said:
DPCIManager shows also the same behavior.

Mavericks is already running a few hours.
Click to expand...

Like I said before, check Activity Monitor for processes using CPU resources...
 
Closed browser just HWMonitor is showing consuming CPU, between 0.6% and 1.0%.
 
hackatos said:
Closed browser just HWMonitor is showing consuming CPU, between 0.6% and 1.0%.
Click to expand...

And the pstates?

Close HwMonitor also... Just monitor with one of the other tools.
 
HWMoniter closed, no other hungry app, waited for a while and loaded MSRDumper.
HTML: 
10/27/13 6:05:23.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:23.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:23.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:24.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:24.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:24.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:24.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:25.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:25.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:25.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:25.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:26.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:26.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:26.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:26.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:27.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:27.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:27.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:27.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:28.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:28.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:28.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:28.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:29.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:29.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:29.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:29.000 PM kernel[0]: MSRDumper PStatesReached: 12 
10/27/13 6:05:30.000 PM kernel[0]: MSRDumper CoreMulti(12) 
10/27/13 6:05:30.000 PM kernel[0]: MSRDumper PStatesReached: 12

Without HWMonitor everything seems ok.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top