From: Elliot Wolk <elliot.wolk@gmail.com>
To: cpufreq@vger.kernel.org
Subject: Re: [Bug 50721] CPU freqs stay stuck at max after reboot with on-demand governor set - i7-2630QM
Date: Thu, 17 Jan 2013 21:24:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20130117T221016-208@post.gmane.org> (raw)
In-Reply-To: 20130114013037.4480F11FB6C@bugzilla.kernel.org
i also experience this exactly, with i7-2720QM.
my cores get 'stuck' on 2.2ghz
sometimes, the max w/out turbo.
{kernel 3.7.0, lenovo w520}
cpu usage hovers around 6% and load is .62.
the cores spend nearly all their time in C7 state,
according to turbostat.
changing the governor does not fix this.
using userspace or ondemand and setting
the min/max can convince to use turbo {2201000, goes to 3.1ghz},
but not change the minimum.
performance makes it use turbo {goes to 3.1ghz},
and powersave does nothing {keeps it at 2.2ghz}.
note that suspending to ram and waking up,
occasionally shakes it loose, and freq drops to 0.8ghz.
so when it gets stuck, as a workaround, i just pm-suspend,
wait 20s, and repeat, until turbostat shows it has dropped.
next prev parent reply other threads:[~2013-01-17 21:24 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
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 [this message]
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=loom.20130117T221016-208@post.gmane.org \
--to=elliot.wolk@gmail.com \
--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.