Issue #392 has been updated by Pawel Radomychelski. CoreBoot 4.15 [ 0.172669] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.172734] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.172796] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000cbfff window] [ 0.172871] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000fffff window] [ 0.172946] pci_bus 0000:00: root bus resource [mem 0x8ea00000-0xefffffff window] [ 0.173020] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window] CoreBoot 4.17 [ 0.172744] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.172809] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.172872] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000cbfff window] [ 0.172948] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000fffff window] [ 0.173022] pci_bus 0000:00: root bus resource [mem 0x8ea00000-0xefffffff window] [ 0.173096] pci_bus 0000:00: root bus resource [mem 0x471600001-0xfffffffff window] [ 0.173170] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff window] ---------------------------------------- Bug #392: Coreboot 4.16 & 4.17 - SeaBios Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-969 * Author: Pawel Radomychelski * Status: New * Priority: High * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. Related links updated Priority changed from High to Normal ---------------------------------------- Bug #392: Coreboot 4.16 & 4.17 - SeaBios Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-975 * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. File CB4.17_BSOD.jpg added Arthur Heymans wrote in #note-7:

Can you check if https://review.coreboot.org/c/coreboot/+/65250 fixes it?

@Arthur: This patch unfortunately doesn't fix it. :( @Paul: 1. Image of BSOD attached. No additional information. 2. How can i create coreboot.log of both images? 3. I can flash externaly and have also Debian 11 on another drive, so its no problem for me. ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-982 * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Lance Zhao. If we can get a windows crash dump will be easier to debug the issue, we can use windbg to open generated dump file(memory.dmp most of the time). Then the detail info normally included, ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-988 * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. File CB417.log added File CB415.log added ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-991 * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. File 062322-6125-01.dmp added ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-993 * 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) 062322-6125-01.dmp (719 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Lance Zhao. Output of minidump shows that's not acpi bios error. 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* **DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)** An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: ffffdd80db3e1760, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8036dea1981, address which referenced memory Debugging Details: BUGCHECK_CODE: d1 BUGCHECK_P1: ffffdd80db3e1760 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8036dea1981 READ_ADDRESS: Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd ffffdd80db3e1760 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: notmyfault64.exe TRAP_FRAME: fffffe87853e24a0 -- (.trap 0xfffffe87853e24a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000730055 rbx=0000000000000000 rcx=ffffdd80d0000340 rdx=0000000000000890 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8036dea1981 rsp=fffffe87853e2630 rbp=0000000000000002 r8=ffffdd80e25e2da0 r9=0000000000000000 r10=ffffdd80d00002c0 r11=ffffdd80db3c1750 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc myfault+0x1981: fffff803`6dea1981 8b03 mov eax,dword ptr [rbx] ds:00000000`00000000=???????? Resetting default scope STACK_TEXT: fffffe87`853e2358 fffff803`70609d69 : 00000000`0000000a ffffdd80`db3e1760 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffffe87`853e2360 fffff803`70606069 : 00000000`00000000 ffffca09`b6b03740 00000000`00000f4d 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffffe87`853e24a0 fffff803`6dea1981 : ffffffff`ffffffff ffffca09`af887080 fffffe87`853e2730 00000000`00000aa0 : nt!KiPageFault+0x469 fffffe87`853e2630 ffffffff`ffffffff : ffffca09`af887080 fffffe87`853e2730 00000000`00000aa0 00000000`00000000 : myfault+0x1981 fffffe87`853e2638 ffffca09`af887080 : fffffe87`853e2730 00000000`00000aa0 00000000`00000000 fffff803`6dea1d3d : 0xffffffff`ffffffff fffffe87`853e2640 fffffe87`853e2730 : 00000000`00000aa0 00000000`00000000 fffff803`6dea1d3d ffffdd80`00730055 : 0xffffca09`af887080 fffffe87`853e2648 00000000`00000aa0 : 00000000`00000000 fffff803`6dea1d3d ffffdd80`00730055 00000000`000f00ff : 0xfffffe87`853e2730 fffffe87`853e2650 00000000`00000000 : fffff803`6dea1d3d ffffdd80`00730055 00000000`000f00ff 00000001`00000000 : 0xaa0 SYMBOL_NAME: myfault+1981 MODULE_NAME: myfault IMAGE_NAME: myfault.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1981 FAILURE_BUCKET_ID: AV_myfault!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {9745090a-9bce-ccba-c096-ca6e9ca04c64} Followup: MachineOwner ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-997 * 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) 062322-6125-01.dmp (719 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. Sorry @Lance Zhao, but this is the wrong dump. It was created by the app, NotMyFault, which i used to play around with dumps. It looks so, that the dump we need is not beeing created... ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1002 * 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) 062322-6125-01.dmp (719 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. File CB416.log added File dmesg_cb416.txt added I could build Coreboot 4.16 with replacing the folder src/drivers/intel/gma/acpi from Coreboot 4.15. With replaced acpi folder Windows 10 works without BSOD. Unfortunately the same trick doesn't work for Coreboot 4.17. With 4.17 and acpi folder from 4.15 Windows 10 crashed very early with ACPI Error BSOD. crash dump is also not created. Maybe because its crashes very early. ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1015 * 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) dmesg_cb416.txt (81.8 KB) CB416.log (128 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Pawel Radomychelski. File dmesg_cb416.txt added ---------------------------------------- Bug #392: coreboot 4.16 & 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1017 * 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Olexandr Nesterenko. I use t420 with Ivy Bridge CPU Run bisect 4.16 - 4.17 and result: `# first bad commit: [f8daf86282c1be33643ace4e9f453e7548cab41c] nb/intel/sandybridge/acpi: Support setting PCI bars above 4G` After this commit i have BSOD ACPI Error. ---------------------------------------- Bug #392: coreboot 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1048 * Author: Pawel Radomychelski * Status: New * Priority: Normal * Category: board support * Target version: 4.17 * Start date: 2022-06-18 * Affected versions: 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Lance Zhao. Do we believe we need to have extra protection to check A4GB is not zero as well? Need to see the debug print about A4GB and A4GS at this point. Lance Pawel Radomychelski <coreboot@fe80.eu> 于2022年7月24日周日 17:00写道：

Issue #392 has been updated by Pawel Radomychelski.

дуже дякую, Олексанре!

Thank you very much, Oleksandr for bisecting the problem!

hope the fix will be applied to the master branch!

Kind regards

Pawel Radomychelski

On July 24, 2022 at 9:19 AM Olexandr Nesterenko < [coreboot@fe80.eu]( http://coreboot@fe80.eu) > wrote:

Issue #392 has been updated by Olexandr Nesterenko.

I use t420 with Ivy Bridge CPU Run bisect 4.16 - 4.17 and result: `# first bad commit: [f8daf86282c1be33643ace4e9f453e7548cab41c] nb/intel/sandybridge/acpi: Support setting PCI bars above 4G` After this commit i have BSOD ACPI Error.

---------------------------------------- Bug #392: coreboot 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" [ https://ticket.coreboot.org/issues/392#change-1048](https://ticket.coreboot.org/issues/392#change-1048)

* Author: Pawel Radomychelski * Status: New * Priority: Normal * Category: board support * Target version: 4.17 * Start date: 2022-06-18 * Affected versions: 4.17, master * Related links: [ https://ticket.coreboot.org/issues/327](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](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)

-- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: [ https://ticket.coreboot.org/my/account](https://ticket.coreboot.org/my/account)

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

* Author: Pawel Radomychelski * Status: New * Priority: Normal * Category: board support * Target version: 4.17 * Start date: 2022-06-18 * Affected versions: 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)

-- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org

---------------------------------------- Bug #392: coreboot 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1050 * Author: Pawel Radomychelski * Status: New * Priority: Normal * Category: board support * Target version: 4.17 * Start date: 2022-06-18 * Affected versions: 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

Issue #392 has been updated by Michael Büchler. I was getting this problem with a port I was working on (Intel DQ67SW, not on Gerrit yet). Since rebasing this port on 4.18 the issue is gone for me. I tested Windows 10 21H2 with SeaBIOS and EDK II (mrchromebox/uefipayload_202107). The live installer on a USB drive and the installation on a disk are both booting without the ACPI Error. ---------------------------------------- Bug #392: coreboot 4.17 - SeaBIOS Windows 10 BSOD "ACPI Error" https://ticket.coreboot.org/issues/392#change-1369 * Author: Pawel Radomychelski * Status: Response Needed * Priority: Normal * Category: board support * Target version: 4.17 * Start date: 2022-06-18 * Affected versions: 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) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account