From: Jay Goodman Tamboli <jay@tamboli.cx>
To: cpufreq@www.linux.org.uk
Subject: Re: Cpufreq: powernow-k7 weirdness
Date: Sun, 6 Jul 2003 13:28:09 -0400 [thread overview]
Message-ID: <20030706172809.GA10482@localhost.localdomain> (raw)
In-Reply-To: <1057511460.d2cf9bc12efe7@carlthompson.net>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Sun, Jul 06, 2003 at 10:11:00AM -0700, Carl Thompson wrote:
> Quoting Ducrot Bruno <ducrot@poupinou.org>:
>
> > ...
>
> > There is a little bug in powernow-k7.c
>
> > ...
>
> > - change_VID(fid);
> > - change_FID(vid);
> > + change_VID(vid);
> > + change_FID(fid);
>
> > ...
>
> > It is not in mainline AFAIK.
>
> This "little bug" caused my computer to repeatedly crash with 2.4.21-ac4 and
> 2.5.72! Not sure if it's in more recent kernels, but it was definitely in
> the mainline at that point.
(new to the list, so hopefully not beating dead horse here)
Yeah, I found this in 2.4.21-ac4, too, and was having
crashes. Fixing this bug still causes lockups if I change
the cpufreq too drastically. Going from one setting to the
next (i.e. not skipping any available speeds) seems to work
ok, though. This is a Sony FR130, so is this the effect of
the PST problems discussed earlier?
/jgt
--
You can't spell "deadly heart palpitations" without "h-a-p-p-y".
-- Jason Zych, on uiuc.general
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-06 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 1:00 Cpufreq: powernow-k7 weirdness Juliusz Chroboczek
2003-07-06 1:21 ` Ducrot Bruno
2003-07-06 17:11 ` Carl Thompson
2003-07-06 17:28 ` Jay Goodman Tamboli [this message]
2003-07-06 17:43 ` Carl Thompson
2003-07-06 18:48 ` Ducrot Bruno
2003-07-06 21:56 ` Luigi Belli
2003-07-07 4:16 ` Michael Frank
2003-07-07 13:12 ` Ducrot Bruno
2003-07-07 15:06 ` Michael Frank
2003-07-07 16:32 ` Daniel Thor Kristjansson
2003-07-07 12:58 ` Juliusz Chroboczek
2003-07-07 13:32 ` Ducrot Bruno
2003-07-07 17:32 ` Dave Jones
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=20030706172809.GA10482@localhost.localdomain \
--to=jay@tamboli.cx \
--cc=cpufreq@www.linux.org.uk \
/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