From: Pippo Caloggero <matheng10-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: cpu hog reading battery info
Date: Fri, 17 Jun 2005 15:01:42 +0200 [thread overview]
Message-ID: <42B2C9B6.2080400@hotmail.com> (raw)
Hi after upgrading to 2.6.11 doing a
cat /proc/acpi/battery/BAT0/info
hogs my cpu to the point that X and the mouse block for 1 second.
This is especially annoyng as for example kde battery monitor do that
every 20 secs to read battery capacity.
Is it a known bug? Is there some way to dig into it?
Thank you very much
Matteo
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-06-17 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 13:01 Pippo Caloggero [this message]
[not found] ` <42B2C9B6.2080400-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2005-06-17 13:36 ` cpu hog reading battery info Oisín Mac Fhearaí
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=42B2C9B6.2080400@hotmail.com \
--to=matheng10-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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