From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 19702] i5-450M CPU gets stuck in low/lowest state
Date: Fri, 12 Aug 2011 13:20:55 GMT [thread overview]
Message-ID: <201108121320.p7CDKtmK030057@demeter2.kernel.org> (raw)
In-Reply-To: <bug-19702-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=19702
--- Comment #54 from David Tomaschik <david@systemoverlord.com> 2011-08-12 13:20:36 ---
An update on my post above. Disabling TurboBoost in the BIOS seems to have
resolved the issue. I wonder if TurboBoost somehow causes mis-reported aperf
statistics.
Interestingly enough, the ratios are the same as the turboboost ratio on this
CPU. That is, 3.2GHz (Turbo)/2.5 GHz (Stock) == 800 MHz (Real minimum)/625 MHz
(reported minimum via aperf). I don't know if it matters, just thought it was
notable.
--
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.
next prev parent reply other threads:[~2011-08-12 13:20 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 [this message]
2011-08-15 15:04 ` bugzilla-daemon
2011-08-15 15:08 ` bugzilla-daemon
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=201108121320.p7CDKtmK030057@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 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.