Issue #392 has been updated by Paul Menzel.
Subject changed from Coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" to coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error"
1. Please attach a photo of the BSOD, or copy all messages from it. 1. Please attach the coreboot log of both images. (If you do not have GNU/Linux installed, you can start it from a USB device with a GNU/Linux live image. 1. If you can flash external to potentially recover, please bisect the issue.
---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-979
* 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)