All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 77771] Intel P-State: Constantly changing CPU frequencies on idle system.
Date: Thu, 19 Jun 2014 16:25:06 +0000	[thread overview]
Message-ID: <bug-77771-12968-tBa3pLQ039@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-77771-12968@https.bugzilla.kernel.org/>

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

--- Comment #9 from Michael Long <harn-solo@gmx.de> ---
Created attachment 140441
  --> https://bugzilla.kernel.org/attachment.cgi?id=140441&action=edit
Kernel config 3.15

Sorry for the delay, yes the turbostat results are all from the same Haswell
i5-4200U with 800-1600 MHz (turbo 2.9 GHz) [1].

I've no clue why this ultrabook is so sensitive. Hence I've attached my current
kernel-config maybe I've misconfigured something.

In the meantime I tried to find a better method to reproduce the effect but I
had no real luck when testing on my other quad-core systems. There, the effect
is very less severe.



[1]
http://ark.intel.com/products/75459/Intel-Core-i5-4200U-Processor-3M-Cache-up-to-2_60-GHz?q=i5-4200U

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

  parent reply	other threads:[~2014-06-19 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  5:49 [Bug 77771] New: Intel P-State: Constantly changing CPU frequencies on idle system bugzilla-daemon
2014-06-13  6:20 ` [Bug 77771] " bugzilla-daemon
2014-06-13  8:18 ` bugzilla-daemon
2014-06-13  9:09 ` bugzilla-daemon
2014-06-15  0:44 ` bugzilla-daemon
2014-06-16 19:15 ` bugzilla-daemon
2014-06-16 19:19 ` bugzilla-daemon
2014-06-17  1:46 ` bugzilla-daemon
2014-06-17  3:34 ` bugzilla-daemon
2014-06-19 16:25 ` bugzilla-daemon [this message]
2014-06-19 16:34 ` bugzilla-daemon
2014-06-20 16:10 ` bugzilla-daemon
2014-06-20 16:11 ` bugzilla-daemon
2014-06-23  8:08 ` 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-77771-12968-tBa3pLQ039@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.