Please try latest kernel again. If it's still there, then please provide acpidump for your platform.

Created attachment 251881 [details]
dmesg for latest stable kernel

Created attachment 251891 [details]
ACPI dump on kernel 4.9

Error persist on latest stable kernel from Arch testing repo which is 4.9.3

Another thing I've noticed in the dmesg:

[    0.791607] platform MSFT0101:00: failed to claim resource 1
[    0.791612] acpi MSFT0101:00: platform device creation failed: -16

this one is also printed to the boot console while the others stay hidden in the dmesg.

MSFT error is due to the Bios's declaration of resources under the MSFT that, dynamically allocated resource just return the same address as the range declared in static resource.
4.10 -rc 4 should has more info dump on this.

Thanks for Yu to clarify the last error log.
You can also find detailed information at:
https://bugzilla.kernel.org/show_bug.cgi?id=188511
Please use this link to track the issue.

I think this is harmless:
[    0.617094] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.617129] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
If you can see real problems related to that, please file a separate bug to power components.

I'll help to check this error here:
[    0.482670] ACPI Error: No handler for Region [RAM_] (ffff8802760db900) [EmbeddedControl] (20160422/evregion-166)
[    0.482674] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160422/exfldio-299)
[    0.482677] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0._REG] (Node ffff8802760daca8), AE_NOT_EXIST (20160422/psparse-542)
[    0.482809] ACPI Error: No handler for Region [RAM_] (ffff8802760db900) [EmbeddedControl] (20160422/evregion-166)
[    0.482811] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160422/exfldio-299)
[    0.482813] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0._REG] (Node ffff8802760daca8), AE_NOT_EXIST (20160422/psparse-542)

Thanks
Lv

Looks like an duplicate of a solved bug.
While the patch is not upstreamed.
https://bugzilla.kernel.org/show_bug.cgi?id=102421

I've put the patch into the ACPICA pull request.
https://github.com/acpica/acpica/pull/200

Please apply attachment 212581 [details] and test again.

Thanks
Lv

Is it possible to patch it against 4.8.13 or only the latest rc?

I successfully applied it to ACPICA upstream with quilt.
So it should be no difference for linux due to the synchronized ACPICA release process.
Please apply it with patch -p 1 < "saved attachment 212581 [details] file"

Patch successfully gets rid off the mentioned error messages. Can we expect this on mainstream for 4.10 or will it be included in 4.11?

Thanks

*** This bug has been marked as a duplicate of bug 102421 ***

(In reply to Coşku Baş from comment #11)
> Patch successfully gets rid off the mentioned error messages.
> Can we expect this on mainstream for 4.10 or will it be included in 4.11?

This problem is actually related to _REG execution.
My recent finding reveals that Windows:
1. only executes _REG when a driver registers/unregisters region handlers,
   which means ACPICA's automatically _REG execution logic is not correct.
2. doesn't invoke _REG for address spaces that are default available.

From that point of view, we really need to change much.
And this commit looks more like a workaround for 2nd facts.

But since we only can do this in Linux upstream step by step.
and this commit can be considered as a regression safer approach,
I think the answer is:
Yes, I'll push it to ACPICA upstream.
You may be able to find it landed in Linux during 4.10/4.11 release cycles.

Thanks
Lv

Unfortunately 4.11 still has the error messages

Closing duplicated bugs.