WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [xen-4.1-testing test] 8663: regressions - FAIL

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [xen-4.1-testing test] 8663: regressions - FAIL
From: xen.org <ian.jackson@xxxxxxxxxxxxx>
Date: Tue, 16 Aug 2011 22:00:42 +0100
Cc: ian.jackson@xxxxxxxxxxxxx
Delivery-date: Tue, 16 Aug 2011 14:04:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
flight 8663 xen-4.1-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8663/

Regressions :-(

Tests which did not succeed and are blocking:
 build-i386-pvops              4 kernel-build               fail REGR. vs. 8426

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-i386-win-vcpus1    1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-rhel6hvm-intel  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-pv            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-pair          1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-i386-i386-xl             1 xen-build-check(1)           blocked  n/a
 test-i386-i386-pv             1 xen-build-check(1)           blocked  n/a
 test-i386-i386-pair           1 xen-build-check(1)           blocked  n/a
 test-i386-i386-xl-win         1 xen-build-check(1)           blocked  n/a
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-i386-i386-win            1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-win-vcpus1  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-multivcpu  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-xl-credit2    1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-rhel6hvm-amd  1 xen-build-check(1)           blocked  n/a
 test-amd64-i386-win           1 xen-build-check(1)           blocked  n/a

version targeted for testing:
 xen                  98c98daab56a
baseline version:
 xen                  84e3706df07a

------------------------------------------------------------
People who touched revisions under test:
  Allen M Kay <allen.m.kay@xxxxxxxxx>
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxxxx>
  Keir Fraser <keir@xxxxxxx>
  Tim Deegan <tim@xxxxxxx>
  Wei Wang2 <wei.wang2@xxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             fail    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           blocked 
 test-i386-i386-xl                                            blocked 
 test-amd64-i386-rhel6hvm-amd                                 blocked 
 test-amd64-i386-xl-credit2                                   blocked 
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               blocked 
 test-amd64-i386-xl-multivcpu                                 blocked 
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         blocked 
 test-i386-i386-pair                                          blocked 
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           blocked 
 test-i386-i386-pv                                            blocked 
 test-amd64-i386-win-vcpus1                                   blocked 
 test-amd64-i386-xl-win-vcpus1                                blocked 
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          blocked 
 test-i386-i386-win                                           blocked 
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        blocked 


------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

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


Not pushing.

------------------------------------------------------------
changeset:   23116:98c98daab56a
tag:         tip
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Tue Aug 16 15:21:46 2011 +0100
    
    x86/PCI-MSI: properly determine VF BAR values
    
    As was discussed a couple of times on this list, SR-IOV virtual
    functions have their BARs read as zero - the physical function's
    SR-IOV capability structure must be consulted instead. The bogus
    warnings people complained about are being eliminated with this
    change.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   23766:8d6edc3d26d2
    xen-unstable date:        Sat Aug 13 10:14:58 2011 +0100
    
    PCI: consolidate interface for adding devices
    
    The functionality of pci_add_device_ext() can be easily folded into
    pci_add_device(), and eliminates the need to change two functions for
    future adjustments.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   23725:4dc6a9ba90d6
    xen-unstable date:        Tue Jul 19 14:14:08 2011 +0100
    
    
changeset:   23115:4797cf482355
user:        Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
date:        Tue Aug 16 15:17:43 2011 +0100
    
    x86: IRQ fix incorrect logic in __clear_irq_vector
    
    In the old code, tmp_mask is the cpu_and of cfg->cpu_mask and
    cpu_online_map.  However, in the usual case of moving an IRQ from one
    PCPU to another because the scheduler decides its a good idea,
    cfg->cpu_mask and cfg->old_cpu_mask do not intersect.  This causes the
    old cpu vector_irq table to keep the irq reference when it shouldn't.
    
    This leads to a resource leak if a domain is shut down wile an irq has
    a move pending, which results in Xen's create_irq() eventually failing
    with -ENOSPC when all vector_irq tables are full of stale references.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    xen-unstable changeset:   23765:68b903bb1b01
    xen-unstable date:        Sat Aug 13 10:14:28 2011 +0100
    
    
changeset:   23114:d52e686e0e2f
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Tue Aug 16 15:17:06 2011 +0100
    
    VT-d: don't reject valid DMAR/ATSR tables on systems with multiple PCI 
segments
    
    On multi-PCI-segment systems, each segment has to be expected to have
    an include-all DRHD and an all-ports ATSR, so the firmware consistency
    check incorrectly rejects valid configurations there (which is
    particularly problematic when the firmware also pre-enabled x2apic
    mode, as the system will panic in that case due to being unable to
    enable interrupt remapping). Thus constrain the check to just segment
    0 for now; once full multi-segment support is there (which I'm working
    on), it can be revisited whether we'd want to track this per segment,
    or whether we trust the firmware of such large systems.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   23763:8f647d409196
    xen-unstable date:        Sat Aug 13 10:12:49 2011 +0100
    
    
changeset:   23113:c8987be040d0
user:        Keir Fraser <keir@xxxxxxx>
date:        Tue Aug 16 15:14:19 2011 +0100
    
    Revert 23092:0f2b9b6c5a74
    
    It has broken unmodified Windows HVM guests for some users:
    
    Signed-off-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   23112:84e3706df07a
user:        Tim Deegan <Tim.Deegan@xxxxxxxxxx>
date:        Fri Aug 12 11:33:41 2011 +0100
    
    Passthrough: disable bus-mastering on any card that causes an IOMMU fault.
    
    This stops the card from raising back-to-back faults and live-locking
    the CPU that handles them.
    
    Signed-off-by: Tim Deegan <tim@xxxxxxx>
    Acked-by: Wei Wang2 <wei.wang2@xxxxxxx>
    Acked-by: Allen M Kay <allen.m.kay@xxxxxxxxx>
    
    
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [xen-4.1-testing test] 8663: regressions - FAIL, xen . org <=