Messages in this thread | | | Date | Fri, 17 Oct 2003 18:52:02 +0200 | From | Paolo Dovera <> | Subject | problem to access /proc/acpi/battery/BAT1/* files |
| |
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
- 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/
| |