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
_______________________________________________
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org
