coreboot July 2015

coreboot@coreboot.org

46 participants
98 discussions

[HEADS UP] Time stamps for AGESA boards now measured relatively to start and not ramstage
by Paul Menzel 11 Jul '15

11 Jul '15

Dear coreboot folks, thanks to the latest time stamp work and especially thanks to Aaron Durbin’s latest fix up commit bd1499d3 (timestamps: don't drop ramstage timestamps with EARLY_CBMEM_INIT) [1], the ramstage time stamps on AGESA boards – I only tested with the ASRock E350M1 – seem to be measured relative to the system start and not relatively to start of ramstage. Before time stamps were measured relatively to ramstage. $ more asrock/e350m1/4.0-10267-g72dd909/2015-07-10T00\:11\:47Z/coreboot_timestamps.txt 12 entries total: 10:start of ramstage 0 30:device enumeration 8 (8) 40:device configuration 94,880 (94,872) 50:device enable 98,697 (3,816) 60:device initialization 108,662 (9,965) 70:device setup done 122,998 (14,335) 75:cbmem post 123,369 (371) 80:write tables 123,374 (4) 90:load payload 128,020 (4,646) 15:starting LZMA decompress (ignore for x86) 128,275 (254) 16:finished LZMA decompress (ignore for x86) 146,142 (17,866) 99:selfboot jump 146,163 (21) With the latest changes we they are measured relatively to system start. $ more asrock/e350m1/4.0-10270-gbd1499d/2015-07-10T13\:23\:53Z/coreboot_timestamps.txt 12 entries total: 10:start of ramstage 385,974 30:device enumeration 385,982 (8) 40:device configuration 480,233 (94,250) 50:device enable 484,088 (3,855) 60:device initialization 494,049 (9,960) 70:device setup done 508,368 (14,318) 75:cbmem post 508,736 (368) 80:write tables 508,741 (4) 90:load payload 513,320 (4,579) 15:starting LZMA decompress (ignore for x86) 513,574 (253) 16:finished LZMA decompress (ignore for x86) 531,423 (17,848) 99:selfboot jump 531,445 (21) So 386 ms for romstage with AGESA is still an acceptable number. This confirms, which was already known. AGESA does a pretty good job. Time stamps from romstage are still not preserved though, which is a well known limitation though. Thanks, Paul [1] http://review.coreboot.org/10880

2 1

Problems about making disk image( qemu-img ... )
by Yu-Cheng Liu 11 Jul '15

11 Jul '15

Hello, I want to boot linux by QEMU with coreboot ,and I have some problems in making Linux image. I followed the steps on QEMU Build Tutorial form coreboot.org. (http://www.coreboot.org/QEMU_Build_Tutorial) As the Creating a hard disk image section points out: 1.qemu-img create -f raw disk.img 200M 2.mkfs.ext2 -F disk.img 3.mkdir /mnt/rootfs 4. mount -o loop disk.img /mnt/rootfs 5.mkdir /mnt/root/boot 6.cp vmlinux /mnt/rootfs/boot/vmlinuz 7.cp *initrd.img* /mnt/rootfs/boot/initrd 8.*cp -R /* /mnt/rootfs * I've done all the steps above, but the image doesn't work on QEMU. What does the 8th step mean? Does it act as *filesystem*? If so, could I only copy the directories and the root filesystem to make it work? I want to know how to build the image. P.S. my Linux distribution is ubuntu 14.04 Many thanks.

1 0

Unsupported mainboard
by Mohamed Zemmouri 11 Jul '15

11 Jul '15

Hi, I intend to purchase a new mainboard based on Intel's new z97 chipset but as I am a great fan of coreboot, I tried to look for the chipsets coreboot supports and nowhere could I find Intel's z97. Now I am kind of hopping you tell me I can't read or it got a different model name/number. If indeed it's unsupported, do you think it will stay that way or will it ever be ported to this chipest? Best regards, Iskander

1 0

Re: [coreboot] Cbfstool compilation error with gcc 5.1
by Stefan Reinauer 11 Jul '15

11 Jul '15

* Anatol Pomozov <anatol.pomozov(a)gmail.com> [150531 08:49]: > Hi > > I am trying to compile coreboot cbfstool on Arch where gcc 5.1 is used. And I > see following compilation error. I wonder if it is coreboot or gcc issue. > > ==> Starting build()... > make: Entering directory '/home/anatol/sources/archpackages/coreboot-utils-git/ > src/coreboot/util/cbfstool' > mkdir -p ./ > cc -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200809L -Iflashmap > -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param= > ssp-buffer-size=4 -g3 -std=c99 -Werror -Wall -Wextra -Wcast-qual > -Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes > -Wwrite-strings -c -o rmodule.o rmodule.c > rmodule.c: In function ‘rmodule_create’: > rmodule.c:286:29: error: ‘phdr’ may be used uninitialized in this function > [-Werror=maybe-uninitialized] > (phdr->p_vaddr + phdr->p_memsz))) { > ^ > rmodule.c:203:14: note: ‘phdr’ was declared here > Elf64_Phdr *phdr; > ^ > cc1: all warnings being treated as errors > Makefile:55: recipe for target 'rmodule.o' failed > make: *** [rmodule.o] Error 1 > make: Leaving directory '/home/anatol/sources/archpackages/coreboot-utils-git/ > src/coreboot/util/cbfstool' > ==> ERROR: A failure occurred in build(). Looks like a false positive. ctx-phdr only gets passed on if nelements is 1, in which we know that phdr was set. Stefan

2 1

ASUS KFSN4-DRE Automated Test Failure
by Raptor Engineering Automated Coreboot Test Stand 10 Jul '15

10 Jul '15

The ASUS KFSN4-DRE fails verification as of commit 72dd90946fd472d4aebcad2952b463b868e662f2 The following tests failed: CBMEM_TIMESTAMP_CONTENT_TRUNCATED Commits since last successful test: See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineeringinc.com> regarding any issues stemming from this notification

1 0

Re: [coreboot] Kernel couldn't find proper MAC address with coreboot (gigabyte ma785gmt-ud2h)
by Paul Menzel 09 Jul '15

09 Jul '15

Dear YongGon, welcome to coreboot and thank you for your message! Am Mittwoch, den 08.07.2015, 20:47 +0900 schrieb YongGon Kim: […] > I have uploaded detailed information using board_status.sh > Following is link for the information. > http://review.coreboot.org/gitweb?p=board-status.git;a=commit;h=dedf456d257… Your commit is marked as *dirty*, meaning that you have applied local changes. What are these? Additionally, could you please also upload the logs of a run with the current code in master? Thanks, Paul PS: Please just send plain text messages to mailing lists. Additionally, pasting logs in the Google Mail Web interface is not optimal as there is no way to turn off auto-wrapping the lines, which is not wanted for pastes.

2 1

RE： minnowboardmax coreboot intel uefi payload :Failedto find the required acpi table
by DM365 09 Jul '15

09 Jul '15

I try the latest coreboot package from edk2. The acpi table is ok,but there is new question."ERROR: C00000002:V03058002 I0 FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F 7A801AD8". The whole log is : POST: 0x4a POST: 0x4b POST: 0x4c POST: 0x4d POST: 0x4e POST: 0x4f POST: 0x39 POST: 0x80 POST: 0x70 POST: 0x71 POST: 0x72 POST: 0x24 POST: 0x25 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x55 POST: 0x73 APIC: 00 missing read_resources PCI: 00:00.0 missing set_resources POST: 0x74 POST: 0x75 POST: 0x75 POST: 0x93 POST: 0x9b POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 Warning: PCI Device 2 does not have an IRQ entry, skipping it POST: 0x75 POST: 0x75 POST: 0x76 POST: 0x77 find_current_mrc_cache_local: No valid fast boot cache found. POST: 0x79 POST: 0x9c POST: 0x9e POST: 0x9d POST: 0x7a POST: 0x7b POST: 0xf8 PROGRESS CODE: V03020003 I0 Loading PEIM at 0x0000080F4A0 EntryPoint=0x0000080F700 CbSupportPeim.efi PROGRESS CODE: V03020002 I0 0. 0000000000000000 - 0000000000000FFF [10] 1. 0000000000001000 - 000000000009FFFF [01] 2. 00000000000A0000 - 00000000000FFFFF [02] 3. 0000000000100000 - 000000007ACBCFFF [01] 4. 000000007ACBD000 - 000000007ADFFFFF [10] 5. 000000007AE00000 - 000000007FFFFFFF [02] 6. 00000000E0000000 - 00000000EFFFFFFF [02] 7. 00000000FEB00000 - 00000000FEC00FFF [02] 8. 00000000FED01000 - 00000000FED01FFF [02] 9. 00000000FED03000 - 00000000FED03FFF [02] 10. 00000000FED05000 - 00000000FED05FFF [02] 11. 00000000FED08000 - 00000000FED08FFF [02] 12. 00000000FED0C000 - 00000000FED0FFFF [02] 13. 00000000FED1C000 - 00000000FED1CFFF [02] 14. 00000000FEE00000 - 00000000FEE00FFF [02] 15. 00000000FEF00000 - 00000000FEFFFFFF [02] 16. 00000000FF800000 - 00000000FFFFFFFF [02] Low memory 0x7ACBD000, High Memory 0x0 LowMemorySize: 0x7ACBD000. HighMemorySize: 0x0. PeiMemBase: 0x76CB0000. PeiMemSize: 0x4000000. PeiInstallPeiMemory MemoryBegin 0x76CB0000, MemoryLength 0x4000000 Found one valid fv : 0x3E000000830000. Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 801C77 The 1th FV start address is 0x00000830000, size is 0x003E0000, handle is 0x830000 Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 Actual Coreboot header: 7ACBD000. Find CbMemTable Id 0x41435049, base 7ACD6000, size 0x24000 Find CbMemTable Id 0x534D4254, base 7ACC5000, size 0x800 Detected Acpi Table at 0x7ACD6000, length 0x24000 Detected Smbios Table at 0x7ACC5000, length 0x800 Create system table info guid hob Find CbMemTable Id 0x41435049, base 7ACD6000, size 0x1000 Find Rsdp at 7ACD6000 Find Rsdt 0x7ACD6030, Xsdt 0x7ACD60E0 PmCtrl Reg 0x404 PmTimer Reg 0x408 Reset Reg 0xCF9 Reset Value 0x6 PmEvt Reg 0x400 PmGpeEn Reg 0x424 Create acpi board info guid hob Found coreboot video frame buffer information physical_address: 0x0 x_resolution: 0x0 y_resolution: 0x0 bits_per_pixel: 0x0 bytes_per_line: 0x0 red_mask_size: 0x0 red_mask_pos: 0x0 green_mask_size: 0x0 green_mask_pos: 0x0 blue_mask_size: 0x0 blue_mask_pos: 0x0 reserved_mask_size: 0x0 reserved_mask_pos: 0x0 Create frame buffer info guid hob PROGRESS CODE: V03020003 I0 Temp Stack : BaseAddress=0x88000 Length=0x8000 Temp Heap : BaseAddress=0x80000 Length=0xD30 Total temporary memory: 65536 bytes. temporary memory stack ever used: 32768 bytes. temporary memory heap used: 3376 bytes. Old Stack size 32768, New stack size 131072 Stack Hob: BaseAddress=0x76CB0000 Length=0x20000 Heap Offset = 0x76C50000 Stack Offset = 0x76C40000 Loading PEIM at 0x0007ACA6000 EntryPoint=0x0007ACA6260 PeiCore.efi Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3 Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6 Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE Loading PEIM at 0x0007ACA2000 EntryPoint=0x0007ACA2260 DxeIpl.efi PROGRESS CODE: V03020002 I0 PROGRESS CODE: V03020003 I0 Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731 Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7 DXE IPL Entry Loading PEIM at 0x0007AC7F000 EntryPoint=0x0007AC7F2C0 DxeCore.efi PROGRESS CODE: V03021001 I0 Loading DXE CORE at 0x0007AC7F000 EntryPoint=0x0007AC7F2C0 Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6 PROGRESS CODE: V03040003 I0 Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A98F040 Loading driver at 0x0007A985000 EntryPoint=0x0007A9852C0 SecurityStubDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A98FF18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 7A987428 InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 7A987420 PROGRESS CODE: V03040003 I0 Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A98F380 Loading driver at 0x0007A970000 EntryPoint=0x0007A9702C0 CpuDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A98FB58 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 7A979480 Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Flushing GCD Detect CPU count: 2 Does not find any HOB stored CPU BIST information! InstallProtocolInterface: 3FDDA605-A76E-4F46-AD29-12F4531B3D08 7A9793A8 PROGRESS CODE: V03040003 I0 Loading driver C8339973-A563-4561-B858-D8476F9DEFC4 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97C040 Loading driver at 0x0007A97A000 EntryPoint=0x0007A97A2C0 Metronome.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A97CF18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 7A97BA10 PROGRESS CODE: V03040003 I0 Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97C380 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\MdeModulePkg\Core\RuntimeDxe\RuntimeDxe\DEBUG\RuntimeDxe.pdb !!!!!!!! Loading driver at 0x0007AB83000 EntryPoint=0x0007AB832C0 RuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A97CDD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 7AB85100 PROGRESS CODE: V03040003 I0 Loading driver 4B28E4C7-FF36-4E10-93CF-A82159E777C5 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97E0C0 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\MdeModulePkg\Universal\ResetSystemRuntimeDxe\ResetSystemRuntimeDxe\DEBUG\ResetSystemRuntimeDxe.pdb !!!!!!!! Loading driver at 0x0007AB80000 EntryPoint=0x0007AB802C0 ResetSystemRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A97EED8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0 PROGRESS CODE: V03040003 I0 Loading driver 02B01AD5-7E59-43E8-A6D8-238180613A5A InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97E540 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\MdeModulePkg\Universal\Variable\EmuRuntimeDxe\EmuVariableRuntimeDxe\DEBUG\EmuVariableRuntimeDxe.pdb !!!!!!!! Loading driver at 0x0007AB7B000 EntryPoint=0x0007AB7B2C0 EmuVariableRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A97E798 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0 InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0 PROGRESS CODE: V03040003 I0 Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97D2C0 Loading driver at 0x0007A96C000 EntryPoint=0x0007A96C2C0 CpuIo2Dxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A97DA58 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F 7A96DC30 PROGRESS CODE: V03040003 I0 Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A97D740 Loading driver at 0x0007A954000 EntryPoint=0x0007A9542C0 DevicePathDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96FF18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 7A95B6E0 InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C 7A95B720 InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E 7A95B730 PROGRESS CODE: V03040003 I0 Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96F880 Loading driver at 0x0007A968000 EntryPoint=0x0007A9682C0 NullMemoryTestDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96F098 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF 7A969900 PROGRESS CODE: V03040003 I0 Loading driver 79CA4208-BBA1-4A9A-8456-E1E66A81484E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96E040 Loading driver at 0x0007A966000 EntryPoint=0x0007A9662C0 Legacy8259.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96E2D8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1 7A9677E0 PROGRESS CODE: V03040003 I0 Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96EA00 Loading driver at 0x0007A91C000 EntryPoint=0x0007A91C2C0 HiiDatabase.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96ED18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 7A935D68 InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A 7A935DB0 InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 7A935DD8 InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F 7A935E30 InstallProtocolInterface: 0A8BADD5-03B8-4D19-B128-7B8F0EDAA596 7A935E60 InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 7A935D88 PROGRESS CODE: V03040003 I0 Loading driver C68DAA4E-7AB5-41E8-A91D-5954421053F3 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96B200 Loading driver at 0x0007A960000 EntryPoint=0x0007A9602C0 CbSupportDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96B858 PROGRESS CODE: V03040002 I0 Install Acpi Table at 0x7ACD6000, length 0x24000 Install Smbios Table at 0x7ACC5000, length 0x800 PmCtrlReg at 0x404 PROGRESS CODE: V03040003 I0 Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96A0C0 Loading driver at 0x0007A94C000 EntryPoint=0x0007A94C2C0 SmbiosDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96AED8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 7A94F710 PROGRESS CODE: V03040003 I0 Loading driver D3987D4B-971A-435F-8CAF-4967EB627241 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A96A540 Loading driver at 0x0007A952000 EntryPoint=0x0007A9522C0 SerialDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A96AB58 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD 7A953D50 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A953D00 PROGRESS CODE: V03040003 I0 Loading driver FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A9659C0 Loading driver at 0x0007A8C2000 EntryPoint=0x0007A8C22C0 BdsDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A965C18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D 7A8E8F08 PROGRESS CODE: V03040003 I0 Loading driver F2765DEC-6B41-11D5-8E71-00902707B35E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A9642C0 Loading driver at 0x0007A94A000 EntryPoint=0x0007A94A2C0 Timer.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A964DD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 7A94B730 PROGRESS CODE: V03040003 I0 Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A965500 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\MdeModulePkg\Universal\CapsuleRuntimeDxe\CapsuleRuntimeDxe\DEBUG\CapsuleRuntimeDxe.pdb !!!!!!!! Loading driver at 0x0007AB79000 EntryPoint=0x0007AB792C0 CapsuleRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A964518 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0 PROGRESS CODE: V03040003 I0 Loading driver AD608272-D07F-4964-801E-7BD3B7888652 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A963C80 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\MdeModulePkg\Universal\MonotonicCounterRuntimeDxe\MonotonicCounterRuntimeDxe\DEBUG\MonotonicCounterRuntimeDxe.pdbLoading driver at 0x0007AB77000 EntryPoint=0x0007AB772C0 MonotonicCounterRuntimeDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A963B98 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0 PROGRESS CODE: V03040003 I0 Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A951040 !!!!!!!! InsertImageRecord - Section Alignment(0x20) is not 4K !!!!!!!! !!!!!!!! Image - d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\PcAtChipsetPkg\PcatRealTimeClockRuntimeDxe\PcatRealTimeClockRuntimeDxe\DEBUG\PcRtc.pdb !!!!!!!! Loading driver at 0x0007AB73000 EntryPoint=0x0007AB732C0 PcRtc.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A9512D8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0 PROGRESS CODE: V03040003 I0 Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A951600 Loading driver at 0x0007A8A9000 EntryPoint=0x0007A8A92C0 SetupBrowser.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A951858 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 7A8C02E0 InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B 7A8C0310 InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 7A8C02F0 PROGRESS CODE: V03040003 I0 Loading driver 0F7EC77A-1EE1-400F-A99D-7CBD1FEB181E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A950880 Loading driver at 0x0007A93C000 EntryPoint=0x0007A93C2C0 PcatPciRootBridge.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A9503D8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A949FD8 InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D 7A949030 InstallProtocolInterface: AF6AC311-84C3-11D2-8E3C-00A0C969723B 7A949C68 PROGRESS CODE: V03040003 I0 Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FC640 Loading driver at 0x0007A8F8000 EntryPoint=0x0007A8F82C0 WatchdogTimer.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8FCBD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D 7A8F95F0 PROGRESS CODE: V03040003 I0 Loading driver E660EA85-058E-4B55-A54B-F02F83A24707 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FC840 Loading driver at 0x0007A881000 EntryPoint=0x0007A881314 DisplayEngine.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8FCAD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E 7A892650 PROGRESS CODE: V03040003 I0 Loading driver 35C0C168-2607-4E51-BB53-448E3ED1A87F InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F4E00 Loading driver at 0x0007A899000 EntryPoint=0x0007A8992C0 PciBusNoEnumerationDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A909AD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A89FFD0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A8A0008 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8A0020 PROGRESS CODE: V03040003 I0 Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F5E00 Loading driver at 0x0007A8A5000 EntryPoint=0x0007A8A52C0 ConPlatformDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A90BA18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A8A7E20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A8A7E80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8A7E98 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A8A7E50 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A8A7E80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8A7E98 PROGRESS CODE: V03040003 I0 Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FAE00 Loading driver at 0x0007A871000 EntryPoint=0x0007A8712C0 ConSplitterDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A90DC18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A877368 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A877808 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A877820 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A8773F8 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A877838 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A877850 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A877428 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A877868 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A877880 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A877398 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A877898 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8778B0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A8773C8 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A8778C8 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8778E0 InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 7A877470 InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 7A8774A0 InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D 7A8774F8 InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 7A877550 InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A877600 InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A877710 PROGRESS CODE: V03040003 I0 Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FA8C0 Loading driver at 0x0007A86B000 EntryPoint=0x0007A86B2C0 GraphicsConsoleDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A918BD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A870320 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A870358 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A870370 PROGRESS CODE: V03040003 I0 Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FBC00 Loading driver at 0x0007A863000 EntryPoint=0x0007A8632C0 TerminalDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A91BA18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A869BC8 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A869D68 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A869D80 PROGRESS CODE: V03040003 I0 Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8FBE00 Loading driver at 0x0007A87C000 EntryPoint=0x0007A87C2C0 DiskIoDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A938B58 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A8808D0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A880988 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8809A0 PROGRESS CODE: V03040003 I0 Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F7380 Loading driver at 0x0007A857000 EntryPoint=0x0007A8572C0 PartitionDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F7A98 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A85C0B0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A85C100 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A85C118 PROGRESS CODE: V03040003 I0 Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F7580 Loading driver at 0x0007A8F0000 EntryPoint=0x0007A8F02C0 EnglishDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A93BAD8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D 7A8F1800 InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 7A8F1838 PROGRESS CODE: V03040003 I0 Loading driver 8F4CD826-A5A0-4E93-9522-CFB0AB72926C InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F7780 Loading driver at 0x0007A879000 EntryPoint=0x0007A8792C0 SataController.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F7A18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A87B790 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A87B7C0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A87B7D8 PROGRESS CODE: V03040003 I0 Loading driver 19DF145A-B1D4-453F-8507-38816676D7F6 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F6040 Loading driver at 0x0007A849000 EntryPoint=0x0007A8492C0 AtaBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A945A18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A84EAA0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A84ECF0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A84ED08 PROGRESS CODE: V03040003 I0 Loading driver 5E523CB4-D397-4986-87BD-A6DD8B22F455 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F6240 Loading driver at 0x0007A833000 EntryPoint=0x0007A8332C0 AtaAtapiPassThruDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A946C18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A83C840 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A83CA80 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A83CA98 PROGRESS CODE: V03040003 I0 Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F6CC0 Loading driver at 0x0007A85F000 EntryPoint=0x0007A85F2C0 ScsiBus.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F6E98 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A862570 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A8625A0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A8625B8 PROGRESS CODE: V03040003 I0 Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F6440 Loading driver at 0x0007A842000 EntryPoint=0x0007A8422C0 ScsiDisk.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F6C18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A847D50 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A847DB0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A847DC8 PROGRESS CODE: V03040003 I0 Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F68C0 Loading driver at 0x0007A82C000 EntryPoint=0x0007A82C56C InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F6758 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A82C360 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A82C438 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A82C450 PROGRESS CODE: V03040003 I0 Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F3BC0 Loading driver at 0x0007A81C000 EntryPoint=0x0007A81C2C0 UhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F3B18 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A822950 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A822980 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A822998 PROGRESS CODE: V03040003 I0 Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F3400 Loading driver at 0x0007A80A000 EntryPoint=0x0007A80A2C0 EhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F35D8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A811F20 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A811F50 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A811F68 PROGRESS CODE: V03040003 I0 Loading driver B7F50E91-A759-412C-ADE4-DCD03E7F7C28 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F2A80 Loading driver at 0x0007A7E6000 EntryPoint=0x0007A7E62C0 XhciDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F21D8 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A7F1758 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A7F1800 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A7F1818 PROGRESS CODE: V03040003 I0 Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8F2480 Loading driver at 0x0007A7DC000 EntryPoint=0x0007A7DC2C0 UsbBusDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8F2658 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A7E4AA8 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A7E4AD8 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A7E4AF0 PROGRESS CODE: V03040003 I0 Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8EFB40 Loading driver at 0x0007A825000 EntryPoint=0x0007A8252C0 UsbKbDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8EF298 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A82AB80 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A82ABB0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A82ABC8 PROGRESS CODE: V03040003 I0 Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8EF540 Loading driver at 0x0007A816000 EntryPoint=0x0007A8162C0 UsbMassStorageDxe.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8EF718 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A81B828 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A81B858 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A81B870 PROGRESS CODE: V03040003 I0 Loading driver 0B04B2ED-861C-42CD-A22F-C3AAFACCB896 InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A8A2B40 Loading driver at 0x0007A805000 EntryPoint=0x0007A8052C0 FbGop.efi InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A8A2298 PROGRESS CODE: V03040002 I0 InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A808BB0 InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A808BE0 InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A808BF8 PROGRESS CODE: V03040003 I0 PROGRESS CODE: V03041001 I0 [BdsDxe] Locate Variable Lock protocol - Not Found PROGRESS CODE: V03051005 I0 Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8E7F08 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A8E7EB8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8E7F20 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A8E7ED0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8E7F38 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A8E7FA8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8E8EF0 InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A8E8128 PlatformBdsPolicyBehavior InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A850A98 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A850468 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A850E18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A850128 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A854FD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A854568 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A850DD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A851028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898718 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A851BE8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A850BD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A851368 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8988D8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A8516A8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A851FD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A824028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A854F98 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A824BE8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898918 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A824368 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8981D8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A8246A8 PciExp - 1 (B-0, D-1C, F-0) InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A824FD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A815028 PciExp - 1 (B-0, D-1C, F-2) InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A850B58 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A815BE8 PciExp - 1 (B-2, D-0, F-0) InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898BD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A815368 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898C18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A8156A8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A815FD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A814028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898E18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A814BE8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898CD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A814368 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898E58 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A8146A8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A814FD8 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A813028 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A898F18 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A813BE8 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A8A1698 InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A813368 PlatformBdsGetDriverOption Boot Mode:0 Found PCI VGA device GOP START PROGRESS CODE: V01030004 I0 InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A801998 FbGopCheckForVbe - Success InstallProtocolInterface: 9042A9DE-23DC-4A38-96FB-7ADED080516A 7A801C30 InstallProtocolInterface: 1C0C34F6-D380-41FA-A049-8AD06C1A66AA 7A801C50 InstallProtocolInterface: BD8C1056-9F36-44EC-92A8-A6337F817986 7A801C60 ERROR: C00000002:V03058002 I0 FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F 7A801AD8 Found LPC Bridge device BdsPlatform.c+140: COM1 DevPath: VenHw(BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD)/Uart(115200,8,N,1)/VenPcAnsi() !!!! X64 Exception Type - 0000000000000000 CPU Apic ID - 00000000 !!!! RIP - 000000007A8061A7, CS - 0000000000000028, RFLAGS - 0000000000010246 RAX - 0000000000000000, RCX - 000000007A801ED8, RDX - 0000000000000000 RBX - 000000007A801818, RSP - 000000007AC7EA40, RBP - 000000007A801C18 RSI - 000000007AC7EAC0, RDI - 0000000000000000 R8 - 0000000000000000, R9 - 000000007A80185F, R10 - 0000000000000019 R11 - FFFFFFFF857FE128, R12 - 0000000000000000, R13 - 0000000000000001 R14 - 000000007AC7EAF4, R15 - 000000007A801798 DS - 0000000000000008, ES - 0000000000000008, FS - 0000000000000008 GS - 0000000000000008, SS - 0000000000000008 CR0 - 0000000080000011, CR2 - 0000000000000000, CR3 - 000000007AC1D000 CR4 - 0000000000000628, CR8 - 0000000000000000 DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000 DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400 GDTR - 000000007AC0AA98 000000000000003F, LDTR - 0000000000000000 IDTR - 000000007A990018 0000000000000FFF, TR - 0000000000000000 FXSAVE_STATE - 000000007AC7E6A0 !!!! Find PE image d:\share\e3800\edk2\Build\CorebootPayloadPkgX64\DEBUG_VS2008x86\X64\CorebootPayloadPkg\FbGop\FbGop\DEBUG\FbGop.pdb (ImageBase=000000007A805000, EntryPoint=000000007A8052C0) !!!! My understanding is that your coreboot does not have ACPI table, you possible 1) add ACPI support in coreboot, or 2) modify UEFI payload to remove the assert if ACPI table not exist, or 3) trying the latest coreboot package from edk2 source tree. On Tue, Jul 7, 2015 at 2:58 AM, DM365 <1395158558(a)qq.com> wrote: Hello! I tested intel uefi payload instead of seabios in coreboot minnowboard max . It failed with "Failed to find the required acpi table ". If I use seabios payload ,the bios runs ok! I followed "http://www.elinux.org/Minnowboard:MinnowMaxCoreboot" to build coreboot. I used "https://firmware.intel.com/develop/" 2014-WW26-UEFI.coreboot.Payload.zip to builed uefi in coreboot. The whole terminal log is : POST: 0x4a POST: 0x4b POST: 0x4c POST: 0x4d POST: 0x4e POST: 0x4f POST: 0x39 POST: 0x80 POST: 0x70 POST: 0x71 POST: 0x72 POST: 0x24 POST: 0x25 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x24 POST: 0x25 POST: 0x55 POST: 0x55 POST: 0x73 APIC: 00 missing read_resources PCI: 00:00.0 missing set_resources POST: 0x74 POST: 0x75 POST: 0x75 POST: 0x93 POST: 0x9b POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 POST: 0x75 Warning: PCI Device 2 does not have an IRQ entry, skipping it POST: 0x75 POST: 0x75 POST: 0x76 POST: 0x77 find_current_mrc_cache_local: No valid fast boot cache found. POST: 0x79 POST: 0x9c POST: 0x9e POST: 0x9d POST: 0x7a POST: 0x7b POST: 0xf8 PROGRESS CODE: V03020003 I0 Loading PEIM at 0x0000080EC20 EntryPoint=0x0000080EE80 CbSupportPeim.efi PROGRESS CODE: V03020002 I0 0. 0000000000000000 - 0000000000000FFF [10] 1. 0000000000001000 - 000000000009FFFF [01] 2. 00000000000A0000 - 00000000000FFFFF [02] 3. 0000000000100000 - 000000007ACBCFFF [01] 4. 000000007ACBD000 - 000000007ADFFFFF [10] 5. 000000007AE00000 - 000000007FFFFFFF [02] 6. 00000000E0000000 - 00000000EFFFFFFF [02] 7. 00000000FEB00000 - 00000000FEC00FFF [02] 8. 00000000FED01000 - 00000000FED01FFF [02] 9. 00000000FED03000 - 00000000FED03FFF [02] 10. 00000000FED05000 - 00000000FED05FFF [02] 11. 00000000FED08000 - 00000000FED08FFF [02] 12. 00000000FED0C000 - 00000000FED0FFFF [02] 13. 00000000FED1C000 - 00000000FED1CFFF [02] 14. 00000000FEE00000 - 00000000FEE00FFF [02] 15. 00000000FEF00000 - 00000000FEFFFFFF [02] 16. 00000000FF800000 - 00000000FFFFFFFF [02] Low memory 0x7ACBD000, High Memory 0x0 LowMemorySize: 0x7ACBD000. HighMemorySize: 0x0. PeiMemBase: 0x76CB0000. PeiMemSize: 0x4000000. PeiInstallPeiMemory MemoryBegin 0x76CB0000, MemoryLength 0x4000000 Found one valid fv : 0x820000. Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39 Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 801BC0 The 1th FV start address is 0x00000820000, size is 0x003E0000, handle is 0x820000 Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410 Actual Coreboot header: 0x7ACBD000. Failed to find the required acpi table PEI_ASSERT!: d:\myworkspace\CorebootModulePkg\CbSupportPei\CbSupportPei.c (338): ((BOOLEAN)(0==1)) -- coreboot mailing list: coreboot(a)coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot

