From: Peter Wu <peter@lekensteyn.nl>
To: Lv Zheng <lv.zheng@intel.com>
Cc: Rick Kerkhof <rick.2889@gmail.com>,
Bartosz Skrzypczak <barteks2x@gmail.com>,
Robert Moore <robert.moore@intel.com>,
linux-acpi@vger.kernel.org
Subject: ACPI module-level code (MLC) not working?
Date: Tue, 8 Nov 2016 10:49:51 +0100 [thread overview]
Message-ID: <20161108094951.GA20849@al> (raw)
Hi Lv,
According to some tests, setting acpi_gbl_parse_table_as_term_list to
TRUE does is not effective. The code within the If-block is still not
executed early enough or something else is wrong.
Previously Rick had an issue with an Acer Aspire V7-582PG where the dGPU
could not be powered off and I demonstrated an isolated test case in
http://www.spinics.net/lists/linux-acpi/msg70069.html
In Bartosz's case, the dGPU cannot be powered on (also using nouveau),
preventing suspend from working. Situation is as follows (tested with
Linux 3.16, 4.8.4, 4.9-rc2, 4.9-rc4):
His Lenovo IdeaPad Z510 laptop (BIOS date 2014) enables power resources
and related _PR3 objects under the conditional If(_OSI("Windows 2013")).
Both with and without acpi_gbl_parse_table_as_term_list set to TRUE, the
module-level code is not loaded properly. Via a SSDT override, it was
confirmed that removing the If conditional results in the expected
behavior.
Various details are given in https://github.com/Bumblebee-Project/bbswitch/issues/142
including lots of dmesg logs (see posts at the bottom).
With above MLC flag set (v4.9-rc4): https://pastebin.com/raw/vCEPGezX
With SSDT override (v4.9-rc2): https://pastebin.com/raw/3Fsf2VPU
If you would like a new bugzilla entry or have some patches to test, you
know where to find us :)
--
Kind regards,
Peter Wu
https://lekensteyn.nl
next reply other threads:[~2016-11-08 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 9:49 Peter Wu [this message]
2016-11-08 17:35 ` ACPI module-level code (MLC) not working? Zheng, Lv
2016-11-08 17:56 ` Peter Wu
2016-11-09 0:07 ` Zheng, Lv
2016-11-09 0:32 ` Peter Wu
2016-11-09 0:43 ` Zheng, Lv
2016-11-09 1:17 ` Peter Wu
2016-11-09 1:26 ` Zheng, Lv
2016-11-09 1:02 ` Zheng, Lv
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=20161108094951.GA20849@al \
--to=peter@lekensteyn.nl \
--cc=barteks2x@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rick.2889@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox