From: <stewart@neuron.com>
To: linux-kernel@vger.kernel.org
Subject: kapm-idled : is this a bug?
Date: Mon, 11 Dec 2000 12:00:29 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.10.10012111151470.2070-100000@localhost> (raw)
I've recently begun testing my laptop on the latest 2.4.0-test12-pre[78]
kernels. When freshly booted and nothing producing a load on the system,
top reports a process called 'kapm-idled' consuming between 60% an 85%
of CPU cycles. If I induce a load on the machine (by recompiling kernel
modules, for example), this process slowly loses priotity and stops
consuming cycles. Once the compilation is complete, it climbs back up to
the top of the stack again. Here are top snapshots taken at about 90
second intervals:
PID USER PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM TIME COMMAND
3 root 20 0 0 0 0 SW 0 81.7 0.0 1:14 kapm-idled
3 root 20 0 0 0 0 SW 0 76.8 0.0 1:41 kapm-idled
* 3 root 9 0 0 0 0 SW 0 0.0 0.0 3:09 kapm-idled
3 root 14 0 0 0 0 SW 0 60.5 0.0 3:39 kapm-idled
3 root 20 0 0 0 0 SW 0 85.7 0.0 5:15 kapm-idled
* during re-compilation of kernel modules, kapm-idled was de-prioritized
and took up no CPU cycles. after the compilation completed, the task
priority increased until it was again consuming hi percentages.
I've consistently re-produced this on my Dell Latitude CS laptop. I'm
wondering if this will reduce battery life since the CPU is constantly
being loaded instead of properly idled.
Stewart
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-11 5:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 17:00 stewart [this message]
2000-12-11 5:11 ` Robert M. Love
2000-12-11 15:16 ` Rik van Riel
2000-12-11 15:45 ` Nick Holloway
2000-12-11 18:56 ` stewart
2000-12-11 19:26 ` Richard B. Johnson
2000-12-11 19:28 ` Mark Hahn
2000-12-11 23:49 ` Kurt Garloff
2000-12-15 22:40 ` Pavel Machek
2000-12-17 2:18 ` Jamie Lokier
2000-12-17 15:26 ` Igmar Palsenberg
2000-12-20 9:11 ` Pavel Machek
2000-12-21 11:00 ` Igmar Palsenberg
2000-12-21 12:28 ` Pavel Machek
2000-12-21 19:27 ` Albert D. Cahalan
2000-12-22 10:02 ` Pavel Machek
2000-12-22 18:50 ` Igmar Palsenberg
2000-12-22 18:45 ` Igmar Palsenberg
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=Pine.LNX.4.10.10012111151470.2070-100000@localhost \
--to=stewart@neuron.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
all inboxes | Powered by JetHome®