All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Dovera <pdovera@bmind.it>
To: linux-kernel@vger.kernel.org
Subject: problem to access  /proc/acpi/battery/BAT1/* files
Date: Fri, 17 Oct 2003 18:52:02 +0200	[thread overview]
Message-ID: <3F901E32.2000203@bmind.it> (raw)

Hi all,
I'm using the kernel 2.6.0-test6/7 and I've noticed this warning into 
/var/log/messages

Oct 17 18:15:16 localhost kernel:  dswload-0269: *** Error: Looking up 
[PBST] in namespace, AE_ALREADY_EXISTS
Oct 17 18:15:16 localhost kernel:  psparse-0589 [293932] 
ps_parse_loop         : During name lookup/catalog, AE_ALREADY_EXISTS
Oct 17 18:15:16 localhost kernel:  psparse-1121: *** Error: Method 
execution failed [\_SB_.PCI0.LPC0.BAT1._BST](Nodec12ab328), 
AE_ALREADY_EXISTS
Oct 17 18:15:25 localhost kernel:  dswload-0269: *** Error: Looking up 
[PBST] in namespace, AE_ALREADY_EXISTS
Oct 17 18:15:25 localhost kernel:  psparse-0589 [294043] 
ps_parse_loop         : During name lookup/catalog, AE_ALREADY_EXISTS
Oct 17 18:15:25 localhost kernel:  psparse-1121: *** Error: Method 
execution failed [\_SB_.PCI0.LPC0.BAT1._BST] (Node c12ab328), 
AE_ALREADY_EXISTS

when some programs concurrently access to /proc/acpi/battery/BAT1/* files.

For example I use cpufrequency (a daemon to switch CPU frequency on my 
P4 laptop) http://sourceforge.net/projects/cpufrequency/
(this program checks every some seconds the status of battery)
and I use
        watch -n 8 "cat /proc/acpi/battery/BAT1/*"
to see the battery state in a xterm.

Is there some lock to access to status of battery?

thanks for your time,
Paolo Dovera




             reply	other threads:[~2003-10-17 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-17 16:52 Paolo Dovera [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-02 20:43 problem to access /proc/acpi/battery/BAT1/* files Paolo Dovera

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=3F901E32.2000203@bmind.it \
    --to=pdovera@bmind.it \
    --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 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.