> Stoney has the same issue, pretty sure it's related to a memory address range being incorrectly marked or something similar (based on the DWORD output of the BSOD), but never bothered to troubleshoot
How did you come to that conclusion? > Highly possible you don't need to connect live sessions using windbg, you can analysis the generated dump file to simply open with windbg. The installer media doesn't seem to create a dump :( So I was finally able to get the debugger to attach. There are two bcd stores on the installer USB, one for BIOS and one for UEFI. I was modifying the BIOS one. Once I updated the UEFI store the OS seemed to hang for the debugger. The second problem was that the serial port needs to be using a 1.8MHz base clock. This way the OS can calculate the correct divisor to use. Apparently linux also assumes a 1.8MHz base clock. So once I got all that fixed I was able to attach with the debugger. Unfortunately the debugger was non-functional: https://docs.microsoft.com/en-us/answers/questions/232781/debugging-acpi-bios-error-with-windbg.html I then decided to ditch the install media and instead created a WinPE boot image that has a full OS install. This allowed me to modify the registry values offline to enable displaying the error codes: https://windowsreport.com/bsod-details-windows-8/ With that I was finally able to get the error codes: 0x0000000000000000 OxFFFFD38AC66EC7FO Ox000000004449555F 0x0000000000000000 I need to figure out how to decode them. On Wed, Jan 13, 2021 at 7:37 PM Lance Zhao <lance.z...@gmail.com> wrote: > Highly possible you don't need to connect live sessions using windbg, you > can analysis the generated dump file to simply open with windbg. > > > Raul Rangel <rran...@chromium.org> 于2021年1月14日周四 上午6:21写道： > >> I'm trying to boot the Windows 10 Installer on a picasso based device >> using coreboot + tianocore. I keep getting a BSOD after the windows logo >> shows with the very descriptive stop code `ACPI BIOS ERROR`. >> >> I've enabled bootdebug on the USB stick using the following: >> >> bcdedit /store H:\boot\bcd /bootdebug {bootmgr} on >> bcdedit /store H:\boot\bcd /bootdebug {default} on >> bcdedit /store H:\boot\bcd /debug {debug} on >> >> Here is the BCD: >> >> C:\Windows\system32>bcdedit /store h:\boot\bcd >> Windows Boot Manager >> -------------------- >> identifier {bootmgr} >> description Windows Boot Manager >> locale en-US >> inherit {globalsettings} >> bootdebug Yes >> default {default} >> displayorder {default} >> toolsdisplayorder {memdiag} >> timeout 30 >> >> Windows Boot Loader >> ------------------- >> identifier {default} >> device >> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} >> path \windows\system32\boot\winload.exe >> description Windows Setup >> locale en-US >> inherit {bootloadersettings} >> bootdebug Yes >> osdevice >> ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f} >> systemroot \windows >> bootmenupolicy Standard >> detecthal Yes >> winpe Yes >> debug Yes >> ems No >> >> C:\Windows\system32>bcdedit /store h:\boot\bcd /dbgsettings >> debugtype Serial >> debugport 1 >> baudrate 115200 >> >> >> I have also added the SPCR table: >> >> [000h 0000 4] Signature : "SPCR" [Serial Port >> Console Redirection table] >> [004h 0004 4] Table Length : 00000050 >> [008h 0008 1] Revision : 02 >> [009h 0009 1] Checksum : F1 >> [00Ah 0010 6] Oem ID : "COREv4" >> [010h 0016 8] Oem Table ID : "COREBOOT" >> [018h 0024 4] Oem Revision : 0000002A >> [01Ch 0028 4] Asl Compiler ID : "CORE" >> [020h 0032 4] Asl Compiler Revision : 20200925 >> >> [024h 0036 1] Interface Type : 00 >> [025h 0037 3] Reserved : 000000 >> >> [028h 0040 12] Serial Port Register : [Generic Address >> Structure] >> [028h 0040 1] Space ID : 00 [SystemMemory] >> [029h 0041 1] Bit Width : 20 >> [02Ah 0042 1] Bit Offset : 00 >> [02Bh 0043 1] Encoded Access Width : 03 [DWord Access:32] >> [02Ch 0044 8] Address : 00000000FEDC9000 >> >> [034h 0052 1] Interrupt Type : 03 >> [035h 0053 1] PCAT-compatible IRQ : 04 >> [036h 0054 4] Interrupt : 00000004 >> [03Ah 0058 1] Baud Rate : 00 >> [03Bh 0059 1] Parity : 00 >> [03Ch 0060 1] Stop Bits : 00 >> [03Dh 0061 1] Flow Control : 00 >> [03Eh 0062 1] Terminal Type : 00 >> [04Ch 0076 1] Reserved : 00 >> [040h 0064 2] PCI Device ID : FFFF >> [042h 0066 2] PCI Vendor ID : FFFF >> [044h 0068 1] PCI Bus : 00 >> [045h 0069 1] PCI Device : 00 >> [046h 0070 1] PCI Function : 00 >> [047h 0071 4] PCI Flags : 00000000 >> [04Bh 0075 1] PCI Segment : 00 >> [04Ch 0076 4] Reserved : 00000000 >> >> And the DBG2 table: >> >> [000h 0000 4] Signature : "DBG2" [Debug Port >> table type 2] >> [004h 0004 4] Table Length : 0000005C >> [008h 0008 1] Revision : 00 >> [009h 0009 1] Checksum : 78 >> [00Ah 0010 6] Oem ID : "COREv4" >> [010h 0016 8] Oem Table ID : "COREBOOT" >> [018h 0024 4] Oem Revision : 00000000 >> [01Ch 0028 4] Asl Compiler ID : "CORE" >> [020h 0032 4] Asl Compiler Revision : 20200925 >> >> [024h 0036 4] Info Offset : 0000002C >> [028h 0040 4] Info Count : 00000001 >> >> [02Ch 0044 1] Revision : 00 >> [02Dh 0045 2] Length : 0030 >> [02Fh 0047 1] Register Count : 01 >> [030h 0048 2] Namepath Length : 000A >> [032h 0050 2] Namepath Offset : 0026 >> [034h 0052 2] OEM Data Length : 0000 [Optional field >> not present] >> [036h 0054 2] OEM Data Offset : 0000 [Optional field >> not present] >> [038h 0056 2] Port Type : 8000 >> [03Ah 0058 2] Port Subtype : 0000 >> [03Ch 0060 2] Reserved : 0000 >> [03Eh 0062 2] Base Address Offset : 0016 >> [040h 0064 2] Address Size Offset : 0022 >> >> [042h 0066 12] Base Address Register : [Generic Address >> Structure] >> [042h 0066 1] Space ID : 00 [SystemMemory] >> [043h 0067 1] Bit Width : 20 >> [044h 0068 1] Bit Offset : 00 >> [045h 0069 1] Encoded Access Width : 03 [DWord Access:32] >> [046h 0070 8] Address : 00000000FEDC9000 >> >> [04Eh 0078 4] Address Size : 000000F8 >> >> [052h 0082 10] Namepath : "\_SB.FUR0" >> >> >> Given all this I have yet to see windows dump anything to the serial >> console. The device just reboots after the BSOD message. Does anyone have >> any experience debugging Windows boot errors? Can you share any tips? :) >> >> Thanks, >> Raul >> _______________________________________________ >> coreboot mailing list -- coreboot@coreboot.org >> To unsubscribe send an email to coreboot-le...@coreboot.org >> >
_______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
