From: Len Brown <len.brown@intel.com>
To: Bob Dobbs <bob_dobbs@linuxmail.org>
Cc: linux-kernel@vger.kernel.org,
"cpufreq@www.linux.org.uk" <cpufreq@www.linux.org.uk>
Subject: Re: Mobile Intel Pentium(R) 4 - M CPU 2.60GHz - kernel 2.6.3
Date: 27 Feb 2004 09:51:54 -0500 [thread overview]
Message-ID: <1077893513.22392.188.camel@dhcppc4> (raw)
In-Reply-To: <1077893211.22404.184.camel@dhcppc4>
caffine needed...
the fact that MHz goes down under heavy load means the BIOS must be
throttling your CPU to keep it cool. If you can't disable this BIOS
policy in SETUP, then running Linux with ACPI enabled and the processor
driver loaded should do it.
cheers,
-Len
On Fri, 2004-02-27 at 09:46, Len Brown wrote:
> Perhaps with ACPI disabled you've left CPU frequency control in the
> hands of SMM (the BIOS)? That would be consistent with Linux having no
> visibility or conrol over what is going on. There may be some BIOS
> SETUP options to turn it off.
>
> cheers,
> -Len
>
> Thu, 2004-02-26 at 19:46, Bob Dobbs wrote:
> > Hello,
> >
> > I am currently running kernel 2.6.3 on my Dell Inspiron 8500 laptop.
> > I disabled all the ACPI and APM options in the kernel.
> >
> > I have upgraded my bios
> > I have tried from kernel 2.4.23 up to mm and love-sources and my
> > current kernel 2.6.3.
> >
> > What happens is during heavy loads my cpu drops from 2.60GHz down to
> > 1.20GHz, this happens for a few minutes, say 5 - 10 at the most. But
> > performance while running a game, puts the game into slow motion.
> > (Which is weird because 1.20GHz should be more than enough to run all
> > of the games I currently have). I have read up on the documentation
> > in /usr/src/linux/Documentation, under the "power" and "cpu-freq" but
> > after disabling ACPI and such, those options do not seem to work
> > anymore.
> >
> > I have also tried running a program called "cpufreqd" which launches
> > at boot time, but once again without ACPI enabled in the kernel this
> > seems not to work either. Also /sys/devices/system/cpu/cpu0/cpufreq/
> > has the following files.
> >
> > cpuinfo_min_freq
> > cpuinfo_max_freq
> > scaling_min_freq
> > scaling_max_freq
> >
> > I even tried to echo the options at bootup:
> >
> > echo 2600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq &
> > echo 2000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq &
> >
> > I tried to make those files set at: 2.00GHz min and 2.60GHz max, but
> > something changes them right back to 1.20GHZ no matter what I do.
> >
> > I am sure I am missing something, but atm I am totally lost.. and I
> > could surely be doing everything wrong to begin with... that is why I
> > am asking for help.
> >
> > Is there a patch or anything to force the cpu to run at 2.60GHz all
> > the time?
> >
> > Thank you
>
next prev parent reply other threads:[~2004-02-27 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F3C81@hdsmsx402.hd.intel.com>
2004-02-27 14:46 ` Mobile Intel Pentium(R) 4 - M CPU 2.60GHz - kernel 2.6.3 Len Brown
2004-02-27 14:51 ` Len Brown [this message]
2004-02-27 0:46 Bob Dobbs
2004-02-27 13:14 ` Zwane Mwaikambo
2004-02-27 23:51 ` Robin Rosenberg
2004-02-27 18:25 ` Disconnect
2004-03-04 14:38 ` Pavel Machek
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=1077893513.22392.188.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=bob_dobbs@linuxmail.org \
--cc=cpufreq@www.linux.org.uk \
--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