2 1

Req: FOSS-restricting firmware hints
by Nico Rikken 08 Jul '15

08 Jul '15

Dear ARM-netbook and Coreboot readers, In FSFE context we're looking for examples regarding firmware restrictions on modern computer hardware. This so that we can shed light on the difficult situation you are all too familiar with. Examples are: - Trusted Platform Module (TPM) chips - Secure Boot - Intel - Management Engine - Advanced Management Technology - Boot Guard It will be great if you can add some from the top of your head, ideally including some references. I'll be doing my own research as well, but your hints will greatly help this process. Kind regards, Nico Rikken

3 2

Re: [coreboot] Hudson-D4 (A88X): IRQ routing of XHCI seems incomplete?
by Rudolf Marek 08 Jul '15

08 Jul '15

Hi > > In "AMD Bolton FCH Register Reference Guide" (51192), page 2-154, this > register "Interrupt Line – RW – 32 bits - [PCI_Reg:3Ch]" is 0x12/0x11 > while having booted the vendor binary and 0xff/0xff when having booted > coreboot. Well this register is used only by OS when MPTABLE/ACPI PCI routing fails. The register is only a storage, it does not drive any logic.Btw 12/11 is wrong as PCI specs says it can be 0-15 range. So the issues must be something else. Thanks Rudolf

