From: Thomas Renninger <trenn@suse.de>
To: Patrick McLean <patrick@cim.mcgill.ca>
Cc: cpufreq@vger.kernel.org
Subject: Re: Core 2 Duo E6600 (2.4GHz) reporting max frequency of 900MHz
Date: Wed, 30 Mar 2011 12:48:23 +0200 [thread overview]
Message-ID: <201103301248.23763.trenn@suse.de> (raw)
In-Reply-To: <4D91F866.20503@cim.mcgill.ca>
On Tuesday, March 29, 2011 05:19:02 PM Patrick McLean wrote:
...
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
> > nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni
> > dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm
> > tpr_shadow
This cpu already supports aperfmperf registers.
You could try cpufreq-aperf with a recent cpufrequtils package
to double check. Oh no, this is also based on maxfreq exported by cpufreq
subsystem... Hm, I'd still be interested about the outcome.
Best try with idle cores and one core utilized:
cpufreq-aperf
-> send output
cat /dev/zero >/dev/null &
cpufreq-aperf
-> send output
> > hardware limits: 600 MHz - 900 MHz
Even HW (MSRs) report wrong frequencies?!?
(if CPU is using MSR based switching, what I expect).
Looks like the HW/firmware is broken.
Best is you try with latest BIOS (also search for some related BIOS
settings and fiddle with them), maybe also make sure that Intel's latest
CPU microcode patch is loaded if BIOS observations do not help...
Thomas
prev parent reply other threads:[~2011-03-30 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 15:19 Core 2 Duo E6600 (2.4GHz) reporting max frequency of 900MHz Patrick McLean
2011-03-30 10:48 ` Thomas Renninger [this message]
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=201103301248.23763.trenn@suse.de \
--to=trenn@suse.de \
--cc=cpufreq@vger.kernel.org \
--cc=patrick@cim.mcgill.ca \
/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.