UME does not have GV3 (EIST)

Bug #268626 reported by CheonwoeiNg
2
Affects Status Importance Assigned to Milestone
Ubuntu Mobile Edition
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu UME does not have GV3. cpufreq is not present in the folder /sys/devices/system/cpu/cpu0.

Tested with 8.04.1a, 8.04PV(updated to 2.6.24-19), RC2(2.6.24-18-lpia) and Beta4(2.6.24.16-lpia). All versions of UME does not have GV3.

Checked config-2.6.24-18-lpia, CONFIG_X86_SPEEDSTEP_CENTRINO=m and CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y

cpufreq_ondemand.ko and freq_table.ko are available in /lib/modules/2.6.24-*-lpia/kernel/drivers/cpufreq, but both modules are NOT loaded during system boot.

Tried to modprobe cpufreq_ondemand.ko and both modules get loaded. But Enhanced Intel Speed Technology (GV3 or EIST) still not working, don't see the scaling frequency table folder "cpufreq" in /sys/devices/system/cpu/cpu*

UME will run only Lowest Frequency (Ratio 0x6)without EIST.

Without the feature enabled, CPU frequency will not change and always stays at minimum CPU frequency. If UME has this working, the CPU frequency will change up/down according to the workload or user-select depends on what scaling governor is being chosen.

This means that a customer will never be running the CPU at the rated frequency, i.e. the frequency he bought the part at. For example a 1.0Ghz Silverthone part will only be running at 0.6Ghz.

Revision history for this message
Loïc Minier (lool) wrote :

upon boot, /proc/cpuinfo shows two logical CPUs with:
model name : Genuine Intel(R) CPU @ 1.33GHz
cpu MHz : 1330.060

I launched powertop and saw:
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 1.7%)
C1 0.0ms ( 0.0%)
C2 0.2ms ( 0.0%)
C3 0.6ms ( 0.0%)
C4 20.8ms (98.3%)

so effectively C states are changing, and not P states (frequency).

I think this is thanks to the cpuidle driver (acpi_idle).

I loaded acpi-cpufreq, and as soon as it was loaded I got /sys/devices/system/cpu/cpu*/cpufreq/ dirs which would say:
scaling_governor:
ondemand

cpuinfo_cur_freq:
800000

and /proc/cpuinfo would then say:
model name : Genuine Intel(R) CPU @ 1.33GHz
cpu MHz : 800.000

and powertop:
Cn Avg residency P-states (frequencies)
C0 (cpu running) ( 2.0%) 1333 Mhz 0.0%
C1 0.0ms ( 0.0%) 1067 Mhz 0.0%
C2 0.3ms ( 0.0%) 800 Mhz 100.0%
C3 1.9ms ( 0.1%)
C4 21.9ms (97.9%)

Revision history for this message
Loïc Minier (lool) wrote :

My personal conclusion is that the current setup works as designed: power will be saved by entering lower C states and frequency is at the maximum (boot default), unless you load a frequency governor.

If you're not seeing this behavior, please report on which hardware; I tested on a menlow crownbeach.

Changed in ubuntu-mobile:
status: New → Invalid
Changed in ubuntu-mobile:
status: Invalid → Confirmed
Revision history for this message
CheonwoeiNg (cheon-woei-ng) wrote :

Loic,
Steve Magoun said his MID image has 2 governors available: ondemand and performance.
The ondemand governor is the default, and the user does not need to run modprobe to enable the governor.

So, the current setup does not works as designed. Please provide fix to match the minimum MID configuration. Thanks!

Revision history for this message
Loïc Minier (lool) wrote :

mobile.hardy seed updated to pull powernowd for mobile. NB: mid and mobile seeds in mobile.intrepid updated as well.

Pushed to ubuntu-mobile ppa.

Changed in ubuntu-mobile:
status: Confirmed → Fix Committed
Revision history for this message
Loïc Minier (lool) wrote :

I'm confident that it will be fine as MIC is using apt-get, but there's a chance that this doesn't make it in the next images if Recommends aren't honored.

If this is the case, I'll promote the dep to a Depends, but it really should be fine as a Recommends.

Revision history for this message
Loïc Minier (lool) wrote :

Pushed to mobile archive. Update the ubuntu-mobile meta-package to get the update/fix.

(NB: Effective immediately, and of course also after reboot.)

Changed in ubuntu-mobile:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.