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: Thu, 14 Mar 2013 16:07:16 +0000 (UTC) [thread overview]
Message-ID: <20130314160717.0134811FA4C@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-50721-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=50721
Vadim Fint <mocksoul@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mocksoul@gmail.com
--- Comment #14 from Vadim Fint <mocksoul@gmail.com> 2013-03-14 16:07:16 ---
Got absolutely the same behaviour with 3.7.5 kernel on i7-2620M cpu.
As far as I can see -- it occurs after long sleeps > 5-10 mins. I occurs 100%
after long sleep (going to work -- it happens, going home at evening -- it
happens again).
cpufreq shows what it sets lowest freq possibly, but once I try "-w" switch it
shows 2.7GHz real hardware clock.
I tried plain vanilla 3.7.10 kernel with no luck.
Cant try 3.8.x yet, because there is no pf-patches for it (I *need* BFS ;)).
Will try to downgrade onto 3.6.x and post results here...
Cpufreq from unprivileged user shows 800MHz:
csl linux/tools/power/x86/turbostat # sudo -u mocksoul cpufreq-info| grep
'curre
nt CPU'
current CPU frequency is 800 MHz.
current CPU frequency is 800 MHz.
current CPU frequency is 800 MHz.
current CPU frequency is 800 MHz.
While root can read hw freq and it shows 2.7GHz :(
mcsl linux/tools/power/x86/turbostat # cpufreq-info| grep 'current CPU'
current CPU frequency is 2.70 GHz (asserted by call to hardware).
current CPU frequency is 2.70 GHz (asserted by call to hardware).
current CPU frequency is 2.70 GHz (asserted by call to hardware).
current CPU frequency is 2.70 GHz (asserted by call to hardware).
Turbostat (as well as powertop 1.x) shows that my cpu mostly in c7 state:
mcsl linux/tools/power/x86/turbostat # ./turbostat
cor CPU %c0 GHz TSC %c1 %c3 %c6 %c7 %pc2 %pc3 %pc6
%pc7
0.42 2.69 2.69 1.34 0.03 0.00 98.22 0.00 0.00 0.00
0.00
0 0 0.86 2.69 2.69 2.41 0.05 0.00 96.67 0.00 0.00 0.00
0.00
0 1 0.63 2.69 2.69 2.64
1 2 0.15 2.69 2.69 0.09 0.00 0.00 99.76
1 3 0.02 2.69 2.69 0.22
--
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-03-14 16:07 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
2013-01-22 10:53 ` bugzilla-daemon
2013-03-14 16:07 ` bugzilla-daemon [this message]
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=20130314160717.0134811FA4C@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;
as well as URLs for NNTP newsgroup(s).