From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
Date: Thu, 03 Apr 2014 01:33:42 +0000 [thread overview]
Message-ID: <bug-73421-12968-JlRlhF0bos@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73421-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=73421
--- Comment #2 from Álvaro Castillo <netsys@fedoraproject.org> ---
Yes I am getting 2.90 but does not set 3.1Ghz.
For example, In this bug https://bugzilla.kernel.org/show_bug.cgi?id=66581 got
problems that does not increases more of 2.8Ghz of kernel when max frecuencies
is 3.8Ghz.
I don't understand why is not increases into 3.1Ghz.If not Intel should be tell
the truth about Turbo boost and frequencies.
By other hand, I end compile a kernel over 30 minutes more less. However, my
friend does have an Intel Core 2 P8600 takes 10 minutes more less. How is a
CPU old with 2 cores can compile a kernel into 10 minutes more less than my new
CPU It's new model. I think is a bug.
Some users of Gentoo with i5 processors tells me that 5-6 minutes more less
should be end compiling a kernel process. :/
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-03 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 0:51 [Bug 73421] New: intel/p_state Does not increase into Turbo Boost states and does not display al governors. i5-3201M bugzilla-daemon
2014-04-03 0:53 ` [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all " bugzilla-daemon
2014-04-03 1:12 ` bugzilla-daemon
2014-04-03 1:33 ` bugzilla-daemon [this message]
2014-04-03 1:52 ` bugzilla-daemon
2014-04-03 15:14 ` bugzilla-daemon
2014-04-03 15:37 ` bugzilla-daemon
2014-04-15 6:10 ` bugzilla-daemon
2014-09-22 13:38 ` 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=bug-73421-12968-JlRlhF0bos@https.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.