-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
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
The QEMU x86_64 Q35 fails verification for branch master as of commit
3be35976d6a640d0bc4fd40e232b6499b170431f
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
3be3597 google/snappy: enhance BigDaddy USB#2 2.0 strength
1b64ae1 soc/intel/cannonlake: Add Pch iSCLK
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
The QEMU x86_64 Q35 fails verification for branch master as of commit
6ee716e863117246d453e573d1a128da28b62cb7
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
6ee716e drivers/intel/fsp2_0: Remove fsp_find_smbios_memory_info() from FSP2.0
driver
93fde11
The QEMU x86_64 Q35 fails verification for branch master as of commit
2a9e8124e19a1a9143b9461d1f1f114e8e751c8a
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
2a9e812 mb/google/fizz: Set Pmax to 120 for all SKUs
dc4bc06 google/kahlee/grunt: Fix 2 device specific
The QEMU x86_64 Q35 fails verification for branch master as of commit
485c0ad0783aa168feab8944e498a393774512fd
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
485c0ad0 inteltool: Add Cougar- and Pantherpoint PCH PCI IDs for SPI
921fa84 inteltool: Fix displaying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/11/2016 01:58 AM, Paul Menzel wrote:
> Dear coreboot folks,
>
>
> Am Donnerstag, den 10.03.2016, 19:24 -0600 schrieb REACTS:
>> The QEMU x86_64 Q35 fails verification for branch master as of
>> commit
>>
>> The following tests failed:
>>
Dear coreboot folks,
Am Donnerstag, den 10.03.2016, 19:24 -0600 schrieb REACTS:
> The QEMU x86_64 Q35 fails verification for branch master as of
> commitÂ
>
> The following tests failed:
> BOOT_FAILURE
>
> Commits since last successful test:
> c7a1a3e northbridge/i945/gma: Re-enable NVRAM
The QEMU x86_64 Q35 fails verification for branch master as of commit
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness
a2176d8 soc/apollolake: Add memory and reserve MMIO resources
555d6c2 cbmem: Add
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
On Wed, May 13, 2015 at 9:02 AM, Raptor Engineering Automated Coreboot
Test Stand no-re...@raptorengineeringinc.com wrote:
The QEMU x86_64 Q35 fails verification as of commit
0a50d9b35334d03f13b38e21497ba0aae8b16712
The following tests failed:
ACPI_DSDT_ACCESS_FAILURE
On Wed, May 13, 2015 at 9:54 AM, Aaron Durbin adur...@google.com wrote:
On Wed, May 13, 2015 at 9:02 AM, Raptor Engineering Automated Coreboot
Test Stand no-re...@raptorengineeringinc.com wrote:
The QEMU x86_64 Q35 fails verification as of commit
0a50d9b35334d03f13b38e21497ba0aae8b16712
The
On 05/13/2015 12:31 PM, Timothy Pearson wrote:
On 05/13/2015 09:56 AM, Aaron Durbin via coreboot wrote:
On Wed, May 13, 2015 at 9:54 AM, Aaron Durbinadur...@google.com wrote:
All those are empty including dmesg. Was this a flaky test run?
Yes it was, and of course it happened overnight. I
On 05/13/2015 09:56 AM, Aaron Durbin via coreboot wrote:
On Wed, May 13, 2015 at 9:54 AM, Aaron Durbinadur...@google.com wrote:
On Wed, May 13, 2015 at 9:02 AM, Raptor Engineering Automated Coreboot
Test Standno-re...@raptorengineeringinc.com wrote:
The QEMU x86_64 Q35 fails verification as
The QEMU x86_64 Q35 fails verification as of commit
8ccdeaeb207031eea3881511acfaf3e949678f74
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
8ccdeae haswell: Link stage_cache_external_region into ramstage, too
634899c resource: Adjust memory resources high earlier
On 05/04/2015 10:08 PM, Raptor Engineering Automated Test Stand wrote:
The QEMU x86_64 Q35 fails verification as of commit
8ccdeaeb207031eea3881511acfaf3e949678f74
The following tests failed:
BOOT_FAILURE
Commits since last successful test:
8ccdeae haswell: Link stage_cache_external_region
The QEMU x86_64 Q35 fails verification as of commit
8ccdeaeb207031eea3881511acfaf3e949678f74
The following tests failed:
CBMEM_TIMESTAMP_ACCESS_FAILURE
CBMEM_OBJECT_TABLE_TRUNCATED
Commits since last successful test:
8ccdeae haswell: Link stage_cache_external_region into ramstage, too
634899c
The QEMU x86_64 Q35 fails verification as of commit
58649b058baecf24a07a2bc85fff68b339d67503
The following tests failed:
CBMEM_TIMESTAMP_ACCESS_FAILURE
CBMEM_OBJECT_TABLE_TRUNCATED
Commits since last successful test:
See attached boot log for details
This message was automatically generated
On 22.04.2015 06:01, Timothy Pearson wrote:
On 04/21/2015 05:25 PM, Carl-Daniel Hailfinger wrote:
Thank you for providing this service. It is very much appreciated.
I would like to make a suggestion, though: The mail size of failure
reports is increasing constantly as long as a boot problem
On 04/22/2015 01:28 AM, Gerd Hoffmann wrote:
Hi,
If the community would like me to stop sending these notifications I
will do so; I could also adjust the maximum frequency if desired.
How about sending out messages on status changes (i.e. edge not level
triggered). That should avoid
Hi,
If the community would like me to stop sending these notifications I
will do so; I could also adjust the maximum frequency if desired.
How about sending out messages on status changes (i.e. edge not level
triggered). That should avoid annoying repeated reports on the same
failure.
The QEMU x86_64 Q35 fails verification as of commit
6897f4e796c4645cec5d7a247dba78f002008080
The following tests failed:
CBMEM_TIMESTAMP_ACCESS_FAILURE
CBMEM_CONSOLE_CONTENT_TRUNCATED
Commits since last successful test:
6897f4e google/storm: indicate start of normal boot on LED ring
ace3e3f
The QEMU x86_64 Q35 fails verification as of commit
7ab46f8085146db57699001462da871f2e4d9965
Commits since last successful test:
7ab46f8 libpayload: add timer driver for cygnus
b048432 cygnus: add QSPI driver
82a7bc4 veyron: add new SDRAM configuration with ram-code 1101b
823f607 pistachio:
On 04/21/2015 11:44 AM, Timothy Pearson wrote:
On 04/21/2015 11:31 AM, Patrick Georgi via coreboot wrote:
2015-04-21 17:31 GMT+02:00 Gregg Levinegregg.drw...@gmail.com:
I suspect somehow it was supposed to be internal to hs outfit only.
Timothy provides boot testing of coreboot master with
On Di, 2015-04-21 at 02:24 -0500, Raptor Engineering Automated Test
Stand wrote:
The QEMU x86_64 Q35 fails verification as of commit
7ab46f8085146db57699001462da871f2e4d9965
Log says at the end RAPTOR ENGINEERING AUTOMATED TEST BOOT SUCCESS
Can you fix your test case and stop spamming the
Hello!
My thoughts exactly. Thank you sir.
I suspect somehow it was supposed to be internal to hs outfit only.
And something changed with regards to the logic behind how those
annoying e-mail messages being sent to us.
As for the test cases, they are extremely confusing to me. How many of
us
On 04/21/2015 05:25 PM, Carl-Daniel Hailfinger wrote:
Thank you for providing this service. It is very much appreciated.
I would like to make a suggestion, though: The mail size of failure
reports is increasing constantly as long as a boot problem remains
unfixed. Would it make sense to only
On 21.04.2015 19:14, Timothy Pearson wrote:
On 04/21/2015 11:44 AM, Timothy Pearson wrote:
On 04/21/2015 11:31 AM, Patrick Georgi via coreboot wrote:
2015-04-21 17:31 GMT+02:00 Gregg Levinegregg.drw...@gmail.com:
I suspect somehow it was supposed to be internal to hs outfit only.
Timothy
On 04/21/2015 11:31 AM, Patrick Georgi via coreboot wrote:
2015-04-21 17:31 GMT+02:00 Gregg Levinegregg.drw...@gmail.com:
I suspect somehow it was supposed to be internal to hs outfit only.
Timothy provides boot testing of coreboot master with QEmu and a AMD
board that he maintains as a
2015-04-21 17:31 GMT+02:00 Gregg Levine gregg.drw...@gmail.com:
I suspect somehow it was supposed to be internal to hs outfit only.
Timothy provides boot testing of coreboot master with QEmu and a AMD
board that he maintains as a service to the community.
And something changed with regards to
The QEMU x86_64 Q35 fails verification as of commit
1abb6002ddc84dd6f2dc01e76475480445fa4271
Commits since last successful test:
1abb600 broadcom/cygnus: Fix missing writel-write32 transformation
7ab46f8 libpayload: add timer driver for cygnus
b048432 cygnus: add QSPI driver
82a7bc4 veyron: add
The QEMU x86_64 Q35 fails verification as of commit
f21b657f27965beacd2a3134aafbf66d4db60930
Commits since last successful test:
f21b657 build system: improve portability by not relying on extraordinary dd
options
01368ed Kconfig: rename CONSOLE_SERIAL_UART to DRIVERS_UART
c047b10 purin: add
The QEMU x86_64 Q35 fails verification as of commit
4038a7f631dce05aa184184a225a49bc7723aed0
Commits since last successful test:
4038a7f gigabyte/ga-b75m-d3v: Add GIGABYTE GA-B75M-D3V mainboard
31ca97c southbridge/intel/bd82x6x: Add LPC id 0x1e49 for B75 chipset
bcff3bd
The QEMU x86_64 Q35 fails verification as of commit
f21b657f27965beacd2a3134aafbf66d4db60930
Commits since last successful test:
f21b657 build system: improve portability by not relying on extraordinary dd
options 01368ed Kconfig: rename CONSOLE_SERIAL_UART to DRIVERS_UART c047b10
purin: add
The QEMU x86_64 Q35 does not boot as of commit
c14e42623bede2480284cf500362d545f85f8f69
Commits since last successful test:
See attached boot log for details
This message was automatically generated from Raptor Engineering's QEMU x86_64
Q35 test stand
Raptor Engineering offers coreboot
36 matches
Mail list logo
