On Wed, May 13, 2015 at 9:54 AM, Aaron Durbin <[email protected]> wrote: > On Wed, May 13, 2015 at 9:02 AM, Raptor Engineering Automated Coreboot > Test Stand <[email protected]> wrote: >> The QEMU x86_64 Q35 fails verification as of commit >> 0a50d9b35334d03f13b38e21497ba0aae8b16712 >> >> The following tests failed: >> ACPI_DSDT_ACCESS_FAILURE >> ACPI_SSDT_ACCESS_FAILURE >> DMIDECODE_ACCESS_FAILURE >> CBMEM_CONSOLE_ACCESS_FAILURE >> CBMEM_TIMESTAMP_ACCESS_FAILURE >> CBMEM_OBJECT_TABLE_ACCESS_FAILURE >>
All those are empty including dmesg. Was this a flaky test run? ======================================================= CBMEM timestamps ======================================================= ======================================================= CBMEM object table ======================================================= ======================================================= CBMEM log ======================================================= ======================================================= dmesg ======================================================= ======================================================= dmidecode ======================================================= ======================================================= ACPI DSDT ======================================================= ======================================================= ACPI SSDT ======================================================= ======================================================= RS232 log ======================================================= >> Commits since last successful test: >> 0a50d9b libpayload: x86: correct types used for IO > > I was curious about this... I'll take a look at the log. > >> >> See attached log for details >> >> This message was automatically generated from Raptor Engineering's QEMU >> x86_64 Q35 test stand >> Raptor Engineering offers coreboot consulting services! Please visit >> https://www.raptorengineeringinc.com for more information >> >> Please contact Timothy Pearson at Raptor Engineering >> <[email protected]> regarding any issues stemming from this >> notification >> >> -- >> coreboot mailing list: [email protected] >> http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
