This test is triggering some kind of bug that will reliably cause a full host crash/hang of the x86 host environment on TGL/cAVS 2.5. It's interfering with CI testing, so filter it out for now while we figure it out. Interestingly it doesn't have any trouble on older cavs15. And even more so, it seems to be some kind of build interaction. If I disable LOG=y, it passes. But when it fails, it actually fails BEFORE the boot entry and core 0 initialization code is reached (i.e. LONG before any logging initialization). Something is wrong with the generated file; maybe a linker or rimage bug? The signature is reported OK by the ROM, but that's the last we hear from the device before it blows up. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
5 lines
105 B
YAML
5 lines
105 B
YAML
tests:
|
|
kernel.objects.tracking:
|
|
tags: kernel
|
|
platform_exclude: qemu_x86_tiny intel_adsp_cavs25
|