From: Dave Jones <davej@codemonkey.org.uk>
To: "Hassard, Stephen" <SHassard@angio.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Enabling CPU freq scaling on VIA Cyrix 3 causes kernel l ockup / divide error
Date: Mon, 14 Jul 2003 18:26:18 +0100 [thread overview]
Message-ID: <20030714172618.GA7117@suse.de> (raw)
In-Reply-To: <E2B3FD6B3FF2804CB276D9ED037268354FF620@mail4.angio.com>
On Mon, Jul 14, 2003 at 08:46:19AM -0700, Hassard, Stephen wrote:
> longhaul: VIA CPU detected. Longhaul version 2 supportred
> longhaul: VRM 8.5 : Min VID=1.250 Max VID=1.250, 0 possible voltage scales
^^^^^^^^^^^^^^^^^^^^^^^
Erk, it should default into the 'voltage scaling unavailable' mode when
this happens, but the code is missing. I'll push that out to Linus
along with a large bunch of other cpufreq changes tonight/tomorrow.
Strange how your CPU seems to claim to support voltage scaling, but
erm.. doesn't. Can you also mail me the output of x86info -a -v
(Get the snapshot from http://www.codemonkey.org.uk/cvs/ )
> longhaul: MinMult(x10)=30 MaxMult(x10)=60
> longhaul: Lowestspeed=0 Highestspeed=0
> longhaul: FSB:0 Mult(x10):100
Something also went horribly wrong when trying to determine your FSB.
> divide error: 0000 [#1]
Leading to this tradegy. I'll take a look over the longhaul code later
too, as it could use some cleanups in more than a few areas.
I've also fallen behind in adding support for the newer C3s to it.
Dave
prev parent reply other threads:[~2003-07-14 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 15:46 PROBLEM: Enabling CPU freq scaling on VIA Cyrix 3 causes kernel l ockup / divide error Hassard, Stephen
2003-07-14 17:26 ` 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=20030714172618.GA7117@suse.de \
--to=davej@codemonkey.org.uk \
--cc=SHassard@angio.com \
--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).