From: root@mauve.demon.co.uk
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1 ACPI minor? proc problems.
Date: Sun, 20 Jul 2003 15:57:27 +0100 (BST) [thread overview]
Message-ID: <200307201457.PAA18000@mauve.demon.co.uk> (raw)
While beating on 2.6.0-test1, the only issue I've seen so far is:
cd /proc/
while true
do
find [^0-9k]* -exec wc \{} \; &
sleep 1
done
Causes some ACPI proc errors to be logged in syslog.
(bogus dates)
Mar 9 15:31:54 darkstar kernel: dswload-0269: *** Error: Looking up [BUFF] in
namespace, AE_ALREADY_EXISTS
Mar 9 15:31:54 darkstar kernel: psparse-0589 [1394] ps_parse_loop : During name lookup/catalog, AE_ALREADY_EXISTS
Mar 9 15:31:54 darkstar kernel: psparse-1121: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node cbf285c8), AE_ALREADY_EXISTS
Mar 9 15:31:54 darkstar kernel: dswload-0269: *** Error: Looking up [BUFF] in
namespace, AE_ALREADY_EXISTS
Mar 9 15:31:54 darkstar kernel: psparse-0589 [1394] ps_parse_loop : During name lookup/catalog, AE_ALREADY_EXISTS
Mar 9 15:31:54 darkstar kernel: psparse-1121: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node cbf285c8), AE_ALREADY_EXISTS
Mar 9 15:32:22 darkstar kernel: dswload-0269: *** Error: Looking up [BUFF] in
namespace, AE_ALREADY_EXISTS
Mar 9 15:32:22 darkstar kernel: psparse-0589 [1801] ps_parse_loop : During name lookup/catalog, AE_ALREADY_EXISTS
Mar 9 15:32:22 darkstar kernel: psparse-1121: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node cbf285c8), AE_ALREADY_EXISTS
Mar 9 15:32:22 darkstar kernel: dswload-0269: *** Error: Looking up [BUFF] in
namespace, AE_ALREADY_EXISTS
Mar 9 15:32:22 darkstar kernel: psparse-0589 [1801] ps_parse_loop : During name lookup/catalog, AE_ALREADY_EXISTS
Hmm, maybe it's not so trivial, when I went to copy the .config over from the
affected machine onto this one, to post, nfs locked up. (may of course
be unrelated)
If the .config / /proc/acpi/* is needed, then I'll send that on request.
reply other threads:[~2003-07-20 14:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200307201457.PAA18000@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).