All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 24 Nov 2012 01:11:17 +0000 (UTC)	[thread overview]
Message-ID: <20121124011117.364E311FB5A@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-50721-12968@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=50721





--- Comment #4 from rocko <rockorequin@hotmail.com>  2012-11-24 01:11:16 ---
Created an attachment (id=87151)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=87151)
Log output from turbostat and other commands

Here's the output from turbostat, top, and cpuinfo after I booted the system
and the cores stayed stuck in max frequency. I also included the output from
turbostat after a suspend/resume cycle, when the cores had successfully clocked
down to their min frequencies.

One point of strangeness is that first turbostat indicates frequencies up to
2.45GHz, which I thought is higher than my system allows. The subsequent
turbostat shows the cores running at around 2GHz. I suppose it is possible that
I ran the first command while the system was still using the performance
governor - could this be why the cores report 2.45GHz? The second turbostat
definitely was running when the ondemand governor was running, as you can see
from the 800Mhz reported in cpuinfo, and my frequency applet also was reporting
that the system was running in low performance mode.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-11-24  1:11 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 [this message]
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
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=20121124011117.364E311FB5A@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.