The QEMU x86_64 Q35 fails verification for branch master as of commit 1b64ae1119fc7891b043d5d29bf93859ef9dbfa1
The following tests failed: BOOT_FAILURE
Commits since last successful test: 1b64ae1 soc/intel/cannonlake: Add Pch iSCLK programming 106a9fe mb/google/fizz: Set SATA GPIOs in bootblock f0b3a5f mb/google/poppy/variants/nautilus: set oem_id, oem_table_id fields of acpi_header_t 3dd7d84 mainboard/google/meowth: Enable ECT again b924f40 mb/google/poppy/variants/nami: set oem_id, oem_table_id fields of acpi_header_t
<45 commits skipped>
75f5d99 mb/asus/m2v-mx_se: Add `cmos.default` 25874b8 mb/google/eve: Enable HotPlug on PCIe root port for WiFi 74ea48e soc/intel/skylake: Add devicetree variable for PCIe HotPlug f5e3775 google/kahlee: Initialize non-early i2c buses in mainboard_init e0ea982 soc/amd/stoneyridge: Add API to initialize non-early_init i2c buses
See attached log for details
This message was automatically generated from Raptor Engineering's QEMU x86_64 Q35 test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html
Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information
Please contact Timothy Pearson at Raptor Engineering tpearson@raptorengineering.com regarding any issues stemming from this notification
Dear Timothy,
Am Samstag, den 10.02.2018, 18:32 -0600 schrieb REACTS:
The QEMU x86_64 Q35 fails verification for branch master as of commit 1b64ae1119fc7891b043d5d29bf93859ef9dbfa1
The following tests failed: BOOT_FAILURE
Commits since last successful test: 1b64ae1 soc/intel/cannonlake: Add Pch iSCLK programming 106a9fe mb/google/fizz: Set SATA GPIOs in bootblock f0b3a5f mb/google/poppy/variants/nautilus: set oem_id, oem_table_id fields of acpi_header_t 3dd7d84 mainboard/google/meowth: Enable ECT again b924f40 mb/google/poppy/variants/nami: set oem_id, oem_table_id fields of acpi_header_t
<45 commits skipped>
75f5d99 mb/asus/m2v-mx_se: Add `cmos.default` 25874b8 mb/google/eve: Enable HotPlug on PCIe root port for WiFi 74ea48e soc/intel/skylake: Add devicetree variable for PCIe HotPlug f5e3775 google/kahlee: Initialize non-early i2c buses in mainboard_init e0ea982 soc/amd/stoneyridge: Add API to initialize non-early_init i2c buses
See attached log for details
Unfortunately, the log only contains the successful boot log of the fallback image. My test showed, that the board builds and runs fine up to the SeaBIOS payload.
I believe there is a problem with the test stand, so could you please take it offline for now until you can look into it and provide the needed log files?
Kind regards,
Paul
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Disabled for now. There might be a disk space issue affecting this particular emulation target, looking into it.
Sorry for the noise!
On 02/12/2018 02:55 AM, Paul Menzel wrote:
Dear Timothy,
Am Samstag, den 10.02.2018, 18:32 -0600 schrieb REACTS:
The QEMU x86_64 Q35 fails verification for branch master as of commit 1b64ae1119fc7891b043d5d29bf93859ef9dbfa1
The following tests failed: BOOT_FAILURE
Commits since last successful test: 1b64ae1 soc/intel/cannonlake: Add Pch iSCLK programming 106a9fe mb/google/fizz: Set SATA GPIOs in bootblock f0b3a5f mb/google/poppy/variants/nautilus: set oem_id, oem_table_id fields of acpi_header_t 3dd7d84 mainboard/google/meowth: Enable ECT again b924f40 mb/google/poppy/variants/nami: set oem_id, oem_table_id fields of acpi_header_t
<45 commits skipped>
75f5d99 mb/asus/m2v-mx_se: Add `cmos.default` 25874b8 mb/google/eve: Enable HotPlug on PCIe root port for WiFi 74ea48e soc/intel/skylake: Add devicetree variable for PCIe HotPlug f5e3775 google/kahlee: Initialize non-early i2c buses in mainboard_init e0ea982 soc/amd/stoneyridge: Add API to initialize non-early_init i2c buses
See attached log for details
Unfortunately, the log only contains the successful boot log of the fallback image. My test showed, that the board builds and runs fine up to the SeaBIOS payload.
I believe there is a problem with the test stand, so could you please take it offline for now until you can look into it and provide the needed log files?
Kind regards,
Paul
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com
-
Paul Menzel -
Raptor Engineering Automated Coreboot Test Stand -
Timothy Pearson