From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 50721] CPU freqs stay stuck at max after reboot with on-demand governor set - i7-2630QM
Date: Tue, 27 Nov 2012 02:52:31 +0000 (UTC) [thread overview]
Message-ID: <20121127025231.D752111F883@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-50721-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=50721
--- Comment #5 from Len Brown <lenb@kernel.org> 2012-11-27 02:52:31 ---
re: /proc/cpuinfo MHz value
I don't think that is used for anything, or means anything.
We really should delete that, as all it does is confuse people.
re: turbostat output
yes, it looks like you are stuck at high frequency
even when mostly idle, but this condition goes away after
suspend/resume. Does the system behave normally after
it breaks out of the initial problem?
--
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:[~2012-11-27 2:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 5:45 [Bug 50721] New: CPU freqs stay stuck at max after reboot with on-demand governor set bugzilla-daemon
2012-11-19 5:45 ` [Bug 50721] " bugzilla-daemon
2012-11-20 2:56 ` [Bug 50721] CPU freqs stay stuck at max after reboot with on-demand governor set - i7-2630QM bugzilla-daemon
2012-11-20 23:30 ` bugzilla-daemon
2012-11-24 1:11 ` bugzilla-daemon
2012-11-27 2:52 ` bugzilla-daemon [this message]
2012-11-27 3:43 ` bugzilla-daemon
2012-12-03 3:14 ` bugzilla-daemon
2012-12-04 1:01 ` bugzilla-daemon
2012-12-23 14:47 ` bugzilla-daemon
2013-01-08 3:01 ` bugzilla-daemon
2013-01-14 1:26 ` bugzilla-daemon
2013-01-14 1:30 ` bugzilla-daemon
2013-01-17 21:24 ` Elliot Wolk
2013-01-22 10:53 ` bugzilla-daemon
2013-03-14 16:07 ` bugzilla-daemon
2013-03-18 17:18 ` bugzilla-daemon
2013-03-24 22:09 ` bugzilla-daemon
2013-03-25 2:56 ` bugzilla-daemon
2013-04-13 17:43 ` 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=20121127025231.D752111F883@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.