[coreboot] [coreboot - Bug #392] coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error"

[Pawel Radomychelski]

Issue #392 has been updated by Pawel Radomychelski.

Paul Menzel wrote in #note-23:
> Nice test. Please bisect with
> $ git bisect start 4.16 4.15 -- src/drivers/intel/gma/acpi
>
> and build and test each commit that is shown. (This only works, if the regression really is in `src/drivers/intel/gma/acpi` – otherwise, just use `git bisect start 4.16 4.15`.)

Thanks for the info, but i am not very familiar with git commands.

When i am on the 4.16 branch (with default src/drivers/intel/gma/acpi) and i enter the command:

git bisect start 4.16 4.15 -- src/drivers/intel/gma/acpi
warning: refname '4.16' is ambiguous.
Switched to branch '4.16_branch'
Your branch is up to date with 'origin/4.16_branch'.
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[24eb605280b737ee63c72ede451bd5a7d0dce5e2] drivers/intel/gma/acpi: Replace Multiply(a,b) with ASL 2.0 syntax

```
What should i do now?

Sorry for dumb questions....

----------------------------------------
Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error"
https://ticket.coreboot.org/issues/392#change-1019

* Author: Pawel Radomychelski
* Status: New
* Priority: Normal
* Category: board support
* Target version: 4.17
* Start date: 2022-06-18
* Affected versions: 4.16, 4.17, master
* Related links: https://ticket.coreboot.org/issues/327
* Affected hardware: Lenovo ThinkPad X230 Tablet
* Affected OS: Windows 10
----------------------------------------
Since CoreBoot 4.16 my Windows 10 cant boot from SeaBios, i get BSOD with "ACPI Error" very early.

Don't know which commit exactly brakes ACPI, but i can say, that in my CoreBoot 4.15 Image from 11/09/2021 Windows 10 is booting just fine from SeaBIOS.
Some time later under CoreBoot 4.16 i saw that windows is BSODing. Tried yesterday with CoreBoot 4.17 and its still broken.

I think, since CB4.16 there is something broken in ACPI. As i read, the problem is, that ACPI reserves some memory area, which in Windows is reserved for the system.

This [[https://ticket.coreboot.org/issues/327]] seems to be a similar problem, but the guy is using TianoCore instead of SeaBIOS.
Changing the line
OperationRegion (OPRG, SystemMemory, ASLS, 0x2000)
to
OperationRegion (OPRG, SystemMemory, ASLS, 0x1000)
doesnt fix it for SeaBios, but fix it for TianoCore.

---Files--------------------------------
dmesg_cb415.txt (78.9 KB)
dmesg_cb417.txt (79.9 KB)
.config (19.7 KB)
CB4.17_BSOD.jpg (143 KB)
CB415.log (46.4 KB)
CB417.log (128 KB)
CB416.log (128 KB)
dmesg_cb416.txt (81.8 KB)