flight 6367 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/6367/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-xl-credit2 9 guest-start fail REGR. vs. 6327
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-multivcpu 5 xen-boot fail pass in 6363
test-i386-xcpkern-i386-xl 5 xen-boot fail pass in 6363
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-amd64-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass
test-amd64-i386-win 16 leak-check/check fail never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never pass
test-amd64-xcpkern-i386-rhel6hvm-amd 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-rhel6hvm-intel 8 guest-saverestore fail never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail never pass
test-amd64-xcpkern-i386-xl-win 13 guest-stop fail never pass
test-i386-i386-win 16 leak-check/check fail never pass
test-i386-i386-xl-win 13 guest-stop fail never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail never pass
version targeted for testing:
xen 6fa299ad15c8
baseline version:
xen bbc03993d31f
------------------------------------------------------------
People who touched revisions under test:
Daniel Stodden <daniel.stodden@citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Ian Jackson <ian.jackson@eu.citrix.com>
Jan Beulich <jbeulich@novell.com>
Keir Fraser <keir@xen.org>
Liu, Jinsong <jinsong.liu@intel.com>
Paul Durrant <paul.durrant@citrix.com>
Shriram Rajagopalan <rshriram@cs.ubc.ca>
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Tim Deegan <Tim.Deegan@citrix.com>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-i386-i386-xl pass
test-amd64-xcpkern-i386-xl pass
test-i386-xcpkern-i386-xl fail
test-amd64-i386-rhel6hvm-amd fail
test-amd64-xcpkern-i386-rhel6hvm-amd fail
test-amd64-i386-xl-credit2 fail
test-amd64-xcpkern-i386-xl-credit2 pass
test-amd64-i386-rhel6hvm-intel fail
test-amd64-xcpkern-i386-rhel6hvm-intel fail
test-amd64-i386-xl-multivcpu fail
test-amd64-xcpkern-i386-xl-multivcpu pass
test-amd64-amd64-pair pass
test-amd64-i386-pair pass
test-i386-i386-pair pass
test-amd64-xcpkern-i386-pair pass
test-i386-xcpkern-i386-pair pass
test-amd64-amd64-pv pass
test-amd64-i386-pv pass
test-i386-i386-pv pass
test-amd64-xcpkern-i386-pv pass
test-i386-xcpkern-i386-pv pass
test-amd64-i386-win-vcpus1 fail
test-amd64-i386-xl-win-vcpus1 fail
test-amd64-amd64-win fail
test-amd64-i386-win fail
test-i386-i386-win fail
test-amd64-xcpkern-i386-win fail
test-i386-xcpkern-i386-win fail
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win fail
test-amd64-xcpkern-i386-xl-win fail
------------------------------------------------------------
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.
(No revision log; it would be 521 lines long.)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Jackson
2011-Mar-10 17:48 UTC
[Xen-devel] Re: [xen-unstable test] 6367: regressions - FAIL
Ian Jackson writes ("[xen-unstable test] 6367: regressions -
FAIL"):> test-amd64-i386-xl-multivcpu 5 xen-boot fail pass in 6363
"Watchdog timer detects that CPU4 is stuck!"
The stack trace suggests a scheduler problem.
Ian.
Mar 10 14:15:18.878756 (XEN) Watchdog timer detects that CPU4 is stuck!
Mar 10 14:15:23.438791 (XEN) ----[ Xen-4.1.0-rc7-pre x86_64 debug=y Not
tainted ]----
Mar 10 14:15:23.446757 (XEN) CPU: 4
Mar 10 14:15:23.446771 (XEN) RIP: e008:[<ffff82c4801005b8>]
__bitmap_weight+0x54/0x19f
Mar 10 14:15:23.446794 (XEN) RFLAGS: 0000000000000002 CONTEXT: hypervisor
Mar 10 14:15:23.455773 (XEN) rax: 0000000000000000 rbx: 5555555555555555
rcx: 0000000000000000
Mar 10 14:15:23.455808 (XEN) rdx: ffff8301a7eace50 rsi: 0000000000000002
rdi: 3333333333333333
Mar 10 14:15:23.470803 (XEN) rbp: ffff8301a7edfbf8 rsp: ffff8301a7edfbe0 r8:
0000000000000000
Mar 10 14:15:23.479767 (XEN) r9: 000000000000003b r10: 00ff00ff00ff00ff
r11: 0f0f0f0f0f0f0f0f
Mar 10 14:15:23.479793 (XEN) r12: 0000000000000080 r13: ffff8301a7edfc58
r14: 0000000000000004
Mar 10 14:15:23.487788 (XEN) r15: ffff82c4802d1ac0 cr0: 000000008005003b
cr4: 00000000000006f0
Mar 10 14:15:23.499763 (XEN) cr3: 00000000d7c9c000 cr2: 00000000c471de94
Mar 10 14:15:23.499784 (XEN) ds: 007b es: 007b fs: 00d8 gs: 0033 ss:
0000 cs: e008
Mar 10 14:15:23.514775 (XEN) Xen stack trace from rsp=ffff8301a7edfbe0:
Mar 10 14:15:23.514804 (XEN) ffff82c4802c0100 0000000000000002
0000000000000008 ffff8301a7edfcb8
Mar 10 14:15:23.523778 (XEN) ffff82c480119449 00007cfe581203c7
ffff82c4802d1ac0 ffff82c4802d0cc0
Mar 10 14:15:23.534763 (XEN) ffff82c4802d1ad0 ffff82c4802d1ad0
ffff82c4802d1ad0 ffff82c4802d1ad0
Mar 10 14:15:23.534789 (XEN) 01ff8301a7ee4048 0000000000000f00
0000000000000000 0000000000000010
Mar 10 14:15:23.543782 (XEN) 0000000000000000 0000000000000f10
0000000000000000 0000000000000f00
Mar 10 14:15:23.555763 (XEN) 0000000000000000 ffff8301a7ee4048
ffff8301a7ee4048 ffff8301a7e85048
Mar 10 14:15:23.555789 (XEN) 0000000000000004 ffff82c4802d0cc0
0000000000000000 ffff8301a7edfcc8
Mar 10 14:15:23.567785 (XEN) ffff82c480119582 ffff8301a7edfd28
ffff82c480122c8d 0000000100000001
Mar 10 14:15:23.575770 (XEN) ffff82c4802d0cc0 ffff82c4802d0cc0
ffff8300d7af6000 0000000000000206
Mar 10 14:15:23.575804 (XEN) ffff8300d7af6000 0000000000000004
ffff8300d7af6000 000000018c0c8558
Mar 10 14:15:23.587782 (XEN) ffff8301a7ee4040 ffff8301a7edfd48
ffff82c480122e24 ec86b52f00000000
Mar 10 14:15:23.599799 (XEN) ffff8300d7cd6000 ffff8301a7edfe38
ffff82c480157f17 ffff8300d7af6000
Mar 10 14:15:23.614766 (XEN) 0000000000000003 000000018c0c8558
ffff8301a7ee4040 ffff8301a7edfd88
Mar 10 14:15:23.614805 (XEN) ffff82c480175d4f 00007cfe58120247
ffff82c48014d300 ffff8301a7ee4040
Mar 10 14:15:23.619920 (XEN) 000000018c0c8558 0000000000000003
ffff8300d7af6000 ffff8301a7edfeb8
Mar 10 14:15:23.631767 (XEN) ffff8300d7cd6000 0f0f0f0f0f0f0f0f
00ff00ff00ff00ff 0000000000000086
Mar 10 14:15:23.631823 (XEN) ffff8301a7edfdf8 ffff82c480123b91
0000000000000004 0000000000000000
Mar 10 14:15:23.646773 (XEN) 0000000000000000 ffff8301a7edfe38
ffff8300d7cd6000 ffff8300d7af6000
Mar 10 14:15:23.658765 (XEN) 0000000000000003 000000018c0c8558
ffff8301a7ee4040 ffff8301a7edfeb8
Mar 10 14:15:23.658802 (XEN) ffff82c4801226b4 ffff8301a7edfe68
000000018c0c8558 ffff8301a7ee4100
Mar 10 14:15:23.667778 (XEN) Xen call trace:
Mar 10 14:15:23.667800 (XEN) [<ffff82c4801005b8>]
__bitmap_weight+0x54/0x19f
Mar 10 14:15:23.675759 (XEN) [<ffff82c480119449>]
_csched_cpu_pick+0x2ef/0x41a
Mar 10 14:15:23.675780 (XEN) [<ffff82c480119582>]
csched_cpu_pick+0xe/0x10
Mar 10 14:15:23.687771 (XEN) [<ffff82c480122c8d>]
vcpu_migrate+0xfb/0x230
Mar 10 14:15:23.687802 (XEN) [<ffff82c480122e24>]
context_saved+0x62/0x7b
Mar 10 14:15:23.699772 (XEN) [<ffff82c480157f17>]
context_switch+0xd98/0xdca
Mar 10 14:15:23.699805 (XEN) [<ffff82c4801226b4>] schedule+0x5fc/0x624
Mar 10 14:15:23.714777 (XEN) [<ffff82c480123837>]
__do_softirq+0x88/0x99
Mar 10 14:15:23.714815 (XEN) [<ffff82c4801238b2>] do_softirq+0x6a/0x7a
Mar 10 14:15:23.719769 (XEN)
Mar 10 14:15:23.719787 (XEN)
Mar 10 14:15:23.719806 (XEN) ****************************************
Mar 10 14:15:23.719824 (XEN) Panic on CPU 4:
Mar 10 14:15:23.719837 (XEN) FATAL TRAP: vector = 2 (nmi)
Mar 10 14:15:23.734772 (XEN) [error_code=0000] , IN INTERRUPT CONTEXT
Mar 10 14:15:23.734801 (XEN) ****************************************
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel