[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.0-testing test] 8774: regressions - trouble: blocked/broken/fail/pass
flight 8774 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8774/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-xl-multivcpu 4 xen-install fail REGR. vs. 8763 test-amd64-i386-pv 4 xen-install fail REGR. vs. 8763 test-amd64-i386-xl 4 xen-install fail REGR. vs. 8763 test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail REGR. vs. 8740 build-i386 3 host-build-prep fail REGR. vs. 8763 test-amd64-i386-pair 6 xen-install/dst_host fail REGR. vs. 8763 test-amd64-i386-pair 5 xen-install/src_host fail REGR. vs. 8763 test-amd64-i386-rhel6hvm-intel 4 xen-install fail REGR. vs. 8763 test-amd64-i386-rhel6hvm-amd 4 xen-install fail REGR. vs. 8763 test-amd64-i386-win-vcpus1 4 xen-install fail REGR. vs. 8763 test-amd64-i386-win 4 xen-install fail REGR. vs. 8763 test-amd64-i386-xl-win-vcpus1 4 xen-install fail REGR. vs. 8763 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 8 debian-fixup fail never pass test-i386-i386-pv 1 xen-build-check(1) blocked n/a test-amd64-amd64-xl 15 guest-stop fail never pass test-i386-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-credit2 4 xen-install fail REGR. vs. 8763 test-i386-i386-pair 1 xen-build-check(1) blocked n/a 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-amd64-xl-win 7 windows-install fail never pass test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a version targeted for testing: xen 0383662ea34c baseline version: xen 4b7b75ace863 ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64 pass build-i386 broken build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl fail test-amd64-i386-xl fail test-i386-i386-xl blocked test-amd64-i386-rhel6hvm-amd fail test-amd64-i386-xl-credit2 fail test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu fail test-amd64-amd64-pair pass test-amd64-i386-pair fail test-i386-i386-pair blocked test-amd64-amd64-pv pass test-amd64-i386-pv fail test-i386-i386-pv blocked test-amd64-amd64-xl-sedf fail 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 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: 21530:0383662ea34c tag: tip user: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> date: Wed Aug 31 15:37:57 2011 +0100 IRQ: manually EOI migrating line interrupts When migrating IO-APIC line level interrupts between PCPUs, the migration code rewrites the IO-APIC entry to point to the new CPU/Vector before EOI'ing it. The EOI process says that EOI'ing the Local APIC will cause a broadcast with the vector number, which the IO-APIC must listen to to clear the IRR and Status bits. In the case of migrating, the IO-APIC has already been reprogrammed so the EOI broadcast with the old vector fails to match the new vector, leaving the IO-APIC with an outstanding vector, preventing any more use of that line interrupt. This causes a lockup especially when your root device is using PCI INTA (megaraid_sas driver *ehem*) However, the problem is mostly hidden because send_cleanup_vector() causes a cleanup of all moving vectors on the current PCPU in such a way which does not cause the problem, and if the problem has occured, the writes it makes to the IO-APIC clears the IRR and Status bits which unlocks the problem. This fix is distinctly a temporary hack, waiting on a cleanup of the irq code. It checks for the edge case where we have moved the irq, and manually EOI's the old vector with the IO-APIC which correctly clears the IRR and Status bits. Also, it protects the code which updates irq_cfg by disabling interrupts. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> xen-unstable changeset: 23805:7048810180de xen-unstable date: Wed Aug 31 15:19:24 2011 +0100 changeset: 21529:4b7b75ace863 user: Keir Fraser <keir@xxxxxxx> date: Thu Aug 25 15:36:50 2011 +0100 Update Xen version to 4.0.3-rc2-pre (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |