cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 59781] New: intel_pstate synchronizes frequencies on wake from suspend
Date: Sun, 16 Jun 2013 16:12:15 +0000 (UTC)	[thread overview]
Message-ID: <bug-59781-12968@https.bugzilla.kernel.org/> (raw)

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

           Summary: intel_pstate synchronizes frequencies on wake from
                    suspend
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.10.0rc5, 3.10.0rc6
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
        AssignedTo: cpufreq@vger.kernel.org
        ReportedBy: pqwoerituytrueiwoq@gmail.com
        Regression: No


Created an attachment (id=104841)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=104841)
Behavior before suspend

When 1st boot both my core's frequencies change independently, but once i wake
from suspend they are synchronized
~$ uname -r # http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc6-saucy/
3.10.0-031000rc6-generic
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_driver 
intel_pstate
intel_pstate
$ cat /sys/devices/system/cpu/cpu*/cpuidle/driver/name 
intel_idle
intel_idle
$ cat /proc/cpuinfo # Only showing one core
processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 42
model name    : Intel(R) Pentium(R) CPU B970 @ 2.30GHz
stepping    : 7
microcode    : 0x23
cpu MHz        : 1242.000
cache size    : 2048 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 2
initial apicid    : 2
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm
constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr
pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave lahf_lm arat epb
xsaveopt pln pts dtherm
bogomips    : 4589.55
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

-- 
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-06-16 16:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 16:12 bugzilla-daemon [this message]
2013-06-16 16:12 ` [Bug 59781] intel_pstate synchronizes frequencies on wake from suspend bugzilla-daemon
2013-06-17  6:59 ` bugzilla-daemon
2013-06-17 11:37 ` bugzilla-daemon
2013-06-17 11:42 ` bugzilla-daemon
2013-06-17 17:15 ` bugzilla-daemon
2013-06-18  1:19 ` bugzilla-daemon
2013-06-18  2:42 ` bugzilla-daemon
2013-06-18 12:10 ` bugzilla-daemon
2013-06-18 16:23 ` bugzilla-daemon
2013-06-18 16:29 ` bugzilla-daemon
2013-07-08  2: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-59781-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 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).