Jump to content

New version 1.1 of GenericCPUPowerManagement

Superhai

By Superhai,
in New Releases and Updates

 Share
625 posts in this topic

Recommended Posts

mitch_de
mitch_de
Posted
Posted
hello,

 

i don't know what's going on but with the new kext (the previous ones up to 1.19 used to work just fine) my lappy freezes at booting, or boots and then freezes after just 2 seconds. when i remove the kext everything returns back to normal.

 

one time i was able to write down the message that showed up during booting i'm not sure if it has something to do with the freezing anomaly:

 

your cpu supports only constant TSC but only in C0 and C1 will attempt to disable C2+ ststes

 

if u need any more info let me know

 

pls help

I dont know but perhaps its because auf not fitting mVolts ?

This part (VID settings) seems to be new in V1.1+ and different to V 1.0.19+.

 

EDIT: For SUPERHAI - my megadlon :)

I also found out that, even if OVERWRITE VID is set, and the code setup the min/max in the startup rountine

of the kext rigth, later it never switches to that own mVolts !

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Debug) Dec 3 2008 13:27:02 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 2660 MHz [0A-00] - 1325 mV [28]

GenericCPUPowerManagement: [Debug] P-State 1: 2394 MHz [09-00] - 1225 mV [20]

GenericCPUPowerManagement: [Debug] P-State 2: 2128 MHz [08-00] - 1125 mV [18]

GenericCPUPowerManagement: [Debug] P-State 3: 1862 MHz [07-00] - 1025 mV [10]

GenericCPUPowerManagement: [Debug] P-State 4: 1596 MHz [06-00] - 0925 mV [08]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0A28 TR 065

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0A28 TR 065

All mVolts at Pstates are OK (i set 925/1325 in plist, your app does made the steps between right , all OK) !!!

But later at trottling, the kext never uses them, only the highest 1325 for all other PSATES.

I am sure only a very little bug. (if you cant find the voltage setting bug in .kext, perhaps it an bug(s) in the control app?)

Thanks

ferywu
ferywu
Posted
Posted
Update on 3rd of December 2008

 

Version 1.1.1 of kext -> a few new features including T-States or stopclock throttling. Should give some more time out from the battery if not running resource heavy apps.

Now the GUI app is ready, and also the command line tool. Go to http://www.superhai.com/ to find downloads.

 

GenericCPUPowerManagement: [Debug] Initialization : Probe

GenericCPUPowerManagement: [Debug] Found 2 I/O Kit CPU's and 2 ACPI CPU's

GenericCPUPowerManagement: [Debug] AMD PN 060C0C0C 12060808

GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Debug) Dec 3 2008 07:35:21 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 2000 MHz [0C-00] - 1350 mV [08]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0000 TR 000

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0000 TR 000

GenericCPUPowerManagement: [Debug] Last loop used 0 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0133 P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] CPU 1 load 0134 highest P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] Last loop used 141 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0033 highest P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] CPU 1 load 0033 P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] Last loop used 89 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0008 P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] CPU 1 load 0010 highest P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] Last loop used 87 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0000 P-State 0 (approximate) and frequency 800

