From: "Aurélien Francillon" <aurel@naurel.org>
To: Stefan Seyfried <seife@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] linux-2.6.11-rc3 probably in ACPI battery procfs ...
Date: Tue, 08 Feb 2005 18:51:42 +0100 [thread overview]
Message-ID: <4208FC2E.4010306@naurel.org> (raw)
In-Reply-To: <4208BC68.8070700@suse.de>
Stefan Seyfried wrote:
> aurelien francillon wrote:
>
>>hi,
>>since just before linux-2.6.11-rc3 ( i think it's rc2-bk10 ) there
>>seems to have a bug in the acpi part of the proc file system :
>>reading /proc/acpi/battery/BAT0/info takes a very long time and locks
>>up the computer, time gives:
>>cat /proc/acpi/battery/BAT0/info 0.00s user 6.76s system 12030% cpu
>>0.056 total
>>I notice it because kde reads it every 10seconds ... so the compuer gets
>>locked for ~5s every ~10s ...
>
>
>>computer is a dell D600 laptop,
>
>
> I have seen the same on a D600 and an Compaq Armada E500, not 6 seconds
> but ~1.2 seconds. Try to put a
>
> #define ACPI_ENABLE_OBJECT_CACHE 1
>
> at the end of include/acpi/acpi.h (before the last #endif), this sort of
> fixed it for me (now it again needs ~0.2 seconds, still way too long,
> but the same as with the last good 2.6.11-rc2-bk9).
>
> Good luck :-)
>
> Stefan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
that's "fixed" it for me too,
thanks
Aurel
--
Lat: 45:11:43N (45.1954)
Lon: 5:43:36E ( 5.7268)
next prev parent reply other threads:[~2005-02-08 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 11:48 [BUG] linux-2.6.11-rc3 probably in ACPI battery procfs aurelien francillon
2005-02-08 13:19 ` Stefan Seyfried
2005-02-08 17:51 ` Aurélien Francillon [this message]
2005-02-09 16:05 ` Stefan Seyfried
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=4208FC2E.4010306@naurel.org \
--to=aurel@naurel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seife@suse.de \
/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.