From: Len Brown <lenb@kernel.org>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Subject: Prevent acpi_run_osc from using NULL objects (was: Re: Oops in ACPI with git latest)
Date: Fri, 24 Oct 2008 16:27:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0810241625170.3056@localhost.localdomain> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D8308580AA7FA4F@orsmsx503.amr.corp.intel.com>
> We've just recently deployed a new module that validates the inputs and outputs
> for the predefined ACPI methods (Those that start with underscore).
>
> That is the source of these messages:
>
> > > ACPI Warning (nspredef-0252): \_SB_.PCI0._OSC: Parameter count mismatch - ASL declared 5, expected 4 [20080926]
> > > ACPI Error (nspredef-0163): \_SB_.PCI0._OSC: Missing expected return value [20080926]
>
> For the initial version of this module, we only output messages when the inputs and/or
> outputs don't match the requirements of the ACPI specification.
>
> We can change this to returning exceptions in the future.
I expect we're going to have a bunch of false positives with this one,
and indeed may need to even pare the warnings back to only
when CONFIG_ACPI_DEBUG, or acpi=strict or something.
-Len
next prev parent reply other threads:[~2008-10-24 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 19:45 Oops in ACPI with git latest James Bottomley
2008-10-23 20:42 ` Rafael J. Wysocki
2008-10-23 22:34 ` Moore, Robert
2008-10-24 1:27 ` James Bottomley
2008-10-24 6:57 ` Rafael J. Wysocki
2008-10-24 11:49 ` [PATCH] Subject: Prevent acpi_run_osc from using NULL objects (was: Re: Oops in ACPI with git latest) Rafael J. Wysocki
2008-10-24 15:02 ` Moore, Robert
2008-10-24 20:27 ` Len Brown [this message]
2008-10-24 20:43 ` Moore, Robert
2008-10-24 14:57 ` Oops in ACPI with git latest Moore, Robert
2008-10-24 18:04 ` Jesse Barnes
2008-10-24 18:43 ` Rafael J. Wysocki
2008-10-24 19:22 ` Jesse Barnes
2008-10-24 19:50 ` Rafael J. Wysocki
2008-10-24 20:42 ` Len Brown
2008-10-24 1:17 ` James Bottomley
2008-10-24 6:47 ` Rafael J. Wysocki
2008-10-24 15:04 ` Moore, Robert
2008-10-24 1:17 ` Lin Ming
2008-10-24 15:37 ` James Bottomley
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=alpine.LFD.1.10.0810241625170.3056@localhost.localdomain \
--to=lenb@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=robert.moore@intel.com \
/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