cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Torsten Wolf <t.wolf@tu-bs.de>
To: cpufreq@www.linux.org.uk
Subject: cpufreq - totally confused
Date: Tue, 11 Jan 2005 13:14:23 +0100	[thread overview]
Message-ID: <20050111121423.GA7426@rhea> (raw)

Hi!

Due to nasty USB problems on my Thinkpad 2722 (Banias 1.5GHz) I've
always switched to the most recent 'stable' kernel release. Up to now,
2.6.10 (debian source package) seems to solve my USB issues; alas! APM
no longer works. However, ACPI has become useable and nearly everything
seems to work right now; except the frequency scaling. With APM, cpufreq
cpmpiled into the kernel and cpudynd I had two frequencies: 600MHz and
1.5GHz. Yesterday, while configuring the ACPI stuff gkrellm showed
various other frequencies that seemed to correspond to the 8 throttling
stages indicated in /proc/acpi/processor/CPU/throttling. Unfortunately,
this nice behaviour somehow got lost and I am desperately trying to get
it back.

The cpufreq settings in .config are listed below; ACPI stuff has been
compiled as modules. Debians 2.6.10 has been patched with the latest
swsusp2. Looking at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
the lowest frequency is always 600MHz, while the value displayed
yesterday in gkrellm's x86info plugin was definitely lower. So please
give me a hint (which modules when to load; cpufreqd or cpudynd;...)
to be able to use the throttling. What further information do you need?

In the meantime I have the switching between 0.6 and 1.5GHz, but I hope
to reduce power consumption with additional lower frequencies.

Thanks in advance!

Best wishes,
Torsten

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_TABLE=m

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y

-----------------------------------------------------------------------

cat /proc/cpuinfo

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 9
model name      : Intel(R) Pentium(R) M processor 1500MHz
stepping        : 5
cpu MHz         : 598.160
cache size      : 1024 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov
pat clflush dts acpi mmx fxsr sse sse2 tm pbe est tm2
bogomips        : 1182.92

-----------------------------------------------------------------------

cat /proc/acpi/processor/CPU/throttling

state count:             8
active state:            T0
states:
   *T0:                  00%
    T1:                  12%
    T2:                  25%
    T3:                  37%
    T4:                  50%
    T5:                  62%
    T6:                  75%
    T7:                  87%

             reply	other threads:[~2005-01-11 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 12:14 Torsten Wolf [this message]
2005-01-11 12:48 ` cpufreq - totally confused Dominik Brodowski

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=20050111121423.GA7426@rhea \
    --to=t.wolf@tu-bs.de \
    --cc=cpufreq@www.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox