From: Michael Stucki <mundaun-OI3hZJvNYWs@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Strange error message: Could not allocate new owner_id
Date: Sun, 17 Jul 2005 16:21:43 +0200 [thread overview]
Message-ID: <o46qq2-k8a.ln1@nb02.mstucki.net> (raw)
Hello,
yesterday I've upgrade my laptop from 2.6.11 to 2.6.12. Applied Bootsplash,
SwSusp and the ACPI patches.
All went trough and my laptop is up again.
However, I notice a lot of error messages in the syslog file:
--- cut ---
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1.UPBI] (Node c1434ee0), AE_OWNER_ID_LIMIT
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node c1434f20), AE_OWNER_ID_LIMIT
kernel: ACPI-0098: *** Error: Could not allocate new owner_id (32 max), AE_OWNER_ID_LIMIT
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1.UPBI] (Node c1434ee0), AE_OWNER_ID_LIMIT
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node c1434f20), AE_OWNER_ID_LIMIT
kernel: ACPI-0098: *** Error: Could not allocate new owner_id (32 max), AE_OWNER_ID_LIMIT
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node c1434f20), AE_OWNER_ID_LIMIT
kernel: ACPI-0098: *** Error: Could not allocate new owner_id (32 max), AE_OWNER_ID_LIMIT
kernel: ACPI-0509: *** Error: Method execution failed [\_SB_.BAT1._BIF] (Node c1434f20), AE_OWNER_ID_LIMIT
kernel: ACPI-0098: *** Error: Could not allocate new owner_id (32 max), AE_OWNER_ID_LIMIT
last message repeated 36 times
last message repeated 66 times
last message repeated 66 times
last message repeated 37 times
kernel: codec_semaphore: semaphore is not ready [0x1][0x701300]
kernel: codec_read 0: semaphore is not ready for register 0x2c
kernel: ACPI-0098: *** Error: Could not allocate new owner_id (32 max), AE_OWNER_ID_LIMIT
last message repeated 33 times
--- cut ---
It doesn't seem to hurt much, but as a bad side-effect of this, I am not
able to watch the battery status anymore.
Thanks for any help!
- michael
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
reply other threads:[~2005-07-17 14:21 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=o46qq2-k8a.ln1@nb02.mstucki.net \
--to=mundaun-oi3hzjvnyws@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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