All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan D. Stine" <admin@kentonet.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test1] ACPI slowdown
Date: 23 Jul 2003 19:16:23 -0400	[thread overview]
Message-ID: <1059002183.1484.18.camel@gaia> (raw)
In-Reply-To: <bfn3rj$lql$1@gatekeeper.tmr.com>

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

I had that problem with my old Athlon TBird. Changing config to make
thermal a module and not loading it solved my problem. I don't know how
to change the thermal limits from within the system using ACPI.


On Wed, 2003-07-23 at 18:56, bill davidsen wrote:
> In article <878yqpptez.fsf@deneb.enyo.de>,
> Florian Weimer  <fw@deneb.enyo.de> wrote:
> | If I enable ACPI on my box (Athlon XP at 1.6 GHz, Epox EP-8KHa+
> | mainboard), it becomes very slow (so slow that it's unusable).
> | 
> | Is this a known issue?  Maybe the thermal limits are misconfigured,
> | and the CPU clock is throttled unnecessarily (if something like this
> | is supported at all).
> 
> There have been reports before, check the archives. I seem to remember
> that the solution involved changing some unobvious kernel feature, but
> others have had similar problems.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-23 23:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23  7:57 [2.6.0-test1] ACPI slowdown Florian Weimer
2003-07-23  9:44 ` Dominik Brugger
2003-07-24  6:33   ` Florian Weimer
2003-07-24  9:28     ` Dominik Brugger
2003-07-24  9:35       ` Florian Weimer
2003-07-24  9:45         ` Dominik Brugger
2003-07-24 23:42       ` Pavel Machek
2003-07-23 22:56 ` bill davidsen
2003-07-23 23:16   ` Bryan D. Stine [this message]
2003-07-24 10:03     ` Florian Weimer
2003-07-24 23:41     ` Pavel Machek
2003-07-24 23:54       ` Bryan D. Stine

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=1059002183.1484.18.camel@gaia \
    --to=admin@kentonet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.