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

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

To: "Stefano Stabellini" <stefano.stabellini@xxxxxxxxxxxxx>, "Keir Fraser" <keir@xxxxxxx>
Subject: Re: [Xen-devel] [xen-4.1-testing test] 9805: regressions - FAIL
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Thu, 17 Nov 2011 08:32:30 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx
Delivery-date: Thu, 17 Nov 2011 00:38:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <osstest-9805-mainreport@xxxxxxx>
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>
References: <osstest-9805-mainreport@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 16.11.11 at 23:23, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> flight 9805 xen-4.1-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/9805/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking:
>  test-i386-i386-pv             5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-xl-sedf      5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-pv           5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-xl-multivcpu  5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-rhel6hvm-intel  5 xen-boot                 fail REGR. vs. 
> 9756
>  test-amd64-i386-pv            5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-xl-pcipt-intel  5 xen-boot                fail REGR. vs. 
> 9756
>  test-i386-i386-xl             5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-xl-credit2    5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-rhel6hvm-amd  5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-xl            5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-xl           5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-xl-win-vcpus1  5 xen-boot                  fail REGR. vs. 
> 9756
>  test-amd64-amd64-win          5 xen-boot                   fail REGR. vs. 
> 9756
>  test-i386-i386-xl-win         5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-pair         8 xen-boot/dst_host          fail REGR. vs. 
> 9756
>  test-amd64-amd64-pair         7 xen-boot/src_host          fail REGR. vs. 
> 9756
>  test-i386-i386-pair           7 xen-boot/src_host          fail REGR. vs. 
> 9756
>  test-i386-i386-pair           8 xen-boot/dst_host          fail REGR. vs. 
> 9756
>  test-amd64-i386-pair          8 xen-boot/dst_host          fail REGR. vs. 
> 9756
>  test-amd64-i386-pair          7 xen-boot/src_host          fail REGR. vs. 
> 9756
>  test-amd64-i386-win-vcpus1    5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-amd64-xl-win       5 xen-boot                   fail REGR. vs. 
> 9756
>  test-amd64-i386-win           5 xen-boot                   fail REGR. vs. 
> 9756
>  test-i386-i386-win            5 xen-boot                   fail REGR. vs. 
> 9756

This is due to a bad backport of c/s 24007:0526644ad2a6: In -unstable,
evtchn_unmask() must be called with d->event_lock held, while in 4.1
the function acquires the lock (and now gets called with the lock already
held from do_physdev_op()'s case PHYSDEVOP_eoi). The change dates
back to 23573:584c2e5e03d9, which hardly is a candidate for backporting
(but maybe the locking change needs to be pulled out of there).

Jan


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