All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 65591] New: Haswell CPU is not going to powersafe mode.
Date: Sun, 24 Nov 2013 08:25:31 +0000	[thread overview]
Message-ID: <bug-65591-12968@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 65591
           Summary: Haswell CPU is not going to powersafe mode.
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.12.0-031200-generic #201311031935 SMP Mon Nov 4
                    00:36:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: cpufreq@vger.kernel.org
          Reporter: tomas.ivanek@gmail.com
        Regression: No

CPU speed is not going to powersafe mode - to 800 Mhz. It' always >1.6 GHz
Minfreq is defined as 800000. 

Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz

root@dell-xps:/sys/devices/system/cpu/cpu0/cpufreq# grep "" *
affected_cpus:0
cpuinfo_cur_freq:1878812
cpuinfo_max_freq:2600000
cpuinfo_min_freq:800000
cpuinfo_transition_latency:4294967295
related_cpus:0
scaling_available_governors:performance powersave
scaling_driver:intel_pstate
scaling_governor:powersave
scaling_max_freq:2600000
scaling_min_freq:800000
scaling_setspeed:<unsupported>

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

             reply	other threads:[~2013-11-24  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24  8:25 bugzilla-daemon [this message]
2013-11-24 11:23 ` [Bug 65591] Haswell CPU is not going to powersafe mode bugzilla-daemon
2013-11-25  2:15 ` 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-65591-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.