GenericCPUPowerManagement: [Debug] CPU 1 load 0004 highest P-State 0 (approximate) and frequency 800

 

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0xfffffffff4270ab4,"Profile"=0x0,"CPU"=({"Load"={"User"=0x4a,"Accumulated"=0x76,"System"=0x2c,"Idle"=0x388,"Nice"=0x0},"Clock Modulation"=0x0,"Frequency"=0x320,"Current P-State"=0x0,"DID"=0x0,"VID"=0x0,"Thermal Readout"=0x0,"FID"=0x0,"Voltage"=0x60e,"Exact"=No,"Name"="CPU1"},{"Load"={"User"=0x40,"Accumulated"=0x67,"System"=0x27,"Idle"=0x397,"Nice"=0x0},"Clock Modulation"=0x0,"Frequency"=0x320,"Current P-State"=0x0,"DID"=0x0,"VID"=0x0,"Thermal Readout"=0x0,"FID"=0x0,"Voltage"=0x60e,"Exact"=No,"Name"="CPU2"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Current Latency"=0x64,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes,"Routine Payload TSC"=0x32fd4}

"Characteristics" = {"Voltage Highest"=0x546,"Signature"=0x20fb1,"CPU Count"=0x2,"Build Date"="Dec 3 2008","Constant TSC"=No,"Voltage Lowest"=0x546,"VID Lowest"=0x8,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.1","Individual Core Control"=No,"Frequency Lowest"=0x7d0,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x1,"Mobile CPU"=No,"Build Time"="07:35:21","Auto Throttle On Startup"=Yes,"Build Config"="Debug","Frequency Highest"=0x7d0,"String"="AMD Athlon 64 X2 Dual Core Processor 3800+","DID Highest"=0x0,"FID Lowest"=0xc,"VID Highest"=0x8,"FID Highest"=0xc,"P-State Count"=0x0}

 

GenericCPUPowerManagement.kext 1.1.1 (Debug) Dec 3 2008 07:35:21

CPU: 2 x Desktop AMD Athlon 64 X2 Dual Core Processor 3800+ (20fb1)

P-States: 1 - Frequency 2000 MHz -> 2000 MHz - Voltage 1350 mV -> 1350 mV

[0c-00-08] -> [0c-00-08]

Auto throttle on at startup: true, Voltage Override: false, Timer: 250 ms

 

Darwin Kernel Version 9.5.0: Wed Nov 26 22:39:57 PST 2008; Voodoo; RC1 :xnu-1228.7.58/BUILD/obj/RELEASE_I386

 

18 9 0x1ad9c000 0x4000 0x3000 com.apple.iokit.IOACPIFamily (1.2.0) <12>

19 3 0x1adeb000 0x3d000 0x3c000 com.apple.driver.AppleACPIPlatform (1.2.1) <18 17 12 7 5 4>

29 0 0x20bf3000 0x3000 0x2000 com.apple.driver.AppleACPIPCI (1.2.1) <19 18 17 12>

32 0 0x20d53000 0x2000 0x1000 org.tgwbd.driver.ACPIPS2Nub (1.0.0d1) <19 18 12>

42 0 0x2125c000 0x4000 0x3000 com.apple.driver.AppleACPIButtons (1.2.1) <22 19 18 7 6 5 4 2>

61 0 0x20e84000 0xc000 0xb000 com.apple.driver.ACPI_SMC_PlatformPlugin (3.1.6d0) <60 59 18 17 12 7 6 5 4>

20 0 0x1ae4d000 0x2000 0x1000 net.osrom.kext.IntelCPUPMDisabler (1.0.0) <12>

23 0 0x1afde000 0x1a000 0x19000 com.apple.driver.AppleIntelCPUPowerManagement (9.39.0) <12 7 6 5 4 2>

88 0 0x20dad000 0xc000 0xb000 com.superhai.driver.GenericCPUPowerManagement (1.1.1) <18 12 7 5 4 2>

28 0 0x20aa2000 0x5000 0x4000 com.apple.driver.AppleSMBIOS (1.0.14) <12>

 

hw.cpufrequency_max: 2000000000

hw.cpufrequency_min: 2000000000

hw.cpufrequency: 800000000

 

That's all

Thank you

parabol4
parabol4
Posted
Posted

Hi there,

I don't believe GenericCPUPowerManagement 1.1 detects the right frequency of my Intel Core Duo T2050 at 2x 1,60Ghz.

These are the debug logs:

sudo dmesg | grep GenericCPUPowerManagement

GenericCPUPowerManagement: [Warning] Your CPU supports constant TSC but only in C0 and C1, will attempt to disable C2+ states
GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Release) Dec  3 2008 07:35:16 [1050]
GenericCPUPowerManagement: (C) 2008 Superhai, All Rights Reserved

 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics" 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Characteristics"  
   "Characteristics" = {"Voltage Highest"=0x4ee,"Signature"=0x6e8,"CPU Count"=0x2,"Build Date"="Dec  3 2008","Constant TSC"=Yes,"Voltage Lowest"=0x3b6,"VID Lowest"=0x13,"Product Name"="GenericCPUPowerManagement.kext","Override"=No,"Version"="1.1.1","Individual Core Control"=No,"Frequency Lowest"=0x96,"DID Lowest"=0x0,"Timer Timeout"=0xfa,"CPU Driver"=0x0,"Mobile CPU"=Yes,"Build Time"="07:35:16","Auto Throttle On Startup"=Yes,"Build Config"="Release","Frequency Highest"=0x12c,"String"="Genuine Intel(R) CPU		   T2050  @ 1.60GHz","DID Highest"=0x0,"FID Lowest"=0x6,"VID Highest"=0x2c,"FID Highest"=0xc,"P-State Count"=0x6}

 

ioreg -lxw0 -r -c GenericCPUPowerManagement | grep "Status"

"Status" = {"Threshold"=0xc8,"Wait Time TSC"=0x17c868f0,"Profile"=0x0,"CPU"=({"Load"={"User"=0x0,"Accumulated"=0x0,"System"=0x0,"Idle"=0x400,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0xfa,"Current P-State"=0x2,"DID"=0x0,"VID"=0x23,"Thermal Readout"=0x21,"FID"=0xa,"Voltage"=0x47e,"Exact"=Yes,"Name"="CPU0"},{"Load"={"User"=0x0,"Accumulated"=0x0,"System"=0x0,"Idle"=0x400,"Nice"=0x0},"Clock Modulation"=0x400,"Frequency"=0xfa,"Current P-State"=0x2,"DID"=0x0,"VID"=0x23,"Thermal Readout"=0x21,"FID"=0xa,"Voltage"=0x47e,"Exact"=Yes,"Name"="CPU1"}),"Timer Timeout (ms)"=0xfa,"P-State Limit"=0x0,"P-State Capability"=0x0,"Current Latency"=0x6,"Kernel Extension Ready"=Yes,"Hysteresis"=0x32,"Auto Throttle Running"=Yes,"Routine Payload TSC"=0x266f4}

 

Can you explain this, Superhai?

Is there some way to fix it with the correct frequency min end max?

 

Thanks in advance

Superhai
Superhai
Posted
  • Author
Posted
your cpu supports only constant TSC but only in C0 and C1 will attempt to disable C2+ ststes

if u need any more info let me know

pls help

 

Boot into single user mode (use -s option) and post me the output from the kernel panic (picture is maybe easiest)

 

Hope that helps a bit ...

Goron

 

Use the newest version instead. You use an old version.

 

Can you explain this, Superhai?

Is there some way to fix it with the correct frequency min end max?

 

Check which smbios.kext you use, the fsb is wrong.

 

The newest 1.1.1 works now without the problem of v1.1 which wont go down to slowest MHZ.

It now stays also at my slowest 1596 MHZ if CPU load is less. Last version stays onyl at 1800 MHZ.THANKS

(Has it to do with new value Tstate is not set in AC (i only use AC, desktop) ?

 

T-State is a new option which I dont set for AC, it will not change behavior except when you set this option. It is on default for battery, saves some more power if you run in lowest P-State.

U.C.
U.C.
Posted
Posted

I have a MSI Wind and till now 1.0.2.0 Version of your kext worked great. But I just installed 1.1.1 (the latest one on your site) n the machine just kernel panics.

 

Using Vanilla kernel, Vanilla SMBIOS and SMBIOS EFI. Also the FSB has been manually set to 133.

Superhai
Superhai
Posted
  • Author
Posted
I have a MSI Wind and till now 1.0.2.0 Version of your kext worked great. But I just installed 1.1.1 (the latest one on your site) n the machine just kernel panics.

 

I can´t thelp you if you don´t post me the kernel panic screen. (The verbose one)

jinnggoff
jinnggoff
Posted
Posted

hai superhai, sorry because i dont have camera, i write kp screen with wind :

kernel loadable modules in backtrace (with dependencies):

com.superhai.driver.genericcpupowermanagement (1.1.1)@0x4c25b000->0x4c263fff

depency: com.apple.iokit.IOACPIFamily(1.2.0)@0x2eb98000

thanks.

Superhai
Superhai
Posted
  • Author
Posted
hai superhai, sorry because i dont have camera, i write kp screen with wind :

kernel loadable modules in backtrace (with dependencies):

com.superhai.driver.genericcpupowermanagement (1.1.1)@0x4c25b000->0x4c263fff

depency: com.apple.iokit.IOACPIFamily(1.2.0)@0x2eb98000

thanks.

 

Thanks, but you write that part of the panic screen I don't have use for. I need everything above of those lines. Anyway you can try the newest download version, I removed the CState remove routine, because it seem to need different bits set for the different core models.

jinnggoff
jinnggoff
Posted
Posted

I've tried the last version, but still Kp

This part of above the writing Kp

Panic (CPUs 0x001a8cec Caller 1): kernel trap at 0x4d4c123b, type 13 = general protection, Registers:

CR0: 0X8001003B, CR2 0X001030E8, CR3 0X01b2d000, CR4 0X000006E0

EAX 0xffffffef, EBX 0x0000019a, ECX 0x0000019a, EDX 0xffffffff

CR2 0x3cf27cfc, EBP 0x3cf27d48, ESI 0x00000000, 0x00000001 EDI

EFL 0x00010082, EIP 0x4d4c123b, CS 0x00000008, DS 0x3cf20010

error code: 0x00000000

thanks

Superhai
Superhai
Posted
  • Author
Posted
EAX 0xffffffef, EBX 0x0000019a, ECX 0x0000019a, EDX 0xffffffff

 

I c... seem like atom cpus dont support the tstates... or i make a mistake in the code... have to check... will you try to disable the TStateThrottle option (change to false from true) in the profiles and see if it works again then...

 

Getting panic with 1.1.1 on M1530 with T8300. 1.1 is working fine.

If the pic is too blurry, I can take another one.

 

It is the same issues, it is the t-state throttle. I just wish Intel could have the same config on all their cpu's...

mitch_de
mitch_de
Posted
Posted

SUPERHAI - my megadlon , please can you look at that VID trottle bug ?

I also found out that, even if OVERWRITE VID is set, and the code setup the min/max in the startup rountine

of the kext rigth, later it never switches to that own mVolts !

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Debug) Dec 3 2008 13:27:02 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 2660 MHz [0A-00] - 1325 mV [28]

GenericCPUPowerManagement: [Debug] P-State 1: 2394 MHz [09-00] - 1225 mV [20]

GenericCPUPowerManagement: [Debug] P-State 2: 2128 MHz [08-00] - 1125 mV [18]

GenericCPUPowerManagement: [Debug] P-State 3: 1862 MHz [07-00] - 1025 mV [10]

GenericCPUPowerManagement: [Debug] P-State 4: 1596 MHz [06-00] - 0925 mV [08]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0A28 TR 065

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0A28 TR 065

All mVolts at Pstates are OK (i set 925/1325 in plist, your app does made the steps between right , all OK) !!!

So the init part of the lastest kext reads the vid settings right and also should setup it for trotthling right.

BUG:

But later at autotrottling, the kext never uses them, only the highest 1325 for all other PSATES.

Means: autotrottling works, but never lowers the VID togehter with MHZ.

Also the command app only shows 1325:1325 (version before was 1212:1212 which was complety wrong)

I am sure only a very little bug in the part of the set MHZ/set VID function.

V 1.0.20 uses all those VIDS.

 

Thanks

Superhai
Superhai
Posted
  • Author
Posted
the last edition of kext do a kernel panic on my E8400 have a solution?

 

Seem like newer intel cpus panic on T-States, which is odd because intel says thats an architectural feature. Can you see if the panic always comes on cpu 1? Or also on cpu 0? Anyway you can turn it off.

mitch_de
mitch_de
Posted
Posted

Hi, i also tried newest 1.1.1 (i am that with the VID not trothhled problem, all info some post before).

 

Problems stay:

1. kextload, some throttleing then: stays at PSTATE slowest +1 even near no Load (see shoot)

2. VIDs didnt change (sometimes for short time 1187 mV - not in PSTATE VID-array, maybe from gigabyte EP35 board made itself)

 

enericCPUPowerManagement: [Debug] Initialization : Probe

GenericCPUPowerManagement: [Debug] Found 2 I/O Kit CPU's and 4 ACPI CPU's

GenericCPUPowerManagement: [Debug] Your CPU supports constant TSC but only in C0 and C1, you should disable C2+ states

GenericCPUPowerManagement: [Debug] Minimum VID Probe

GenericCPUPowerManagement: [Debug] Minimum VID Probe Complete : 28

GenericCPUPowerManagement: [Debug] Intel 06000A28 0A280A28

GenericCPUPowerManagement: [Debug] CPU Hardware Driver Setup Complete

GenericCPUPowerManagement: [Debug] Initialization : Start

GenericCPUPowerManagement: GenericCPUPowerManagement.kext 1.1.1 (Debug) Dec 4 2008 19:08:32 [1050]

GenericCPUPowerManagement: © 2008 Superhai, All Rights Reserved

GenericCPUPowerManagement: [Debug] P-State 0: 2660 MHz [0A-00] - 1325 mV [28]

GenericCPUPowerManagement: [Debug] P-State 1: 2394 MHz [09-00] - 1225 mV [20]

GenericCPUPowerManagement: [Debug] P-State 2: 2128 MHz [08-00] - 1125 mV [18] VIDs all OK but never used ?!

GenericCPUPowerManagement: [Debug] P-State 3: 1862 MHz [07-00] - 1025 mV [10] That VIDs work in V 1.0.20

GenericCPUPowerManagement: [Debug] P-State 4: 1596 MHz [06-00] - 0925 mV [08]

GenericCPUPowerManagement: [Debug] CPU 0: CTL 0A28 TR 064

GenericCPUPowerManagement: [Debug] CPU 1: CTL 0A28 TR 063

GenericCPUPowerManagement: [Debug] Last loop used 0 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0020 highest P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0020 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

GenericCPUPowerManagement: [Debug] Last loop used 114 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0018 highest P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] CPU 1 load 0013 P-State 0 (exact) and frequency 2660

GenericCPUPowerManagement: [Debug] AutoThrottle - from 0 to 4 - Requesting 0608

GenericCPUPowerManagement: [Debug] Last loop used 167 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0005 P-State 4 (approximate) and frequency 1596

GenericCPUPowerManagement: [Debug] CPU 1 load 0010 highest P-State 4 (approximate) and frequency 1596

bash-3.2# dmesg

 

Would it be possible to add an debug output for VID (VID or mVolts , doesnt matter) throttling in debug out ?

 

 

But with that version i get some interesting debug out (time as it should throtthle down to 1596 MHZ (slowest), stays at 18xx MHZ

 

I never seen got userland request before.

enericCPUPowerManagement: [Debug] CPU 1 load 0010 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Last loop used 103 us

GenericCPUPowerManagement: [Debug] CPU 0 load 0013 P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] CPU 1 load 0018 highest P-State 4 (approximate) and frequency 1862

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Got userland request

GenericCPUPowerManagement: [Debug] Last loop used 103 us

 

Thanks

Bild_113.jpg

aliasa_anderson
aliasa_anderson
Posted
Posted
Uploaded new version of 1.1.1, hope it is not panicing now.

 

 

Superhai,

 

Just wanted to know,how is this kext different from AppleIntelCPUPowermanagement kext in principle.

I know that the AppleIntelCPUPowermanagement.kext causes a kp without fixed HPET,so did you modify its sources to remove HPET dependency ?

what about its differences with the speedstep kext by Mercurysquad ?

mitch_de
mitch_de
Posted
Posted
Superhai,

 

Just wanted to know,how is this kext different from AppleIntelCPUPowermanagement kext in principle.

I know that the AppleIntelCPUPowermanagement.kext causes a kp without fixed HPET,so did you modify its sources to remove HPET dependency ?

what about its differences with the speedstep kext by Mercurysquad ?

I answer what i know:

1. AppleIntelCPUPowermanagement kext didngt use speedstep function (Intel CPU, buildin), does throttle other way

2. This .kext also supports AMDs Cool&Quit;) , which is not supported by Mercurysquad

3. On Intel (with speedstep CPU + Speedstep in BIOS enabled) both, this + Mercurysquad work near same, this has also an

Tool for showing MHZ+VID+TEMP (also in Menue).

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...