cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 56101] Intel Core2 Duo E6600 reports max-frequency of just 900 MHz instead of 2.4 GHz
Date: Fri,  5 Apr 2013 14:14:25 +0000 (UTC)	[thread overview]
Message-ID: <20130405141425.558B711FB79@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-56101-12968@https.bugzilla.kernel.org/>

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





--- Comment #11 from S. Kalteis <spam@kernelspace.de>  2013-04-05 14:14:25 ---
(In reply to comment #8)
> You can use
> cpupower monitor
> tool (sources located in the kernel, depending on the distribution it might
> have another name, which should get addressed by distro maintainers, there
> should be a separate cpupower package on Linux distros).
> This will show you the exact frequency your cores run on over a certain amount
> of time (or workload if a command is appended) including boosting.

cpupower monitor (from kernel 3.8.5) exits after printing the following output:

     |Mperf               
CPU | C0   | Cx   | Freq 
   0|******|******|******
   1|******|******|******


instead of running continously, I guess.

cpupower monitor -l gives:

Monitor "Mperf" (3 states) - Might overflow after 922000000 s
C0      [T] -> Processor Core not idle
Cx      [T] -> Processor Core in an idle state
Freq    [T] -> Average Frequency (including boost) in MHz


For the acpi-tables, see attachments.

-- 
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:[~2013-04-05 14:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  9:41 [Bug 56101] New: Intel Core2 Duo E6600 reports max-frequency of just 900 MHz instead of 2.4 GHz bugzilla-daemon
2013-04-02  9:41 ` [Bug 56101] " bugzilla-daemon
2013-04-02  9:42 ` bugzilla-daemon
2013-04-02  9:42 ` bugzilla-daemon
2013-04-02 10:09 ` bugzilla-daemon
2013-04-02 10:18 ` bugzilla-daemon
2013-04-02 10:20 ` bugzilla-daemon
2013-04-05 12:54 ` bugzilla-daemon
2013-04-05 13:45 ` bugzilla-daemon
2013-04-05 14:09 ` bugzilla-daemon
2013-04-05 14:10 ` bugzilla-daemon
2013-04-05 14:14 ` bugzilla-daemon [this message]
2013-04-05 14:23 ` bugzilla-daemon
2013-04-05 14:48 ` bugzilla-daemon
2013-04-05 15:17 ` 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=20130405141425.558B711FB79@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).