All of lore.kernel.org
 help / color / mirror / Atom feed
* problem to access  /proc/acpi/battery/BAT1/* files
@ 2003-10-17 16:52 Paolo Dovera
  0 siblings, 0 replies; 2+ messages in thread
From: Paolo Dovera @ 2003-10-17 16:52 UTC (permalink / raw)
  To: linux-kernel

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

* problem to access /proc/acpi/battery/BAT1/* files
@ 2003-11-02 20:43 Paolo Dovera
  0 siblings, 0 replies; 2+ messages in thread
From: Paolo Dovera @ 2003-11-02 20:43 UTC (permalink / raw)
  To: linux-c-programming

Hi all,
on my RH9 2.6.0-test6 I noticed a strange log in /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


the problem arises when on my system two programs access concurrently 
the files into /proc/acpi/battery/BAT1/*

for example I run the 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 another xterm.

Is there any kind of lock to access the status of battery?

thanks for your time,
Paolo Dovera



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-11-02 20:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-02 20:43 problem to access /proc/acpi/battery/BAT1/* files Paolo Dovera
  -- strict thread matches above, loose matches on Subject: below --
2003-10-17 16:52 Paolo Dovera

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.