search

brucehuynhlee / xnu-speedstep

Automatically exported from code.google.com/p/xnu-speedstep
0 stars 0 forks source link

On HP nc6320 w/original (vanilla) 9.4 kernel, the frequency can only be lowered #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. install iDeneb v1 (10.5.4) onto HP nc6320, apply speedstep kernel
extension and tuxx_SpeedStep_improved_beta
2. the latter can lower the CPU's frequency to 1GHz (the fan stops the loud
whining), but won't raise it, even if forced (chosen manually), so the
machine becomes dog slow

What is the expected output? What do you see instead?
Upping and lowering the frequency as needed.

What version of the kext are you using? On what kernel and processor?
kext: 1.3.2, kernel: 9.4 vanilla, CPU: 2GHz Core 2 duo (second core
disabled from BIOS)

Please provide any additional information below.

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: INFO  On your processor, voltages can be changed in
16 mV steps
IntelEnhancedSpeedStep: INFO  Using 4 PStates.
IntelEnhancedSpeedStep: INFO  Initializing version 1.3.2 (C) Prashant
Vaibhav <mercurysquad@yahoo.com>
IntelEnhancedSpeedStep: DBG   FSB = 166 MHz
IntelEnhancedSpeedStep: DBG   Probing for Intel processor...
IntelEnhancedSpeedStep: DBG   Supported Intel processor found on your system
IntelEnhancedSpeedStep: DBG   Processor Family 6, Model 14
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 4 P-States
IntelEnhancedSpeedStep: DBG   P-State 0: 2000 MHz at 2796 mV, consuming 31
W, latency 110 usec
IntelEnhancedSpeedStep: DBG   P-State 1: 1667 MHz at 2796 mV, consuming 25
W, latency 110 usec
IntelEnhancedSpeedStep: DBG   P-State 2: 1333 MHz at 2796 mV, consuming 19
W, latency 110 usec
IntelEnhancedSpeedStep: DBG   P-State 3: 1000 MHz at 2796 mV, consuming 13
W, latency 110 usec
IntelEnhancedSpeedStep: INFO  Using 4 PStates.
IntelEnhancedSpeedStep: DBG   Throttling to PState 2
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x283
IntelEnhancedSpeedStep: DBG   Throttle done.
<this is when I try to set a higher frequency>
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
IntelEnhancedSpeedStep: DBG   Throttling to PState 0
IntelEnhancedSpeedStep: DBG   Starting throttle with CTL 0x83
IntelEnhancedSpeedStep: DBG   Throttle done.
hw.busfrequency: 664000000
machdep.cpu.address_bits.virtual: 32
machdep.cpu.address_bits.physical: 32
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: 1
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: 139808
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.cores_per_package: 1
machdep.cpu.extfeatures: XD
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE
MCA CMOV PAT CLFSH DS ACPI MMX FXSR SSE SSE2 SS TM SSE3 MON VMX EST TM2 TPR
PDCM
machdep.cpu.brand: 0
machdep.cpu.signature: 1768
machdep.cpu.extfeature_bits: 1048576 0
machdep.cpu.feature_bits: -1343620097 49577
machdep.cpu.stepping: 8
machdep.cpu.extfamily: 0
machdep.cpu.extmodel: 0
machdep.cpu.model: 14
machdep.cpu.family: 6
machdep.cpu.brand_string: Genuine Intel(R) CPU           T2500  @ 2.00GHz
machdep.cpu.vendor: GenuineIntel
Darwin finestra.local 9.4.0 Darwin Kernel Version 9.4.0: Mon Jun  9
19:30:53 PDT 2008; root:xnu-1228.5.20~1/RELEASE_I386 i386

In case you get kernel panic, boot up in single user mode (bootflag -s),
load the kext manually, and note down or take a photo of the kernel panic
message. Attach it as well.

Original issue reported on code.google.com by nagy.att...@gmail.com on 22 Aug 2008 at 8:08

GoogleCodeExporter commented 8 years ago 
From the logs it seems like yet another BIOS/ACPI problem (look at voltages: 
2.7 V). 
As mentioned, I am not working on fixing this because quite simply it can't be 
fixed. I suggest creating your own P-state table instead, or try updating your 
BIOS.

Original comment by mercurys...@gmail.com on 25 Aug 2008 at 12:44