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 <coreb...@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 < [coreb...@fe80.eu]( > http://coreb...@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-le...@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 _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
