From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 59781] intel_pstate synchronizes frequencies on wake from suspend
Date: Mon, 17 Jun 2013 17:15:25 +0000 (UTC) [thread overview]
Message-ID: <20130617171525.6248211FB35@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-59781-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=59781
Dirk Brandewie <dirk.brandewie@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dirk.brandewie@gmail.com
--- Comment #5 from Dirk Brandewie <dirk.brandewie@gmail.com> 2013-06-17 17:15:25 ---
Could you use turbostat to collect data on the good and bad state please.
Does this happen all the time? There are a number of bugs open where both
intel_pstate and ondemand are doing weird things after coming out of
suspend. I the other bugs the situation would clear sometimes after a number
of suspend/resume cycles.
If you could see if this happens without intel_pstate it would be helpful
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2013-06-17 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 16:12 [Bug 59781] New: intel_pstate synchronizes frequencies on wake from suspend bugzilla-daemon
2013-06-16 16:12 ` [Bug 59781] " 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 [this message]
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=20130617171525.6248211FB35@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.