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: Tue, 17 Jun 2014 01:46:02 +0000 [thread overview]
Message-ID: <bug-77771-12968-wjtOYC7W6I@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 #7 from Yuyang Du <yuyang.du@intel.com> ---
(In reply to Michael Long from comment #5)
> Thanks for the hint about the turbostat utility. Without starting a desktop
> environment I got similar stats, all frequencies are very close around the
> lowest state. Logged into KDE showed different results. Eventually I found
> the cause of those high clocks:
>
> A superkaramba desktop-widget. This widget basically does a grep on
> /proc/cpuinfo and checks the load internally each second. Disabling this
> widget gets the clock down. The same behavior can be reproduced just by
> running "for i in {1..99}; do grep MHz /proc/cpuinfo; sleep 1; done".
>
> Admittedley this might be a typical layer8-problem, however why is a simple
> grep every second pounding the CPU so hard that it remains in higher clocks,
> even in turbo mode? Especially when it didn't before the patch or just using
> plain old acpi-cpufreq. If this is still just expected behavior sorry for
> the unnecessary noise.
Expected, but should not happen. So clearly something is wrong...
Yuyang
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-06-17 1:46 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 [this message]
2014-06-17 3:34 ` bugzilla-daemon
2014-06-19 16:25 ` bugzilla-daemon
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-wjtOYC7W6I@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