Can not switch to the higher frequency of Core2Duo.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I'm running 10.5.5 on a GA-965P-DS4 board with a Core2Duo E6400.
2. I'm using the voodoo 9.5.0 kernel (alpha13, currently) -- 
http://groups.google.com/group/xnu-dev/web/voodoo-9-5-0-kernel
3. I installed IntelEnhancedSpeedStep_1.3.2.kext and 
tuxx_SpeedStep_improved_beta

My CPU can do 1600 MHz and 2133 MHz. I cannot get it to go 2133 MHz.
When using the SpeedStep GUI in "custom mode" nothing happens when I select 
2133 MHz - it 
just stays at 1600.
When I try via sysctl, it doesn't work either.

Here's some info:
# sysctl -a |grep throttle
kern.exec: unknown type returned
kern.cputhrottle_curfreq: 1600
kern.cputhrottle_curvolt: 1340
kern.cputhrottle_freqs: 1600 2133 
kern.cputhrottle_factoryvolts: 1564 1564 
kern.cputhrottle_ctl: 1576

# sysctl -w kern.cputhrottle_curfreq=2133
kern.cputhrottle_curfreq: 1600 -> 1600

# sysctl -a kern.cputhrottle_curfreq     
kern.cputhrottle_curfreq: 1600

What version of the kext are you using? On what kernel and processor?

see above.

Please turn on DebugMessages in the Info.plist, reload the kext and try to 
reproduce the 
problem. Attach output of this command:
sudo dmesg | grep IntelEnhanced && sysctl hw.busfrequency && sysctl machdep.cpu 
&& uname -
a

IntelEnhancedSpeedStep: INFO  Initializing version 1.3.2 (C) Prashant Vaibhav 
<mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG   FSB = 266 MHz
IntelEnhancedSpeedStep: DBG   Probing for Intel processor...
IntelEnhancedSpeedStep: DBG   Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG   Processor Family 6, Model 15
IntelEnhancedSpeedStep: DBG   Starting
IntelEnhancedSpeedStep: INFO  On your processor, voltages can be changed in 16 
mV steps
IntelEnhancedSpeedStep: DBG   Using data from CPU0
IntelEnhancedSpeedStep: DBG   Found 2 P-States
IntelEnhancedSpeedStep: DBG   P-State 0: 2133 MHz at 1564 mV, consuming 88 W, 
latency 160 
usec
IntelEnhancedSpeedStep: DBG   P-State 1: 1600 MHz at 1564 mV, consuming 59 W, 
latency 160 
usec
IntelEnhancedSpeedStep: INFO  Using 2 PStates.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x36
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x36
IntelEnhancedSpeedStep: DBG   Throttle done.
hw.busfrequency: 1064000000
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.cache.size: 2048
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.linesize: 64
machdep.cpu.arch_perf.fixed_width: 0
machdep.cpu.arch_perf.fixed_number: 0
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.width: 40
machdep.cpu.arch_perf.number: 2
machdep.cpu.arch_perf.version: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.dynamic_acceleration: 0
machdep.cpu.thermal.sensor: 1
machdep.cpu.mwait.sub_Cstates: 32
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.cores_per_package: 2
machdep.cpu.logical_per_package: 2
machdep.cpu.extfeatures: XD EM64T
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 SSE3 MON DSCPL VMX EST TM2 
SSSE3 
CX16 TPR PDCM
machdep.cpu.brand: 0
machdep.cpu.signature: 1778
machdep.cpu.extfeature_bits: 537919488 1
machdep.cpu.feature_bits: -1075053569 58301
machdep.cpu.stepping: 2
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 15
machdep.cpu.family: 6
machdep.cpu.brand_string: Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz
machdep.cpu.vendor: GenuineIntel
Darwin xxxx 9.5.0 Darwin Kernel Version 9.5.0: Thu Sep 25 05:59:23 IST 2008; 
Voodoo; based 
on ToH:xnu-1228.7.58/BUILD/obj/RELEASE_I386 i386

Original issue reported on code.google.com by seb.k...@gmail.com on 25 Sep 2008 at 9:46

[GoogleCodeExporter]

This is possibly related to N/2 bus ratio. A fix should be available in the 
next version.

Original comment by mercurys...@gmail.com on 27 Sep 2008 at 11:39

• Changed state: Started
• Added labels: Component-KextLogic, KextLogic-Nby2, PlatformSupport, Usability

[GoogleCodeExporter]

Yes i have the same problem. I have the option of 1200 or 1600 and i cant 
change to
1600. But im looking forward to using the next version.

Original comment by jmotyka07 on 29 Sep 2008 at 5:32

[GoogleCodeExporter]

Possibly due to the high voltage reported by your BIOS/ACPI. It reports 1564 mV 
but current voltage (and also 
probably the max) is 1340 mV, so the CPU is rejecting the p-state change 
request. Work-around is going to be 
available for a future version.

Original comment by prashant...@gmail.com on 19 Oct 2008 at 1:24

• Added labels: Component-ACPI
• Removed labels: KextLogic-Nby2

[GoogleCodeExporter]

Thanks for looking into this! I'm looking forward for the new version!

Original comment by seb.k...@gmail.com on 19 Oct 2008 at 4:49

[GoogleCodeExporter]

I tried the new v1.4.5 but the problem still persists.

Original comment by seb.k...@gmail.com on 23 Nov 2008 at 9:46