1 0

Re: [coreboot] Hudson-D4 (A88X): IRQ routing of XHCI seems incomplete?
by Idwer Vollering 08 Jul '15

08 Jul '15

Subject should read "Re: Hudson-D4 (A85X): IRQ routing of XHCI seems incomplete?" 2015-07-08 15:59 GMT+02:00 Idwer Vollering <vidwer(a)gmail.com>: > Board: asus/f2a85-m > > In "AMD Bolton FCH Register Reference Guide" (51192), page 2-154, this > register "Interrupt Line – RW – 32 bits - [PCI_Reg:3Ch]" is 0x12/0x11 > while having booted the vendor binary and 0xff/0xff when having booted > coreboot. This is about hudson, not bolton.. Unfortunately its RRG/RPR/databook is not public :( http://support.amd.com/en-us/search/tech-docs#k=a85x > > Could the erratic value cause SeaBIOS boot issues? See > http://www.coreboot.org/pipermail/seabios/2014-June/008148.html and > http://www.coreboot.org/pipermail/seabios/2014-June/008150.html > > lspci -s 10.{0,1} -nnvvvxx output follows. > > vendor binary: > 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH > USB XHCI Controller [1022:7812] (rev 03) (prog-if 30 [XHCI]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8527] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 18 > Region 0: Memory at fef4a000 (64-bit, non-prefetchable) > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [70] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: 00000000fee13000 Data: 0031 > Capabilities: [90] MSI-X: Enable- Count=8 Masked- > Vector table: BAR=0 offset=00001000 > PBA: BAR=0 offset=00001080 > Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0 > ExtTag- RBE+ > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- > DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, > OBFF Not Supported > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, > OBFF Disabled > 00: 22 10 12 78 06 04 10 00 03 30 03 0c 10 00 80 00 > 10: 04 a0 f4 fe 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 27 85 > 30: 00 00 00 00 50 00 00 00 00 00 00 00 12 01 00 00 > 40: 00 00 00 00 00 00 00 00 88 00 00 00 08 77 76 76 > 50: 01 70 03 c8 08 00 00 00 00 00 00 00 00 00 00 00 > 60: 30 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 05 90 87 00 00 30 e1 fe 00 00 00 00 31 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 11 a0 07 00 00 10 00 00 80 10 00 00 00 00 00 00 > a0: 10 00 92 00 c0 8f 00 00 00 28 10 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 10 08 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: fc 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 08 17 80 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH > USB XHCI Controller [1022:7812] (rev 03) (prog-if 30 [XHCI]) > Subsystem: ASUSTeK Computer Inc. Device [1043:8527] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin B routed to IRQ 17 > Region 0: Memory at fef48000 (64-bit, non-prefetchable) > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [70] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: 00000000fee10000 Data: 0034 > Capabilities: [90] MSI-X: Enable- Count=8 Masked- > Vector table: BAR=0 offset=00001000 > PBA: BAR=0 offset=00001080 > Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0 > ExtTag- RBE+ > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- > DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, > OBFF Not Supported > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, > OBFF Disabled > 00: 22 10 12 78 06 04 10 00 03 30 03 0c 10 00 00 00 > 10: 04 80 f4 fe 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 43 10 27 85 > 30: 00 00 00 00 50 00 00 00 00 00 00 00 11 02 00 00 > 40: 00 00 00 00 00 00 00 00 04 00 00 00 11 01 66 00 > 50: 01 70 03 c8 08 00 00 00 00 00 00 00 00 00 00 00 > 60: 30 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 05 90 87 00 00 00 e1 fe 00 00 00 00 34 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 11 a0 07 00 00 10 00 00 80 10 00 00 00 00 00 00 > a0: 10 00 92 00 c0 8f 00 00 00 28 10 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 10 08 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: fc 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 08 17 80 00 00 00 00 00 00 00 00 00 00 00 00 00 > > coreboot: > 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH > USB XHCI Controller [1022:7812] (rev 03) (prog-if 30 [XHCI]) > Subsystem: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI > Controller [1022:7812] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 255 > Region 0: Memory at f0148000 (64-bit, non-prefetchable) > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [70] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: 00000000fee10000 Data: 0033 > Capabilities: [90] MSI-X: Enable- Count=8 Masked- > Vector table: BAR=0 offset=00001000 > PBA: BAR=0 offset=00001080 > Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0 > ExtTag- RBE+ > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- > DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, > OBFF Not Supported > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, > OBFF Disabled > 00: 22 10 12 78 06 04 10 00 03 30 03 0c 10 00 80 00 > 10: 04 80 14 f0 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 12 78 > 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 01 00 00 > 40: 00 00 00 00 00 00 00 00 04 00 00 00 11 01 ff 00 > 50: 01 70 03 c8 08 00 00 00 00 00 00 00 00 00 00 00 > 60: 30 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 05 90 87 00 00 00 e1 fe 00 00 00 00 33 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 11 a0 07 00 00 10 00 00 80 10 00 00 00 00 00 00 > a0: 10 00 92 00 c0 8f 00 00 00 28 10 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 10 08 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: fc 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 08 17 80 00 00 00 00 00 00 00 00 00 00 00 00 00 > > 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH > USB XHCI Controller [1022:7812] (rev 03) (prog-if 30 [XHCI]) > Subsystem: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI > Controller [1022:7812] > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0, Cache Line Size: 64 bytes > Interrupt: pin B routed to IRQ 255 > Region 0: Memory at f014a000 (64-bit, non-prefetchable) > Capabilities: [50] Power Management version 3 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [70] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Address: 00000000fee11000 Data: 0032 > Capabilities: [90] MSI-X: Enable- Count=8 Masked- > Vector table: BAR=0 offset=00001000 > PBA: BAR=0 offset=00001080 > Capabilities: [a0] Express (v2) Root Complex Integrated Endpoint, MSI 00 > DevCap: MaxPayload 128 bytes, PhantFunc 0 > ExtTag- RBE+ > DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- > RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ > MaxPayload 128 bytes, MaxReadReq 512 bytes > DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- > DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, > OBFF Not Supported > DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, > OBFF Disabled > 00: 22 10 12 78 06 04 10 00 03 30 03 0c 10 00 00 00 > 10: 04 a0 14 f0 00 00 00 00 00 00 00 00 00 00 00 00 > 20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 12 78 > 30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 02 00 00 > 40: 00 00 00 00 00 00 00 00 04 00 00 00 11 01 ff 00 > 50: 01 70 03 c8 08 00 00 00 00 00 00 00 00 00 00 00 > 60: 30 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 70: 05 90 87 00 00 10 e1 fe 00 00 00 00 32 00 00 00 > 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 90: 11 a0 07 00 00 10 00 00 80 10 00 00 00 00 00 00 > a0: 10 00 92 00 c0 8f 00 00 00 28 10 00 00 00 00 00 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 10 08 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: fc 1f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 08 17 80 00 00 00 00 00 00 00 00 00 00 00 00 00

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot July 2015