From: Dave Jones <davej@redhat.com>
To: Jurgen Kramer <gtm.kramer@inter.nl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8: cpufreq longhaul probs..still :-(
Date: Sun, 19 Oct 2003 14:54:29 +0100 [thread overview]
Message-ID: <20031019135429.GA8924@redhat.com> (raw)
In-Reply-To: <1066475780.2607.6.camel@paragon.slim>
On Sat, Oct 18, 2003 at 01:16:21PM +0200, Jurgen Kramer wrote:
> With test8 there are still problems with the longhaul cpufreq stuff:
>
> longhaul: VIA C3 'Ezra' [C5C] CPU detected. Longhaul v1 supported.
> longhaul: MinMult=3.0x MaxMult=6.0x
> longhaul: FSB: 0MHz Lowestspeed=0MHz Highestspeed=0MHz
*boggle*, we had these fixed I thought..
I'm going to need you to litter the code with printk's to find out
why your MSRs are returning zeros. Contact me off list if you want
a patch to do this, otherwise.. don't be afraid to go overboard,
the more debug info the better.
> I'll check if I can fix the min/max freq. Is Longhaul v1 correct for
> this CPU? With cpufreq from 2.4 it always displays v2.
According to the documentation, yes.
Dave
--
Dave Jones http://www.codemonkey.org.uk
prev parent reply other threads:[~2003-10-19 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-18 11:16 2.6.0-test8: cpufreq longhaul probs..still :-( Jurgen Kramer
2003-10-19 13:54 ` Dave Jones [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=20031019135429.GA8924@redhat.com \
--to=davej@redhat.com \
--cc=gtm.kramer@inter.nl.net \
--cc=linux-kernel@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).