What steps will reproduce the problem?
with 1.4.5 beta its just instantly after the boot.With 1.4.0 version its
hard to tell beacause is one time each two days that it happens, sometimes
daily :(
1.just run the commands and it not change, and when change, change for one
clock i didnt specifyed, i can change only the targetload without problems,
the clock change by itself after a random reboot the clock speed sometimes
goes to 1064 sometimes boot on 1733mhz, in my system profiler it reads
1,73ghz processor everytime, it is throtling the full speed aways to the
speed reported at system profile ?
i think yes by the way and this is good..just the esporadic kernel panics
are annoying me since if i get a gig to use this lap i cannot rely to much
on it.
2.i had sluttering in audio for the first time in 5 days as i wrote this
post and this is BAD real BAD im using this system dedicated to work in the
studio, but all UI smooth as a rock.
3.yes i can sleep resume just fine.
What is the expected output? What do you see instead?
im expecting no sluttering in audio (itunes/tracktor pro) no kernel panics
never from this kext... almost daily im having this issues (kernel panics).
What version of the kext are you using? On what kernel and processor?
1.4.0 on vanilla kernel 9.6.0 on Intel® Core(TM)2 Duo CPU T7250 @ 2.0ghz
Please provide any additional information below.
besides this problems the kext do its job in mantaining the processor cool
and when processor is needed its release the full speed, but never at the
2.0 ghz, thats a great thing the cpu doesnt burn, and i have an santa rosa
technology here so this down clock doesnt afect in nothing here the OS just
run smoother than before in with 4gb 667hz memory instaled on a SONY VAIO
VGN CR-220e.
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: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -235 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -519 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x70a
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -653 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x918
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -680 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -680 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -769 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -800 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -600 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -730 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -840 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -880 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -807 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -666 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -583 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -666 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -880 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -760 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -730 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -346 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -115 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -233 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -245 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -137 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -640 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x918
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -600 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -518 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -666 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -666 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -720 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -680 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -653 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -600 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -615 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -692 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -640 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -692 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -680 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -730 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -653 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -846 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -840 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -280 /10 pc
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -222 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x70a
IntelEnhancedSpeedStep: DBG Throttle done.
IntelEnhancedSpeedStep: DBG Autothrottle: CPU load -117 /10 pc
IntelEnhancedSpeedStep: DBG Starting throttle with CTL 0x401
IntelEnhancedSpeedStep: DBG Throttle done.
hw.busfrequency: 800000000
machdep.cpu.thread_count: 2
machdep.cpu.core_count: 2
machdep.cpu.address_bits.virtual: 48
machdep.cpu.address_bits.physical: 36
machdep.cpu.tlb.data_large: 32
machdep.cpu.tlb.inst_large: 8
machdep.cpu.tlb.data_small: 256
machdep.cpu.tlb.inst_small: 128
machdep.cpu.cache.size: 2048
machdep.cpu.cache.L2_associativity: 6
machdep.cpu.cache.linesize: 64
machdep.cpu.arch_perf.fixed_width: 40
machdep.cpu.arch_perf.fixed_number: 3
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: 1
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.microcode_version: 0
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: 1789
machdep.cpu.extfeature_bits: 537919488 1
machdep.cpu.feature_bits: -1075053569 58301
machdep.cpu.stepping: 13
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 Duo CPU T7250 @ 2.00GHz
machdep.cpu.vendor: GenuineIntel
Darwin TimDavila.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24
17:37:00 PST 2008; root:xnu-1228.9.59~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.
when i get the panic i should run "sudo dmesg | grep IntelEnhanced &&
sysctl hw.busfrequency && sysctl machdep.cpu && uname -a" again in the
single user mode? because my boot messages keeps upthere where i cannot
take a photo of it anymore. please guide me here first atempt to be an beta
tester, how i make a photo of the log from the kernel panic?.. thanks a lot
and keep this project going please !
all the best have a great new year all
Original issue reported on code.google.com by tim.dav...@gmail.com on 28 Dec 2008 at 2:09
Original issue reported on code.google.com by
tim.dav...@gmail.comon 28 Dec 2008 at 2:09