From: Joerg Platte <jplatte@naasa.net>
To: Frans Pop <elendil@planet.nl>
Cc: Kasper Sandberg <lkml@metanurb.dk>, linux-kernel@vger.kernel.org
Subject: Re: cpuinfo shows wrong MHz value
Date: Sun, 15 Feb 2009 08:11:35 +0100 [thread overview]
Message-ID: <200902150811.36826.jplatte@naasa.net> (raw)
In-Reply-To: <200902150800.59694.jplatte@naasa.net>
Am Sonntag, 15. Februar 2009 schrieb Joerg Platte:
> Am Sonntag, 15. Februar 2009 schrieb Frans Pop:
> > On Sunday 15 February 2009, Joerg Platte wrote:
> > > Sorry, I should have made it clear that my computer is running with 13
> > > GHz (at leat according to the kernel). With previous kernels (IIRC
> /sys/devices/system/cpu/cpu0/cpufreq> grep . *
> affected_cpus:0
> cpuinfo_cur_freq:13000000
> cpuinfo_max_freq:13000000
> cpuinfo_min_freq:3250000
> related_cpus:0
> scaling_available_frequencies:3250000 4875000 6500000 8125000 9750000
> 11375000 13000000
> scaling_available_governors:conservative ondemand userspace powersave
> performance
> scaling_cur_freq:13000000
> scaling_driver:p4-clockmod
> scaling_governor:performance
> scaling_max_freq:13000000
> scaling_min_freq:3250000
> scaling_setspeed:<unsupported>
Looks like p4_clockmod is responsible for these high values. After removing
it /proc/cpuinfo shows the correct values:
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 1
model name : Intel(R) Pentium(R) 4 CPU 1.60GHz
stepping : 2
cpu MHz : 1598.609
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
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 pebs bts
bogomips : 3197.21
clflush size : 64
power management:
best regards,
Jörg
next prev parent reply other threads:[~2009-02-15 7:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 21:17 cpuinfo shows wrong MHz value Joerg Platte
2009-02-14 22:29 ` Frans Pop
2009-02-14 22:38 ` Kasper Sandberg
2009-02-14 22:46 ` Frans Pop
2009-02-14 23:22 ` Joerg Platte
2009-02-15 0:02 ` Frans Pop
2009-02-15 7:00 ` Joerg Platte
2009-02-15 7:11 ` Joerg Platte [this message]
2009-02-15 16:41 ` Frans Pop
2009-02-16 14:19 ` Thomas Renninger
2009-02-16 16:50 ` Matthew Garrett
2009-02-16 18:13 ` Thomas Renninger
2009-02-16 18:19 ` Matthew Garrett
2009-02-16 18:47 ` Thomas Renninger
2009-02-16 18:52 ` Frans Pop
2009-02-16 19:01 ` Matthew Garrett
2009-02-18 19:54 ` Joerg Platte
2009-02-18 21:05 ` Frans Pop
2009-02-19 17:03 ` Joerg Platte
2009-02-20 2:52 ` Frans Pop
2009-02-20 18:42 ` Joerg Platte
2009-02-15 17:43 ` Frans Pop
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=200902150811.36826.jplatte@naasa.net \
--to=jplatte@naasa.net \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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