Re: [coreboot] ACPI error booting Windows

[Alex Feinman]

Just to close the thread - I've found the problem. It was a reference to PMIC.OVTH in the mipi camera asl file. I've removed the entire MIPI block for now because my platform does not have a camera, but the underlying issue should be easy to solve if needed
________________________________
From: Matt DeVillier 
Sent: Wednesday, April 25, 2018 8:50 PM
To: [e-mail]
Cc: coreboot
Subject: Re: [coreboot] ACPI error booting Windows

you can take a look at all my configs as as well as all the patches in my tree in my github there.  They aren't all fully up to date, but should be useful.  Check Caroline, Cave, Chell, Sentry for Skylake CrOS devices, which should all be the same ACPI-wise as kblrvp3.  I haven't pushed the config for the KabyLake CrOS device yet since it's not yet released, but it it doesn't require any additional patches from what's in my tree now.

On Wed, Apr 25, 2018 at 9:02 PM Alex Feinman <[e-mail]> wrote:
That unfortunately did not help. Would it be possible to take a look at your .config? Perhaps I'll be able to spot something
________________________________
From: Matt DeVillier <[e-mail]>
Sent: Wednesday, April 25, 2018 4:14 PM
To: [e-mail]
Cc: coreboot
Subject: Re: [coreboot] ACPI error booting Windows

I have Windows booting on a KBL CrOS device, and looking at my tree, pretty sure the only change I have that would potentially address that error is adding the pcon value to the IGD ACPI OpRegion header:
https://github.com/MattDevo/coreboot/commit/3349065354709c852765555168272469...

there were a few others but they've all since been merged upstream

On Wed, Apr 25, 2018 at 6:00 PM Alex Feinman <[e-mail]> wrote:
I've built a Coreboot image (from the HEAD) for my custom Kaby Lake board. The build uses Chrome EC and is based on kblrvp3 mainboard configuration. Linux runs fine, but when I attempt to install Windows 10 (or boot a preinstalled Windows image from USB) I instantly get ACPI_BIOS_ERROR (0xC00000A5). There is a Microsoft document that provides a large amount of possible reasons for this error, however I can't even narrow it down because cleverly Windows 10 no longer prints the bug check parameters, at least not in this case.

I would appreciate some pointers if possible.

Thank you
Alex
--
coreboot mailing list: [e-mail]
https://mail.coreboot.org/mailman/listinfo/coreboot