cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 19702] i5-450M CPU gets stuck in low/lowest state
Date: Mon, 15 Aug 2011 15:08:34 GMT	[thread overview]
Message-ID: <201108151508.p7FF8YLk025977@demeter2.kernel.org> (raw)
In-Reply-To: <bug-19702-12968@https.bugzilla.kernel.org/>

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





--- Comment #56 from Thomas Renninger <trenn@suse.de>  2011-08-15 15:08:25 ---
You can verify whether turboboost is enabled/disabled by:
- utilizing one core:
  cat /dev/zero >/dev/null &
- run turbostat or "cpupower monitor -m Mperf"
  and double check average frequency of the utilized core whether it got
boosted

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

  parent reply	other threads:[~2011-08-15 15:08 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-19702-12968@https.bugzilla.kernel.org/>
2010-10-04  6:42 ` [Bug 19702] i5-450M CPU gets stuck in low/lowest state bugzilla-daemon
2010-10-04  6:43 ` bugzilla-daemon
2010-10-04  6:44 ` bugzilla-daemon
2010-10-08  5:26 ` bugzilla-daemon
2010-10-08 12:59 ` bugzilla-daemon
2010-10-08 19:04 ` bugzilla-daemon
2010-10-08 19:06 ` bugzilla-daemon
2010-10-12 11:19 ` bugzilla-daemon
2010-10-14  5:56 ` bugzilla-daemon
2010-10-14  5:58 ` bugzilla-daemon
2010-10-14  9:11 ` bugzilla-daemon
2010-10-14  9:22 ` bugzilla-daemon
2010-10-14 15:20 ` bugzilla-daemon
2010-10-15 10:07 ` bugzilla-daemon
2010-10-15 10:12 ` bugzilla-daemon
2010-10-15 10:15 ` bugzilla-daemon
2010-10-15 17:52 ` bugzilla-daemon
2010-10-15 19:25 ` bugzilla-daemon
2010-10-15 19:37 ` bugzilla-daemon
2010-10-16  8:56 ` bugzilla-daemon
2010-10-16  9:19 ` bugzilla-daemon
2010-10-19  2:50 ` bugzilla-daemon
2010-10-19  3:12 ` bugzilla-daemon
2010-10-19  3:51 ` bugzilla-daemon
2010-10-19  3:52 ` bugzilla-daemon
2010-10-19  7:34 ` bugzilla-daemon
2010-10-19  9:40 ` bugzilla-daemon
2010-10-19 14:13 ` bugzilla-daemon
2010-10-19 22:47 ` bugzilla-daemon
2010-10-28 15:12 ` bugzilla-daemon
2010-10-28 15:13 ` bugzilla-daemon
2010-10-29 11:06 ` bugzilla-daemon
2010-10-29 12:14 ` bugzilla-daemon
2010-10-29 13:00 ` bugzilla-daemon
2010-10-29 15:49 ` bugzilla-daemon
2010-10-29 20:15 ` bugzilla-daemon
2010-10-29 20:19 ` bugzilla-daemon
2010-11-01 10:49 ` bugzilla-daemon
2010-11-01 13:42 ` bugzilla-daemon
2010-11-01 17:43 ` bugzilla-daemon
2010-11-01 18:03 ` bugzilla-daemon
2010-11-01 18:16 ` bugzilla-daemon
2010-11-02  7:09 ` bugzilla-daemon
2010-11-02  8:59 ` bugzilla-daemon
2010-11-02  9:03 ` bugzilla-daemon
2010-11-03 20:42 ` bugzilla-daemon
2010-11-04  8:15 ` bugzilla-daemon
2010-11-04  8:41 ` bugzilla-daemon
2010-11-08 12:32 ` bugzilla-daemon
2010-11-08 12:49 ` bugzilla-daemon
2010-11-09 17:38 ` bugzilla-daemon
2010-11-10 11:18 ` bugzilla-daemon
2010-11-10 12:51 ` bugzilla-daemon
2011-07-31 17:58 ` bugzilla-daemon
2011-08-01  7:35 ` bugzilla-daemon
2011-08-11 13:00 ` bugzilla-daemon
2011-08-12 13:20 ` bugzilla-daemon
2011-08-15 15:04 ` bugzilla-daemon
2011-08-15 15:08 ` bugzilla-daemon [this message]
2012-06-18 19:11 ` 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=201108151508.p7FF8YLk025977@demeter2.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