From: Brad Laue <brad@brad-x.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ksoftirqd using mysteriously high amounts of CPU time
Date: Thu, 11 Mar 2004 12:22:15 -0500 [thread overview]
Message-ID: <4050A047.9030603@brad-x.com> (raw)
In-Reply-To: <1079013947.24999.17.camel@firefly>
Yury V. Umanets wrote:
> Hello,
>
> I have impression, that it is somehow related to ACPI and CPU
> temperature. When CPU gets more hot ksoftirqd starts to eat 99% of CPU.
>
> It may be checked by disabling ACPI (if enabled) and/or monitoring
> /proc/acpi/thermal_zone/THRM/temperature (if any).
Happens on a system without ACPI or Power Management of any kind enabled
though.
Brad
next prev parent reply other threads:[~2004-03-11 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 21:16 ksoftirqd using mysteriously high amounts of CPU time Brad Laue
2004-03-10 23:57 ` Andrew Morton
2004-03-11 8:45 ` Brad Laue
2004-03-11 9:28 ` Brad Laue
2004-03-11 10:08 ` Andrew Morton
2004-03-11 14:05 ` Yury V. Umanets
2004-03-11 17:22 ` Brad Laue [this message]
2004-03-11 18:09 ` Yury V. Umanets
2004-03-11 18:21 ` Brad Laue
2004-03-11 18:24 ` Brad Laue
2004-03-12 17:51 ` Brad Laue
2004-03-11 14:00 ` Yury V. Umanets
[not found] <Pine.LNX.4.21.0403111916570.3466-100000@linux08.ece.utexas.edu>
2004-03-12 7:06 ` Brad Laue
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=4050A047.9030603@brad-x.com \
--to=brad@brad-x.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