VoodooPower > Bug Reports
Constant errors, weird p-states with core i5-430m
(1/1)
piyokos:
Vostro 3700. Others are working on vanilla speedstepping but I wish to get the Voodoo implementation working. I can't really tell what's going on here besides the fact that something else is screwing around with the p-states, and VoodooPowerMini only detects one p-state (0) while many exist and it appears to bounce between them, although the Intel speedstepping kexts have been removed.
Attached is a copy of the vanilla linux-extracted DSDT, if that's of any help at all.
I'm going to try VoodooPowerAcpi soon but just to let you know there's an issue here.
--- Code: ---6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085BBC5] probe: 96: CPU Family 6 Model 37
6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085C6B6] probe: 259: P-state 0 - 0000
6/27/10 8:27:41 PM kernel Voodoo[0xFFFFFF7F8085C71E] probe: 262: Thresholds Upper 375/500 75 % Lower 125/500 25 %
6/27/10 8:27:41 PM kernel VoodooPowerMini 1.2 (C) 2009-10 Superhai, All Rights Reserved. May 1 2010 13:49:35 DEBUG 64 bit
--- End code ---
--- Code: ---6/27/10 9:04:02 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:02 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (447/500) = 89 % Trend Down Current P-State 0
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:07 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (427/500) = 85 % Trend Down Current P-State 0
6/27/10 9:04:12 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0011 expected 0000 (0)
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:12 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (429/500) = 85 % Trend Down Current P-State 0
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0011 expected 0000 (0)
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:17 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (419/500) = 83 % Trend Down Current P-State 0
6/27/10 9:04:22 PM kernel VoodooPowerMini: Failed to get full power management control of CPU
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:22 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (446/500) = 89 % Trend Down Current P-State 0
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BD17] event: 366: Lost control: State 0009 expected 0000 (0)
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BE19] event: 378: Setting P-State to 0
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130BEEA] event: 386: External power connected and battery good
6/27/10 9:04:27 PM kernel Voodoo[0xFFFFFF7F8130C35A] event: 457: Ticks: Idle (433/500) = 86 % Trend Down Current P-State 0
--- End code ---
piyokos:
Voodoopoweracpi
--- Code: ---6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F81320DEE] probe: 35: Find ACPI CPUs
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F81320F1C] probe: 51: Found 4 CPUs from ACPI, using 4 active CPUs
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F81320F59] probe: 53: Evaluating ACPI performace capabilities
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132108B] probe: 72: ControlRegister: ID 82 LEN 000C ASI 7F RBW 40 RBO 00 ASZ 00 ADR 0000000000000199
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F813211DD] probe: 88: StatusRegister: ID 82 LEN 000C ASI 7F RBW 10 RBO 00 ASZ 00 ADR 0000000000000199
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 0: FREQ 2262 PWR 3500 TLAT 10 BMLAT 10 CTL 0000000000000012 STS 0000000000000012
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 1: FREQ 2261 PWR 3125 TLAT 10 BMLAT 10 CTL 0000000000000011 STS 0000000000000011
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 2: FREQ 2128 PWR 2625 TLAT 10 BMLAT 10 CTL 0000000000000010 STS 0000000000000010
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 3: FREQ 1995 PWR 2250 TLAT 10 BMLAT 10 CTL 000000000000000F STS 000000000000000F
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 4: FREQ 1862 PWR 1875 TLAT 10 BMLAT 10 CTL 000000000000000E STS 000000000000000E
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 5: FREQ 1729 PWR 1625 TLAT 10 BMLAT 10 CTL 000000000000000D STS 000000000000000D
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 6: FREQ 1596 PWR 1375 TLAT 10 BMLAT 10 CTL 000000000000000C STS 000000000000000C
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 7: FREQ 1463 PWR 1125 TLAT 10 BMLAT 10 CTL 000000000000000B STS 000000000000000B
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 8: FREQ 1330 PWR 1000 TLAT 10 BMLAT 10 CTL 000000000000000A STS 000000000000000A
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F8132147A] probe: 122: PerformanceSupportedStates 9: FREQ 1197 PWR 875 TLAT 10 BMLAT 10 CTL 0000000000000009 STS 0000000000000009
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F81321668] probe: 134: PerformancePresentCapabilities 0
6/27/10 9:43:39 PM kernel Voodoo[0xFFFFFF7F81321735] probe: 149: Functional Fixed Hardware not supported in this version for now
--- End code ---
No indication if it's actually functioning or not after boot (no output beyond initial detection).
VoodooMonitor results in a KP.
Superhai:
i3/5/7 are really not supported, but I did some simple code for it, but no testing has been done. I will take a look at the intel docs, but it would be helpful if you post some MSR data. Most important is 0x198 and 0x199.
piyokos:
Thanks for the reply!
I'll post the reads for 0x198/0x199 when I get a chance to boot into Linux with msr-tools, unless you have a more convenient method.
Of course if you want me to test anything, just post it here and I'll get back to you ASAP.
Navigation
[0] Message Index
Go to full version