public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: linux-acpi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Brown, Len" <len.brown@intel.com>,
	cpufreq@lists.linux.org.uk, Dave Jones <davej@codemonkey.org.uk>
Subject: bug? acpi p-state + ondemand keeps dropping max freq
Date: Thu, 05 Jun 2008 15:30:56 -0700	[thread overview]
Message-ID: <48486920.4040006@intel.com> (raw)


I've consistently experienced the following bizarre problem since 2.6.20, all the
way up to 2.6.25.3 (regressed yesterday and each of these kernels exposes this
behaviour):

/sys/devices/system/cpu/cpu0/cpufreq # grep . *
affected_cpus:0
cpuinfo_cur_freq:800000
cpuinfo_max_freq:1866000
cpuinfo_min_freq:800000
scaling_available_frequencies:1866000 1600000 1333000 1066000 800000
scaling_available_governors:ondemand performance
scaling_cur_freq:800000
scaling_driver:acpi-cpufreq
scaling_governor:ondemand
scaling_max_freq:800000
scaling_min_freq:800000



Notice that scaling_mx_freq dropped down to the lowest possible value and as such
my CPU is only working at 800MHz. At boot time this field properly displays
1866MHz and everything works OK. After a certain period (?) this value drops down
and I cannot manually elevate it back to the normal level:

# echo 1866000 > scaling_max_freq ; cat scaling_max_freq
800000
# echo 1866000 > scaling_max_freq ; cat scaling_max_freq
800000


This renders my Dothan to utterly poor speeds. (standard T43)

performance cpufreq governor makes no difference - I still can't change the
frequency upper/lower values.

Auke

             reply	other threads:[~2008-06-05 22:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 22:30 Kok, Auke [this message]
2008-06-06  4:13 ` bug? acpi p-state + ondemand keeps dropping max freq Henrique de Moraes Holschuh
2008-06-06 16:34   ` Kok, Auke
2008-06-06 19:47     ` Henrique de Moraes Holschuh
2008-06-07  2:46 ` Len Brown
2008-06-07 23:22 ` Björn Steinbrink
     [not found] <20080606140846.GA9580@ucw.cz>
2008-06-07 21:39 ` Pavel Machek
2008-06-07 21:54   ` Arjan van de Ven
2008-06-07 23:36     ` Holger Macht
2008-06-09 16:39     ` Kok, Auke
2008-06-16 10:42     ` Pavel Machek
2008-06-16 14:43       ` Arjan van de Ven
2008-06-17  8:44         ` Pavel Machek
2008-07-05 19:49         ` Björn Steinbrink
2008-07-05 20:04           ` Björn Steinbrink
2008-06-17 18:15       ` Len Brown

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=48486920.4040006@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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