[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [ovmf baseline-only test] 71343: tolerable FAIL



This run is configured for baseline tests only.

flight 71343 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71343/

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 build-amd64-libvirt           5 libvirt-build                fail   like 71342
 build-i386-libvirt            5 libvirt-build                fail   like 71342

version targeted for testing:
 ovmf                 7a85e8474127ae6df47337a04797b2b443b57682
baseline version:
 ovmf                 11a6cc5bda811513d2fbe47d8cb1a70b48077800

Last test of basis    71342  2017-05-18 06:51:54 Z    0 days
Testing same since    71343  2017-05-18 13:19:36 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Dandan Bi <dandan.bi@xxxxxxxxx>
  Laszlo Ersek <lersek@xxxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          fail    
 build-i386-libvirt                                           fail    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit 7a85e8474127ae6df47337a04797b2b443b57682
Author: Dandan Bi <dandan.bi@xxxxxxxxx>
Date:   Thu May 18 09:51:42 2017 +0800

    MdeModulePkg/PciHostBridgeDxe: Fix EBC build failure
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Dandan Bi <dandan.bi@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit 639c7dd86d1d63a6c4ac5f19f8a97986aa1f363b
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 23:59:04 2017 +0100

    OvmfPkg: resolve PcdLib for PEIMs to PeiPcdLib by default
    
    In the previous patch we had to add two explicit Null resolutions, but
    here we can remove five PeiPcdLib ones, after setting the default to it.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit fbce1fe983f6d0cc10607c533d1bd09c4bceba0a
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 23:52:28 2017 +0100

    OvmfPkg: resolve PcdLib for all PEIMs individually
    
    Currently the default (module type independent) PcdLib resolution is to
    BasePcdLibNull.inf, which is inherited by all PEIMs. In the next patch,
    we'll flip the PEIM default resolution to PeiPcdLib.inf, but in order to
    keep that patch both correct and simple to review, we should spell out the
    Null resolution for those two PEIMs (ReportStatusCodeRouterPei and
    StatusCodeHandlerPei) that are now the only ones that don't specify an
    explicit resolution.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 5e167d7e784c92591921c29b61f0f7a000d9c7ce
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 22:01:40 2017 +0100

    OvmfPkg/PlatformPei: don't allocate reserved mem varstore if SMM_REQUIRE
    
    For the emulated variable store, PlatformPei allocates reserved memory (as
    early as possible, so that the address remains the same during reboot),
    and PcdEmuVariableNvStoreReserved carries the address to
    EmuVariableFvbRuntimeDxe.
    
    However, EmuVariableFvbRuntimeDxe is excluded from the SMM_REQUIRE build,
    and then noone consumes PcdEmuVariableNvStoreReserved. Don't waste
    reserved memory whenever that's the case.
    
    (Even a dynamic default for PcdEmuVariableNvStoreReserved would be
    unnecessary; but that way the PcdSet64S() call in the
    ReserveEmuVariableNvStore() function doesn't compile.)
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 62f43f7c1947c799dd69fb4b2d94376b8e689b51
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 5 03:31:32 2017 +0200

    OvmfPkg: sync PcdVariableStoreSize with PcdFlashNvStorageVariableSize
    
    "MdeModulePkg/MdeModulePkg.dec" declares PcdVariableStoreSize like this:
    
    > The size of volatile buffer. This buffer is used to store VOLATILE
    > attribute variables.
    
    There is no inherent reason why the size of the volatile variable store
    should match the same of the non-volatile variable store. Indeed flash
    variables in the 4MB build work fine without this equality.
    
    However, OvmfPkg/EmuVariableFvbRuntimeDxe uses PcdVariableStoreSize to
    initialize the non-volatile VARIABLE_STORE_HEADER too. (Presumably based
    on the fact that ultimately that storage will not be permanent.) When
    using EmuVariableFvbRuntimeDxe in the 4MB build, the mismatch between the
    two mentioned PCDs (which is apparent through EmuVariableFvbRuntimeDxe's
    VARIABLE_STORE_HEADER) triggers an assertion in the variable driver:
    
    > ASSERT MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c(3772):
    > mNvVariableCache->Size == VariableStoreLength
    
    Bringing PcdVariableStoreSize in sync with PcdFlashNvStorageVariableSize
    fixes this. It also happens to ensure a volatile store size in the 4MB
    build that equals the non-volatile store size, which likely doesn't hurt
    for symmetry.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Fixes: b24fca05751f8222acf264853709012e0ab7bf49
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit c15c1c086325efd9b50ca754e44a52501d5fc5ca
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 21:01:25 2017 +0100

    OvmfPkg/PlatformPei: remove unused PcdVariableStoreSize dependency
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 5c27723204a89b65c175b6f4f641dc6437b45f99
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 20:54:16 2017 +0100

    OvmfPkg: remove gUefiOvmfPkgTokenSpaceGuid.PcdSecureBootEnable
    
    This PCD is no longer used.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 6d7af0c9bc5e0d98092da9b6593b31abbc69dc76
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sun Mar 12 20:51:08 2017 +0100

    OvmfPkg/EmuVariableFvbRuntimeDxe: always format an auth varstore header
    
    In this patch, we extend commit d92eaabefbe0 ("OvmfPkg: simplify
    VARIABLE_STORE_HEADER generation", 2016-02-05) to
    EmuVariableFvbRuntimeDxe.
    
    This is the difference between FvAndVarTemplate and
    FvAndAuthenticatedVarTemplate:
    
    > --- non-auth    2017-05-05 22:32:06.001512283 +0200
    > +++ auth        2017-05-05 22:32:18.841364882 +0200
    > @@ -1,7 +1,7 @@
    >    //
    > -  // Templates for standard (non-authenticated) variable FV header
    > +  // Templates for authenticated variable FV header
    >    //
    > -  STATIC FVB_FV_HDR_AND_VARS_TEMPLATE FvAndVarTemplate = {
    > +  STATIC FVB_FV_HDR_AND_VARS_TEMPLATE FvAndAuthenticatedVarTemplate = {
    >      { // EFI_FIRMWARE_VOLUME_HEADER FvHdr;
    >        // UINT8                     ZeroVector[16];
    >        { 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
    > @@ -34,7 +34,7 @@
    >        EFI_FVH_REVISION,
    >
    >        // EFI_FV_BLOCK_MAP_ENTRY    BlockMap[1];
    > -      {
    > +      {
    >          {
    >            2, // UINT32 NumBlocks;
    >            EMU_FVB_BLOCK_SIZE  // UINT32 Length;
    > @@ -44,8 +44,8 @@
    >      // EFI_FV_BLOCK_MAP_ENTRY     EndBlockMap;
    >      { 0, 0 }, // End of block map
    >      { // VARIABLE_STORE_HEADER      VarHdr;
    > -      // EFI_GUID  Signature;
    > -      EFI_VARIABLE_GUID,
    > +        // EFI_GUID  Signature;     // need authenticated variables for 
secure boot
    > +        EFI_AUTHENTICATED_VARIABLE_GUID,
    >
    >        // UINT32  Size;
    >        (
    
    After this change, using "-bios", the variable driver logs:
    
    - with the SB feature enabled:
    > Variable driver will work with auth variable format!
    > Variable driver will work with auth variable support!
    
    - with the SB feature disabled:
    > Variable driver will work with auth variable format!
    > Variable driver will continue to work without auth variable support!
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.