- Joined
- Feb 2, 2010
- Messages
- 8,181
- Motherboard
- ASUS TUF Z390-PRO GAMING - 2606 - UEFI
- CPU
- i9-9900K
- Graphics
- Vega 64
- Mac
- Classic Mac
- Mobile Phone
The best way to test for SpeedStep working is View attachment MSRDumper.kext.zip a kernel extension for reading the Machine Specific Register (MSR) that contains the current P-state and logging it.
The downside to this kext is that if you continue to run it for a long time it will fill up your kernel log file. When the log file reaches 1000K it's rolled over and is saved off and another log file is created. Eventually you could fill up a significant amount of disk space. Based on that I will document how to run it on demand and how to unload.
The first thing you need to do is change ownership of the kext. In Terminal you need to go to the directory that contains the unzipped attachment and run the following command:
Then when you want to run MSRDumper type the following command in Terminal in the directory that contains MSRDumper:
Then in the Console application click on kernel.log and you will see entries like the following:
MSRDumper CoreMulti(31) shows that the current P-state is 31 and
MSRDumper PStatesReached: 8 11 15 19 23 25 26 27 28 29 30 31 33 34 shows all the P-states seen since the kext was loaded.
Be patient when first running MSRDumper as it takes awhile to see multiple P-states. You might need to run some programs to change states.
To stop MSRDumper run the following command in Terminal in the same directory as the kext is located:
The downside to this kext is that if you continue to run it for a long time it will fill up your kernel log file. When the log file reaches 1000K it's rolled over and is saved off and another log file is created. Eventually you could fill up a significant amount of disk space. Based on that I will document how to run it on demand and how to unload.
The first thing you need to do is change ownership of the kext. In Terminal you need to go to the directory that contains the unzipped attachment and run the following command:
Code:
sudo chown -R 0:0 MSRDumper.kextThen when you want to run MSRDumper type the following command in Terminal in the directory that contains MSRDumper:
Code:
sudo kextload MSRDumper.kextThen in the Console application click on kernel.log and you will see entries like the following:
Code:
May 12 20:30:02 MacMans-MacBook-Pro kernel[0]: MSRDumper CoreMulti(31)
May 12 20:30:02 MacMans-MacBook-Pro kernel[0]: MSRDumper PStatesReached: 8 11 15 19 23 25 26 27 28 29 30 31 33 34
May 12 20:30:02 MacMans-MacBook-Pro kernel[0]: MSRDumper CoreMulti(31)
May 12 20:30:02 MacMans-MacBook-Pro kernel[0]: MSRDumper PStatesReached: 8 11 15 19 23 25 26 27 28 29 30 31 33 34
Note: These log entries are from my Early 2011 MacBook Pro.MSRDumper CoreMulti(31) shows that the current P-state is 31 and
MSRDumper PStatesReached: 8 11 15 19 23 25 26 27 28 29 30 31 33 34 shows all the P-states seen since the kext was loaded.
Be patient when first running MSRDumper as it takes awhile to see multiple P-states. You might need to run some programs to change states.
To stop MSRDumper run the following command in Terminal in the same directory as the kext is located:
Code:
sudo kextunload MSRDumper.kext
