From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Dell Inspiron 8200, 2.5.69, ACPI problems
Date: 08 May 2003 11:36:45 -0400 [thread overview]
Message-ID: <1052408205.1531.27.camel@slappy> (raw)
In-Reply-To: <3EB9D625.1060704@blue-labs.org>
As a 'me too' the same is true on inspiron 8500, under 2.4 and 2.5.
I've got a fixed-up DSDT installed (see the guide at
http://www.cpqlinux.com/acpi-howto.html and
http://developer.intel.com/technology/iapc/acpi/bios_override.htm ..)
and that drops some of the noise (and fixes some of the missing bits)
but acpid and others (basically any acpi call) results in similar
messages.
Its not a kernel issue (well, its a warning from the kernel.. but the
kernel can't fix this directly.) Turning off ACPI debugging will
probably make it stop, but the underlying issue is Dell (and many other
vendors) don't test their ACPI firmware under anything except windows.
>From Intel's ACPI site (and this applies to many acpi issues):
Q16. What is the "implicit return" issue, and why hasn't it been fixed?
A16. {cut} Due to an errata, this bug does not manifest itself on
Windows' ACPI implementations, and therefore was not detected when OEMs
tested their systems using that OS.
We've made the decision for now to not be bug-for-bug compatible with
existing ACPI OS implementations. We are implementing according to the
ACPI specification's requirements, and hopefully this may drive better
compliance on all operating systems.
On Wed, 2003-05-07 at 23:59, David Ford wrote:
> ACPI: AC Adapter [AC] (on-line)
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> ACPI: Battery Slot [BAT0] (battery present)
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> ACPI-0207: *** Warning: Buffer created with zero length in AML
> -0091: *** Error: ut_allocate: Attempt to allocate zero bytes
> ACPI: Battery Slot [BAT1] (battery present)
> ACPI: Lid Switch [LID]
> ACPI: Power Button (CM) [PBTN]
> ACPI: Sleep Button (CM) [SBTN]
> ACPI: Processor [CPU0] (supports C1 C2, 8 throttling states)
> ACPI: Thermal Zone [THM] (25 C)
>
>
> -
> 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/
--
Disconnect <lkml@sigkill.net>
prev parent reply other threads:[~2003-05-08 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 3:59 Dell Inspiron 8200, 2.5.69, ACPI problems David Ford
2003-05-08 15:36 ` Disconnect [this message]
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=1052408205.1531.27.camel@slappy \
--to=lkml@sigkill.net \
--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