[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200610112238.03319.caglar@pardus.org.tr>
Date: Wed, 11 Oct 2006 22:38:00 +0300
From: "S.Çağlar Onur" <caglar@...dus.org.tr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
Cc: "Dave Jones" <davej@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Ondemand/Conservative not working with 2.6.18
11 Eki 2006 Çar 22:00 tarihinde, Pallipadi, Venkatesh şunları yazmıştı:
> Can you configure with CPU_FREQ_DEBUG and do "echo 5 >
> /sys/module/cpufreq/parameter/debug" before switching the governor to
> ondemand and see whether you see any messages in dmesg?
Here it is;
zangetsu cpufreq # echo 5 > /sys/module/cpufreq/parameters/debug
zangetsu cpufreq # echo "ondemand" > scaling_governor
zangetsu cpufreq # dmesg
...
cpufreq-core: setting new policy for CPU 0: 800000 - 1733000 kHz
freq-table: request for verification of policy (800000 - 1733000 kHz) for cpu
0
freq-table: verification lead to (800000 - 1733000 kHz) for cpu 0
freq-table: request for verification of policy (800000 - 1733000 kHz) for cpu
0
freq-table: verification lead to (800000 - 1733000 kHz) for cpu 0
cpufreq-core: new min and max freqs are 800000 - 1733000 kHz
cpufreq-core: governor switch
cpufreq-core: __cpufreq_governor for CPU 0, event 2
cpufreq-core: __cpufreq_governor for CPU 0, event 1
cpufreq-core: governor: change or update limits
cpufreq-core: __cpufreq_governor for CPU 0, event 3
Cheers
--
S.Çağlar Onur <caglar@...dus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists