All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 55091] New: cpufreq governors woks crazy
Date: Mon, 11 Mar 2013 21:58:46 +0000 (UTC)	[thread overview]
Message-ID: <bug-55091-12968@https.bugzilla.kernel.org/> (raw)

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

           Summary: cpufreq governors woks crazy
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.9-rc2
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: towo@siduction.org
        Regression: No


Since i test kernel 3.9-rc2, cpufreq is crazy with governors ondemand and
conservative.
Even if the system is idling, cpufreq is on the highest or medium frequency.
Only with powersafe i can get the cpu to the lowest frequency.

This behavior i cant see in 3.8 or below.

Here the output from cpufreq-info:

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 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 2.66 GHz
  available frequency steps: 2.66 GHz, 2.13 GHz, 1.60 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand,
performance
  current policy: frequency should be within 1.60 GHz and 2.66 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
  cpufreq stats: 2.66 GHz:3.10%, 2.13 GHz:3.09%, 1.60 GHz:93.81%  (8123)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 2.66 GHz
  available frequency steps: 2.66 GHz, 2.13 GHz, 1.60 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand,
performance
  current policy: frequency should be within 1.60 GHz and 2.66 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
  cpufreq stats: 2.66 GHz:3.10%, 2.13 GHz:3.09%, 1.60 GHz:93.81%  (8123)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 2.66 GHz
  available frequency steps: 2.66 GHz, 2.13 GHz, 1.60 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand,
performance
  current policy: frequency should be within 1.60 GHz and 2.66 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
  cpufreq stats: 2.66 GHz:3.10%, 2.13 GHz:3.09%, 1.60 GHz:93.81%  (8123)
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 10.0 us.
  hardware limits: 1.60 GHz - 2.66 GHz
  available frequency steps: 2.66 GHz, 2.13 GHz, 1.60 GHz
  available cpufreq governors: powersave, conservative, userspace, ondemand,
performance
  current policy: frequency should be within 1.60 GHz and 2.66 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
  cpufreq stats: 2.66 GHz:3.10%, 2.13 GHz:3.09%, 1.60 GHz:93.81%  (8123)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2013-03-11 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 21:58 bugzilla-daemon [this message]
2013-03-12 11:15 ` [Bug 55091] cpufreq governors woks crazy bugzilla-daemon
2013-03-26  7:44 ` bugzilla-daemon
2013-03-26  7:45 ` bugzilla-daemon
2013-03-26 16:39 ` bugzilla-daemon
2013-04-01  5:50 ` 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-55091-12968@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 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.