[MinnowBoard] Firmware hang

Wei, David david.wei at intel.com
Wed Oct 26 08:36:13 UTC 2016

The Minnowboard max UEFI firmware could pass the stress test of thousands of system reset cycle. 
There are two causes I can think:
(1) The SPI flash is already under unstable state. As we are talking in another mail loop.
(2) The UEFI variable region garbage reclaiming process is interrupted by system reset/shutdown.  

David  Wei                                 

-----Original Message-----
From: elinux-MinnowBoard [mailto:elinux-minnowboard-bounces at lists.elinux.org] On Behalf Of Sjoerd Simons
Sent: Wednesday, October 26, 2016 3:01 PM
To: MinnowBoard Development and Community Discussion <elinux-minnowboard at lists.elinux.org>
Subject: Re: [MinnowBoard] Firmware hang

On Wed, 2016-10-26 at 01:40 +0000, Wei, David wrote:
> The log shows that the UEFI "Setup" and "SetupRecovery" variables in
> SPI flash are corrupted. 
> What kind of test were you running in lab?  

These board are in our lava lab, running mostly boot tests (part of
kernelci.org) and project image testing. For each test there will be a
hard power off/on event one or more times (remote controlled power
socket). I didn't do the math but i would expect these boards to have
seen at least 10 to 20 hard resets every day for the last 2 years or so
(with old firmware). 

We don't run any tests which write to the SPI flash so the only write
cycles that should see are those from the firmware itself.

> Thanks,
> David  Wei                                 
> -----Original Message-----
> From: elinux-MinnowBoard [mailto:elinux-minnowboard-bounces at lists.eli
> nux.org] On Behalf Of Sjoerd Simons
> Sent: Tuesday, October 25, 2016 9:42 PM
> To: elinux-minnowboard at lists.elinux.org
> Subject: [MinnowBoard] Firmware hang
> Hey,
> I've been having issues with some of the minnowboard max boards in
> our
> test lab for a while where at times they never finished post.
> Reflashing the flash seemed to help for a while, until the issues
> came
> back again. With the debug version of the firmware the last few lines
> are:
> Gpio_S5_4 value is 0x3
> Gpio_S5_17 value is 0x3
> Firmware Volume for Variable Store is corrupted
> Firmware Volume for Variable Store is corrupted
> ASSERT_EFI_ERROR (Status = Not Found)
> ASSERT m:\Vlv2TbltDevicePkg\PlatformInitPei\PlatformEarlyInit.c(213):
> !EFI_ERROR (Status)
> A full log can be found here:
>   https://lava.collabora.co.uk/scheduler/job/367353/log_file
> Any ideas?

Sjoerd Simons
Collabora Ltd.
elinux-MinnowBoard mailing list
elinux-MinnowBoard at lists.elinux.org

More information about the elinux-MinnowBoard mailing list