From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Frans Pop <elendil@planet.nl>
Cc: trenn@suse.de, linux-kernel@vger.kernel.org
Subject: Re: cpuinfo shows wrong MHz value
Date: Mon, 16 Feb 2009 19:01:00 +0000 [thread overview]
Message-ID: <20090216190100.GA10627@srcf.ucam.org> (raw)
In-Reply-To: <200902161952.38122.elendil@planet.nl>
On Mon, Feb 16, 2009 at 07:52:37PM +0100, Frans Pop wrote:
> Matthew Garrett wrote:
> > On Mon, Feb 16, 2009 at 07:13:15PM +0100, Thomas Renninger wrote:
> >> AFAIK p4-clockmode is still not synchronized with ACPI throttling?
> >
> > It ought to work fine with any systems using MSR-based throttling.
>
> So what's your take on this particular bug report then Matthew? Is this a
> regression that should be tracked down and fixed, or is this a case where
> the user should just not be using the module?
It's a bug and it should be fixed. My recollection is that we've hit
this kind of thing before - the frequency calculation code is awkward to
get right on this hardware.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-02-16 19:01 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
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 [this message]
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=20090216190100.GA10627@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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