QEMU x86_64 Q35 Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

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
&lt;tpearson(a)raptorengineering.com&gt; regarding any issues stemming from this
notification

[Paul Menzel]

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]

-----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
[phone] (direct line)
[phone] (switchboard)
https://www.raptorengineering.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJaggq8AAoJEK+E3vEXDOFbl7wH/254xsMsPJgWf9NnUVvs4EJE
RzxUysC+L+qELdMzEPXyTslc47XWcrk1gQhQGtADzmc5GseVKBB1h8EXMtv0iJy6
i++1UeTtB5rnqqejuKdcPOpB20n4XFYw9HAe1HZQNgz8DzFy9iodmH8/FlyKWHTB
sU6pOgMQimiDLHWrFEIBZnM2AvrtyGmgcK1PHP7VE/peZvbthxDalzaNH8OAmsw9
5R1fti1hgjJ+4//SlXJCkM4WH5MGgpUFxRvXoOb00nnMlFgEGlXpCcrFTwqr1FVb
s+8HicmzaPpfo4HHIMlxWAWJ7DVAfKLtYHauZBvQNIlPXa9eG86RzWZVcI+5NVI=
=ujHl
-----END PGP SIGNATURE-----