From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Dave Jones" <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Ondemand/Conservative not working with 2.6.18
Date: Wed, 11 Oct 2006 22:08:57 +0300 [thread overview]
Message-ID: <200610112208.57136.caglar@pardus.org.tr> (raw)
In-Reply-To: <EB12A50964762B4D8111D55B764A8454B6C08C@scsmsx413.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
11 Eki 2006 Çar 22:00 tarihinde, Pallipadi, Venkatesh şunları yazmıştı:
> I guess I misunderstood the original issue. You have available_frequencies
> showing all the values and after you load ondemand, frequency remains at
> the highest, even though CPUs are idle. Is this correct?
Yes, thats the originial issue, no freq. changes at all.
> And everything above used to work fine with 2.6.16?
Yes, everything works fine with 2.6.16.
> 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?
I'll and report back.
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-11 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 19:00 Ondemand/Conservative not working with 2.6.18 Pallipadi, Venkatesh
2006-10-11 19:08 ` S.Çağlar Onur [this message]
2006-10-11 19:38 ` S.Çağlar Onur
2006-10-11 19:39 ` S.Çağlar Onur
2006-10-13 18:33 ` S.Çağlar Onur
-- strict thread matches above, loose matches on Subject: below --
2006-10-16 13:08 Pallipadi, Venkatesh
2006-10-16 20:29 ` S.Çağlar Onur
2006-10-09 23:35 Pallipadi, Venkatesh
2006-10-10 20:54 ` S.Çağlar Onur
2006-10-04 13:33 S.Çağlar Onur
2006-10-09 21:52 ` S.Çağlar Onur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200610112208.57136.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.