Flaky EFI test

[Heinrich Schuchardt]

On 16.03.21 02:57, Bin Meng wrote:
> On Tue, Mar 16, 2021 at 3:08 AM Tom Rini <trini at konsulko.com> wrote:
>>
>> On Tue, Mar 16, 2021 at 07:23:23AM +1300, Simon Glass wrote:
>>
>>> Hi Heinrich,
>>>
>>> This job failed:
>>>
>>> https://source.denx.de/u-boot/custodians/u-boot-sh/-/jobs/238476
>>>
>>> Do you think this is a flaky test or something else?
>>
>> It looks like qemu-x86 crashed on boot?
>
> Do we have better output of the tests?
>
> Regards,
> Bin
>
https://source.denx.de/u-boot/custodians/u-boot-sh/-/jobs/238476/raw

stops with this console output:

U-Boot 2021.04-rc4-69437-g60228ba289 (Mar 15 2021 - 17:34:22 +0000)
CPU:   QEMU Virtual CPU version 2.5+
DRAM:  128 MiB

So the last message is from announce_dram_init(). The console prompt is
not reached.

The normal output is:

U-Boot 2021.04-rc3-00017-gb764bf21e6 (Mar 16 2021 - 18:11:41 +0100)

CPU:   QEMU Virtual CPU version 2.5+
DRAM:  128 MiB
Video: 1024x768x32
Model: QEMU x86 (I440FX)
Net:   e1000: 52:54:00:12:34:56
       eth0: e1000#0

You will have to enable more debug output to find out where the failure
occurs.

Interestingly when I set CONFIG_LOG=y and CONFIG_LOG_DEFAULT_LEVEL=8
U-Boot's hangs in an endless loop in initcall_run_list() repeating:

include/initcall.h:44-initcall_run_list() initcall: fff05638
include/initcall.h:44-initcall_run_list() initcall: fff05638
include/initcall.h:44-initcall_run_list() initcall: fff05638

You will have to comment out debug statements in initcall_run_list() and
mtrr_commit().

You can reduce .gitlab.yaml to run multiple instances of only this
board. And then retry until you hopefully hit the problem.

The problem seems not to be easily reproducible, cf.

https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/6797

Best regards

Heinrich