cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12)
Date: Tue, 11 Mar 2014 03:26:14 +0000	[thread overview]
Message-ID: <bug-58001-12968-dclWEokGkp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-58001-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=58001

--- Comment #13 from Raymond Auge <rotty3000@gmail.com> ---
Effectively, I have exactly the same issue as outlined above. The 'ondemand'
governor never reacts to changes in system load, no matter what the system is
doing.

However, the other governors all work perfectly. I generally place my machine
in 'conservative' and that seems to work fine. When I'm going a build and need
more power I switch to performance.

the output of cpufreq-info is:

cpufrequtils 008: 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
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz,
1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz,
800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave,
performance
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.
  cpufreq stats: 2.00 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.80
GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.40 GHz:-nan%, 1.30
GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 900 MHz:-nan%, 800
MHz:-nan%  (403)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz,
1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz,
800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave,
performance
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.
  cpufreq stats: 2.00 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.80
GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.40 GHz:-nan%, 1.30
GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 900 MHz:-nan%, 800
MHz:-nan%  (382)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz,
1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz,
800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave,
performance
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.
  cpufreq stats: 2.00 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.80
GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.40 GHz:-nan%, 1.30
GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 900 MHz:-nan%, 800
MHz:-nan%  (445)
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 2.00 GHz
  available frequency steps: 2.00 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz,
1.60 GHz, 1.50 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 900 MHz,
800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave,
performance
  current policy: frequency should be within 800 MHz and 2.00 GHz.
                  The governor "conservative" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz.
  cpufreq stats: 2.00 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.80
GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.40 GHz:-nan%, 1.30
GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 900 MHz:-nan%, 800
MHz:-nan%  (354)

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2014-03-11  3:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11  9:32 [Bug 58001] New: "ondemand" CPU governor never raises frequency (Dell XPS 12) bugzilla-daemon
2013-05-12 15:32 ` Viresh Kumar
2013-05-12 15:32 ` [Bug 58001] " bugzilla-daemon
2013-05-12 16:55 ` bugzilla-daemon
2013-05-13  3:48   ` Viresh Kumar
2013-05-13  3:48 ` bugzilla-daemon
2013-05-29  1:04 ` bugzilla-daemon
2013-06-07 14:49 ` bugzilla-daemon
2013-07-08 14:57 ` bugzilla-daemon
2013-07-08 15:01 ` bugzilla-daemon
2013-07-08 15:02 ` bugzilla-daemon
2013-07-09  1:28 ` bugzilla-daemon
2013-09-23  1:58   ` [Bug 58001] Raymond Auge
2013-09-23  8:30 ` [Bug 58001] "ondemand" CPU governor never raises frequency (Dell XPS 12) bugzilla-daemon
2013-10-14 11:08 ` bugzilla-daemon
2013-10-14 11:34 ` bugzilla-daemon
2013-10-14 12:23 ` bugzilla-daemon
2014-03-11  3:22 ` bugzilla-daemon
2014-03-11  3:26 ` bugzilla-daemon [this message]
2014-03-23 22:39 ` bugzilla-daemon
2014-03-23 22:45 ` bugzilla-daemon
2014-09-22 13:54 ` bugzilla-daemon
2014-09-24 22:18 ` bugzilla-daemon
2014-09-24 22:55 ` bugzilla-daemon
2014-09-24 22:56 ` bugzilla-daemon
2014-09-25  0:16 ` bugzilla-daemon
2014-09-25  0:59 ` bugzilla-daemon
2014-09-25 14:31 ` bugzilla-daemon
2014-10-23  8:03 ` bugzilla-daemon

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=bug-58001-12968-dclWEokGkp@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@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;
as well as URLs for NNTP newsgroup(s).