From: Dominik Brodowski <linux@brodo.de>
To: Michael Vallaly <vaio@nolatency.com>
Cc: cpufreq@www.linux.org.uk
Subject: Re: 2.6.0-test1 CpuFreq Speedstep Quirks
Date: Fri, 18 Jul 2003 08:16:41 +0200 [thread overview]
Message-ID: <20030718061641.GA1882@brodo.de> (raw)
In-Reply-To: <20030717144842.70a5d7b3.vaio@nolatency.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
Hi Mike,
Many thanks for your extensive bug report. Could you please try out the
following:
a) test the attached patch
b) if this didn't help, boot with "clock=pit"
Dominik
On Thu, Jul 17, 2003 at 02:48:42PM +0000, Michael Vallaly wrote:
>
>
> Hello,
>
> After testing the 2.6.0-test1 kernel with CPUfreq scaling compiled in (+userspace govenor) I have noticed some changes in the way the kernel detects and prints my CPU information. Along these lines some programs (in peticular, mplayer and xmms) have some issues syncing (apparently time critical / cpu speed critical code.) As of right now these issues only seem to disappear if I run in powersave mode. Im not quite sure if this is a bug or not as I am quite new to cpu frequency scaling issues. If this is no
> t a bug / problem maybe someone can help enlighten me as to what is actually occuring. I would be willing to test anything speedstep / cpufreq related as I have quite a bit of freetime until August 25th. Attached are few screenshots of the interesting quirks with Cpufreq installed. Thanks for you time..
>
> - Mike
>
>
> Michael Vallaly
> vaio@nolatency.com
>
>
>
[-- Attachment #2: cpufreq-2.6.0-test1-speedstep-fix_setspeed --]
[-- Type: text/plain, Size: 1207 bytes --]
Correct the notification of the cpufreq core of the new frequency being
set in ich's speedstep_set, and print accurate debug info in this function.
(both bugs noted by Valdis Kletnieks, thanks!)
arch/i386/kernel/cpu/cpufreq/speedstep-ich.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--- linux/arch/i386/kernel/cpu/cpufreq/speedstep-ich.c.original 2003-07-14 23:26:42.415960752 +0200
+++ linux/arch/i386/kernel/cpu/cpufreq/speedstep-ich.c 2003-07-14 23:29:42.624564880 +0200
@@ -82,7 +82,7 @@
return;
freqs.old = speedstep_get_processor_frequency(speedstep_processor);
- freqs.new = speedstep_freqs[SPEEDSTEP_LOW].frequency;
+ freqs.new = speedstep_freqs[state].frequency;
freqs.cpu = 0; /* speedstep.c is UP only driver */
if (notify)
@@ -137,7 +137,7 @@
dprintk(KERN_DEBUG "cpufreq: read at pmbase 0x%x + 0x50 returned 0x%x\n", pmbase, value);
if (state == (value & 0x1)) {
- dprintk (KERN_INFO "cpufreq: change to %u MHz succeeded\n", (freqs.new / 1000));
+ dprintk (KERN_INFO "cpufreq: change to %u MHz succeeded\n", (speedstep_get_processor_frequency(speedstep_processor) / 1000));
} else {
printk (KERN_ERR "cpufreq: change failed - I/O error\n");
}
prev parent reply other threads:[~2003-07-18 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 14:48 2.6.0-test1 CpuFreq Speedstep Quirks Michael Vallaly
2003-07-18 6:16 ` Dominik Brodowski [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=20030718061641.GA1882@brodo.de \
--to=linux@brodo.de \
--cc=cpufreq@www.linux.org.uk \
--cc=vaio@nolatency.com \
/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