ASUS KGPE-D16 Automated Test Failure [master]

[Raptor Engineering Automated Coreboot Test Stand]

The ASUS KGPE-D16 fails verification for branch master as of commit dc97b1ce2f4e671e73e2a3fb65e49a881a694590

The following tests failed:
BOOT_FAILURE

Commits since last successful test:
dc97b1c soc/intel/apollolake: Fix bitshift issue in bootblock
b921725 nb/intel/x4x: Fix CAS latency detection
47995fb arch/riscv: Remove enter_supervisor
b8e67ac arch/riscv: Change all eret instructions to .word 0x30200073 (mret)
5d687ad google/oak & elm: initialize touchscreen reset gpio

<124 commits skipped>

70cd543 AMD k8 fam10: Drop excessive spinlock initialization
b5664de Romstage spinlocks require EARLY_CBMEM_INIT
d113190 AMD k8 fam10: Fix romstage handoff
880b458 google/chromeec: Update EC command header
1f83ffa gru: include ram_code in coreboot table

See attached log for details

This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 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  regarding any issues stemming from this notification

[Aaron Durbin]

Kyosti, this looks in the area of your recent patches.

<snip>
amdmct_cbmem_store_info: Storing AMDMCT configuration in CBMEM
CBFS: 'Master Header Locator' located CBFS at [100100:1fffc0)
CBFS: Locating 'cmos_layout.bin'
CBFS: Checking offset 0
CBFS: File @ offset 0 size 20
CBFS:  Unmatched 'cbfs master header' at 0
CBFS: Checking offset 80
CBFS: File @ offset 80 size 297fc
CBFS:  Unmatched 'normal/romstage' at 80
CBFS: Checking offset 29900
CBFS: File @ offset 29900 size 280
CBFS:  Unmatched 'config' at 29900
CBFS: Checking offset 29bc0
CBFS: File @ offset 29bc0 size 24e
CBFS:  Unmatched 'revision' at 29bc0
CBFS: Checking offset 29e80
CBFS: File @ offset 29e80 size 100
CBFS:  Unmatched 'cmos.default' at 29e80
CBFS: Checking offset 29fc0
CBFS: File @ offset 29fc0 size e84
CBFS: Found @ offset 29fc0 size e84
disable_spd()
prepare_romstage_ramstack: Prepare CAR migration and stack
regions...memset_:  Fill [003f5400-003fffff]
...prepare_romstage_ramstack:  Done
post_cache_as_ram: Copying data from cache to RAM...memcpy_:  Copy
[000c2c00-000cd2bf] to [003f5940 - 003fffff] ...post_cache_as_ram:
Done
post_cache_as_ram: Verifying data integrity in RAM...memcmp_:  Compare
[000c2c00-000cd2bf] with [003f5940 - 003fffff] ...post_cache_as_ram:
Done
post_cache_as_ram: Switching to use RAM as
stack...cache_as_ram_new_stack: Disabling cache as ram now
prepare_ramstage_region: Prepare ramstage memory region...memset_:
Fill [00000000-003f53ff] ...

On Tue, Jul 19, 2016 at 12:48 PM, Raptor Engineering Automated
Coreboot Test Stand  wrote:
> The ASUS KGPE-D16 fails verification for branch master as of commit dc97b1ce2f4e671e73e2a3fb65e49a881a694590
>
> The following tests failed:
> BOOT_FAILURE
>
> Commits since last successful test:
> dc97b1c soc/intel/apollolake: Fix bitshift issue in bootblock
> b921725 nb/intel/x4x: Fix CAS latency detection
> 47995fb arch/riscv: Remove enter_supervisor
> b8e67ac arch/riscv: Change all eret instructions to .word 0x30200073 (mret)
> 5d687ad google/oak & elm: initialize touchscreen reset gpio
>
> <124 commits skipped>
>
> 70cd543 AMD k8 fam10: Drop excessive spinlock initialization
> b5664de Romstage spinlocks require EARLY_CBMEM_INIT
> d113190 AMD k8 fam10: Fix romstage handoff
> 880b458 google/chromeec: Update EC command header
> 1f83ffa gru: include ram_code in coreboot table
>
> See attached log for details
>
> This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 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  regarding any issues stemming from this notification