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 00:22:14 +0100 [thread overview]
Message-ID: <200902150022.39271.jplatte@naasa.net> (raw)
In-Reply-To: <200902142346.30449.elendil@planet.nl>
Am Samstag, 14. Februar 2009 schrieb Frans Pop:
> On Saturday 14 February 2009, Kasper Sandberg wrote:
> > I dont think cpu frequency scaling can suddenly make a cpu go from
> > 1.6ghz to 13ghz, but if it can, i sure want one!
>
> Ah, sorry. I misread the message and thought the problem was it was
> showing 1.3 GHz, which would be a very normal scaling value.
>
> However, it would have helped if the problem had been stated explicitly in
> the original message instead of letting others interpret the raw data.
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 2.6.26) cpuinfo
showed the correct value.
regards,
Jörg
next prev parent reply other threads:[~2009-02-14 23:31 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 [this message]
2009-02-15 0:02 ` Frans Pop
2009-02-15 7:00 ` Joerg Platte
2009-02-15 7:11 ` Joerg Platte
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=200902150022.39271.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