public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Malte Thoma <thoma-xhPu7QH+N+StU9/U+hoEgQ@public.gmane.org>
To: Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>
Cc: ACPI-Devel
	<Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: performance problems?
Date: Mon, 16 Dec 2002 09:06:07 +0100	[thread overview]
Message-ID: <3DFD896F.3020302@uni-muenster.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0211191552030.31104-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>



Markus Gaugusch wrote:
> On Nov 19, Loic Jaquemet <ljaquemet-BNG0eM9rGRi0IRkH3yUr9EW4647UYGdYQQ4Iyu8u01E@public.gmane.org> wrote:
> 
>>i'am using 2.4.19 + around october patch ( I'll check that this evening )
>>on sony vaio fx502
>>[...]
>>when I fetch the /proc/acpi/<batteriesxxx>/state|info files, I get a 1-2
>>second freeze| lag ..
>>[...]
>>I'm not sure, but i think i didn't have this problem on pre-september
>>patches ..
> 
> No, it has been present before. I have an FX405 and can't use any battery
> monitor applet that reads the info file. Even a 'cat
> /proc/acpi/battery/BAT1/info' causes a noticable peak in my cpu monitor
> (kernel time). At least, it doesn't freeze keyboard anymore, thanks to the
> ACPI people!

You can try my 'heatload'. Because I have an Sony, too, I have made a 
workaround for the 'info'-File.
(I'm using an older ACPI-patch for kernel 2.4.18)


Greetings,

Malte




-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

  parent reply	other threads:[~2002-12-16  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-19 13:37 performance problems? Thomas List
2002-11-19 13:54 ` Loic Jaquemet
     [not found]   ` <3DDA42A3.35F6BFE1-BNG0eM9rGRi0IRkH3yUr9EW4647UYGdYQQ4Iyu8u01E@public.gmane.org>
2002-11-19 14:54     ` Markus Gaugusch
     [not found]       ` <Pine.LNX.4.44.0211191552030.31104-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2002-11-19 15:59         ` James D Strandboge
     [not found]           ` <1037721583.1432.12.camel-Ty44UuN9vPJ5T2F9fCU5s856D9/Od9gv@public.gmane.org>
2002-11-19 17:11             ` Ducrot Bruno
2002-11-19 16:39         ` Thomas List
2002-12-16  8:06         ` Malte Thoma [this message]
     [not found] ` <3DDA3E96.50906-vA1bhqPz9FBZXbeN9DUtxg@public.gmane.org>
2002-11-19 14:01   ` Nils Faerber
2002-11-19 14:40   ` David Douard
     [not found]     ` <200211191540.58738.douard-nJJpUPIbDOA@public.gmane.org>
2002-11-19 15:23       ` Ducrot Bruno
2002-11-19 16:00   ` Thomas List
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19 19:22 Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD04C7A520-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-11-19 21:16   ` Thomas List
2002-11-19 22:29   ` Markus Gaugusch

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=3DFD896F.3020302@uni-muenster.de \
    --to=thoma-xhpu7qh+n+stu9/u+hoegq@public.gmane.org \
    --cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org \
    --cc=thoma-iYtK5bfT9M8b1SvskN2V4Q@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