From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: robert.moore@intel.com
Cc: lv.zheng@intel.com, rafael.j.wysocki@intel.com,
linux-kernel@vger.kernel.org
Subject: [BUG] ACPI Error: ...
Date: Wed, 3 Feb 2016 11:04:32 +0000 [thread overview]
Message-ID: <20160203110432.GA4804@localhost> (raw)
v4.5-rc2, Macbook IVB, ACPI errors on boot:
[ 0.618382] ACPI Error: Needed type [Reference], found [Integer] ffff880260240fa0 (20150930/exresop-103)
[ 0.618448] ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff880261acb9e0), AE_AML_OPERAND_TYPE (20150930/psparse-542)
[ 1.581790] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-360)
[ 1.581885] ACPI Error: Method parse/execution failed [\_PR.CPU1._CST] (Node ffff88025f9962e0), AE_NOT_FOUND (20150930/psparse-542)
[ 1.585873] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-360)
[ 1.585968] ACPI Error: Method parse/execution failed [\_PR.CPU2._CST] (Node ffff88025f997b50), AE_NOT_FOUND (20150930/psparse-542)
[ 1.590267] ACPI Error: [\_PR_.CPU0._CST] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-360)
[ 1.590360] ACPI Error: Method parse/execution failed [\_PR.CPU3._CST] (Node ffff88025f996450), AE_NOT_FOUND (20150930/psparse-542)
ae90fbf562d733a392c7a0ffefe1e09b5a31c99c is the first bad commit
commit ae90fbf562d733a392c7a0ffefe1e09b5a31c99c
Author: Bob Moore <robert.moore@intel.com>
Date: Tue Dec 29 14:00:14 2015 +0800
ACPICA: Parser: Fix for SuperName method invocation
ACPICA commit 4b86d1046d06e462dae83ebcd5a66cc132a08f8f
SuperName parameters that are in fact control method invocations were
not handled correctly by the parser. This change fixes the problem
by identifying these properly as method invocations. This affects
about 14 different ASL operators that contain SuperName parameters.
ACPICA BZ 1002.
Link: https://github.com/acpica/acpica/commit/4b86d104
Link: https://bugs.acpica.org/show_bug.cgi?id=1002
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Lv Zheng <lv.zheng@intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
:040000 040000 3c9015e32a1af1bbe211d455138e4940fc313543 441172b0f1209cd86fc68f70a0ce7f0adb1f9e33 M drivers
next reply other threads:[~2016-02-03 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 11:04 Chris Bainbridge [this message]
2016-02-03 15:30 ` [BUG] ACPI Error: Moore, Robert
2016-02-03 15:38 ` Chris Bainbridge
2016-02-03 17:18 ` Moore, Robert
2016-02-03 17:35 ` Chris Bainbridge
2016-02-03 20:41 ` Moore, Robert
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=20160203110432.GA4804@localhost \
--to=chris.bainbridge@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.