Dotaz: Nefunguje scaling CPU na baterku a flash

[tomasi]

Ahoj, mam problem, ktery nevim jak trackovat:

konfigurace:

Laptop, 280.13 Nvidia Driver, Ubuntu 10.10, Linux dell-xps 3.0.0-0300-generic #201107220917 SMP Fri Jul 22 09:20:45 UTC 2011 x86_64 GNU/Linux

popis problemu:

na baterku a pri spusteni flashoveho videa/flashe nefunguje CPU scalling. CPU zustava na 1 GHz (Max 2.17 GHz). Po kliknuti na max speed nebo performace aplet nereaguje (mam dve ikony, kazdou pro cpu). Pri sitovem napajeni je vse v poradku.

otazka:

Stava se to nekomu? Jak to trackovat?

---

---

Odpovědi

[Semo]

Pravdepodobne s ti pri vytiahnuti napajania prepne z governoru ondemand (conservative) na powersave, ktory neskaluje, len stale sedi na najnizsej frekvencii. Over si to prikazom cpufreq-info.

[tomasi]

diky za tu utilitu, vypada to, ze se ?nejakym? zpusoben prepina sam od sebe. /vse bylo na baterku/

Co s tim userspace?
(jdu zkontrolovat nejake cteni... http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaai%2Fcpufreq%2FTheUserspaceGovernor.htm)

bio@dell-xps:|~$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1000 MHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:9.32%, 1.67 GHz:1.07%, 1.33 GHz:1.58%, 1000 MHz:88.03% (76603)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1000 MHz.
The governor "userspace" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:7.60%, 1.67 GHz:0.56%, 1.33 GHz:1.07%, 1000 MHz:90.78% (69018)

bio@dell-xps:|~$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 2.17 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:9.38%, 1.67 GHz:1.07%, 1.33 GHz:1.58%, 1000 MHz:87.97% (76826)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 2.17 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:7.65%, 1.67 GHz:0.56%, 1.33 GHz:1.06%, 1000 MHz:90.73% (69257)

[tomasi]

Co je crash_notes? Obsaguje to jen 11fc1a910

bio@dell-xps:|/sys/devices/system/cpu/cpu0$ ll
total 0
drwxr-xr-x 5 root root 0 2011-08-30 22:41 cache
drwxr-xr-x 3 root root 0 2011-08-30 22:16 cpufreq
drwxr-xr-x 6 root root 0 2011-08-30 22:41 cpuidle
drwxr-xr-x 2 root root 0 2011-08-30 22:41 thermal_throttle
drwxr-xr-x 2 root root 0 2011-08-30 22:41 topology
-r-------- 1 root root 4096 2011-08-30 22:41 crash_notes
lrwxrwxrwx 1 root root 0 2011-08-30 22:41 node0 -> ../../node/node0
bio@dell-xps:|/sys/devices/system/cpu/cpu0$

[tomasi]

a jeste dalsi zahada ...
Jak muze byt ondemand pouze:

<b>current policy: frequency should be within 1000 MHz and 1000 MHz.</b>
The governor<b> "ondemand"</b> may decide which speed to use
within this range.

bio@dell-xps:|~$ cpufreq-info
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: <b>frequency should be within 1000 MHz and 1000 MHz.</b>
The governor <b>"ondemand"</b> may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:9.66%, 1.67 GHz:1.09%, 1.33 GHz:1.59%, 1000 MHz:87.67% (89998)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 0 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 10.0 us.
hardware limits: 1000 MHz - 2.17 GHz
available frequency steps: 2.17 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
<b>current policy: frequency should be within 1000 MHz and 1000 MHz.</b>
The governor<b> "ondemand"</b> may decide which speed to use
within this range.
current CPU frequency is 1000 MHz.
cpufreq stats: 2.17 GHz:8.01%, 1.67 GHz:0.60%, 1.33 GHz:1.08%, 1000 MHz:90.32% (80819)

[Semo]

Asi ti tam bezi nejaky demon, ktory do toho saha podla napajania a/alebo zostavajucej stavy v baterke. Odpovodal by tomu ten userspace governor. A od nejakej urovne stavy sa asi prepne na ondemand, ale nedovoli mu vsetky frekvencii a zvrchu mu oreze moznosti.

V KDE je takymto demonom PowerDevil (niekde v Settings). V inych prostrediach a distribuciach si to budes musiet najst sam. Hladaj niekde v power managemente.

[tomasi]

vyreseno. Problem byl hardwaroveho razu. V baterce byl asi nejaky omezovac proudu (nastaven na nizkou hodnotu). Po vymene baterky funguje vse jak ma.