| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] [xen-unstable test] 7619: regressions - FAIL
flight 7619 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/7619/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-xl-credit2 10 guest-saverestore fail in 7611 REGR. vs. 7607
test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail in 7611 REGR.
vs. 7607
test-amd64-xcpkern-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 7608
REGR. vs. 7607
Tests which are failing intermittently (not blocking):
build-i386 4 xen-build fail pass in 7611
test-amd64-xcpkern-i386-pv 4 xen-install fail pass in 7611
test-amd64-i386-pv 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-xl 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-xl-credit2 4 xen-install fail pass in 7611
test-amd64-i386-pair 6 xen-install/dst_host fail pass in 7611
test-amd64-i386-pair 5 xen-install/src_host fail pass in 7611
test-amd64-xcpkern-i386-xl-multivcpu 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-pair 5 xen-install/src_host fail pass in 7611
test-amd64-xcpkern-i386-pair 6 xen-install/dst_host fail pass in 7611
test-amd64-xcpkern-i386-rhel6hvm-intel 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-rhel6hvm-amd 4 xen-install fail pass in 7611
test-amd64-i386-xl-credit2 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-xl-win 4 xen-install fail pass in 7611
test-amd64-i386-xl 4 xen-install fail pass in 7611
test-amd64-i386-rhel6hvm-intel 4 xen-install fail pass in 7611
test-amd64-i386-xl-multivcpu 4 xen-install fail pass in 7611
test-amd64-i386-rhel6hvm-amd 4 xen-install fail pass in 7611
test-amd64-i386-xl-win-vcpus1 4 xen-install fail pass in 7611
test-amd64-i386-win-vcpus1 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-win 4 xen-install fail pass in 7611
test-amd64-i386-win 4 xen-install fail pass in 7611
test-amd64-xcpkern-i386-rhel6hvm-amd 9 guest-localmigrate fail in 7611 pass in
7608
test-amd64-i386-xl-credit2 9 guest-start fail in 7608 pass in 7611
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-i386-xcpkern-i386-pv 1 xen-build-check(1) blocked n/a
test-i386-i386-pv 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-xl 1 xen-build-check(1) blocked n/a
test-i386-i386-xl 1 xen-build-check(1) blocked n/a
test-i386-i386-pair 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-pair 1 xen-build-check(1) blocked n/a
test-amd64-amd64-win 16 leak-check/check fail never pass
test-amd64-amd64-xl-win 13 guest-stop fail never pass
test-i386-i386-xl-win 1 xen-build-check(1) blocked n/a
test-i386-i386-win 1 xen-build-check(1) blocked n/a
test-i386-xcpkern-i386-win 1 xen-build-check(1) blocked n/a
test-amd64-xcpkern-i386-rhel6hvm-intel 14 guest-start.2 fail in 7611 never pass
test-amd64-xcpkern-i386-xl-win 13 guest-stop fail in 7611 never pass
test-amd64-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 7611 never pass
test-amd64-i386-xl-win-vcpus1 13 guest-stop fail in 7611 never pass
test-amd64-i386-win-vcpus1 16 leak-check/check fail in 7611 never pass
test-amd64-xcpkern-i386-win 16 leak-check/check fail in 7611 never pass
test-amd64-i386-win 16 leak-check/check fail in 7611 never pass
test-i386-i386-xl-win 13 guest-stop fail in 7611 never pass
test-i386-i386-win 16 leak-check/check fail in 7611 never pass
test-i386-xcpkern-i386-win 16 leak-check/check fail in 7611 never pass
version targeted for testing:
xen d25f2c114ace
baseline version:
xen 23c068b10923
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Jan Beulich <jbeulich@xxxxxxxxxx>
Keir Fraser <keir@xxxxxxx>
------------------------------------------------------------
jobs:
build-i386-xcpkern pass
build-amd64 pass
build-i386 fail
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 fail
test-i386-i386-xl blocked
test-amd64-xcpkern-i386-xl fail
test-i386-xcpkern-i386-xl blocked
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 fail
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 fail
test-amd64-amd64-pair pass
test-amd64-i386-pair fail
test-i386-i386-pair blocked
test-amd64-xcpkern-i386-pair fail
test-i386-xcpkern-i386-pair blocked
test-amd64-amd64-pv pass
test-amd64-i386-pv fail
test-i386-i386-pv blocked
test-amd64-xcpkern-i386-pv fail
test-i386-xcpkern-i386-pv blocked
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-xcpkern-i386-win fail
test-i386-xcpkern-i386-win blocked
test-amd64-amd64-xl-win fail
test-i386-i386-xl-win blocked
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.
------------------------------------------------------------
changeset: 23546:d25f2c114ace
tag: tip
user: Keir Fraser <keir@xxxxxxx>
date: Wed Jun 15 20:33:58 2011 +0100
x86_emulate: Fix decode of FUCOMIP %stN.
Signed-off-by: Keir Fraser <keir@xxxxxxx>
changeset: 23545:e462d2e76734
user: Jan Beulich <jbeulich@xxxxxxxxxx>
date: Wed Jun 15 20:25:13 2011 +0100
x86: sync thermal monitor LVT handling with Linux
As of 2.6.33, Linux checks that the thermal monitor LVT isn't set to
SMI delivery mode on just the value read on the boot CPU. As of 2.6.39
it additionally avoids writing back the saved value when its delivery
mode is FIXED (as this can cause APIC errors).
Changes done here that aren't in Linux are
- write back the boot CPU value also if delivery mode is FIXED, but
there is also a valid vector
- print the messages when bailing out only once (on the boot CPU)
- when doing the final (enabling) write to the LVT, don't re-read the
old value from the APIC, as we have it in a local variable already
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
changeset: 23544:644838dc1322
user: Jan Beulich <jbeulich@xxxxxxxxxx>
date: Wed Jun 15 20:24:41 2011 +0100
x86/apic: check maxlvt before accessing certain LVT fields
This follows Linux, including in not checking maxlvt for certain
accesses to APIC_LVTERR.
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
changeset: 23543:a8edfacd4b5e
user: Jan Beulich <jbeulich@xxxxxxxxxx>
date: Wed Jun 15 20:24:09 2011 +0100
x86-64: fix incorrect assertion in __maddr_to_virt()
When memory map sparseness reduction is in use, machine address ranges
can't validly be compared directly against the total size of the
direct mapping range.
Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
changeset: 23542:23c068b10923
user: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
date: Wed Jun 15 16:16:41 2011 +0100
KEXEC: correctly revert x2apic state when kexecing
Introduce the boolean variable 'kexecing' which indicates to functions
whether we are on the kexec path or not. This is used by
disable_local_APIC() to try and revert the APIC mode back to how it
was found on boot.
We also need some fudging of the x2apic_enabled variable. It is used
in multiple places over the codebase to mean multiple things,
including:
What did the user specifify on the command line?
Did the BIOS boot me in x2apic mode?
Is the BSP Local APIC in x2apic mode?
What mode is my Local APIC in?
Therefore, set it up to prevent a protection fault when disabling the
IOAPICs. (In this case, it is used in the "What mode is my Local APIC
in?" case, so the processor doesnt suffer a protection fault because
of trying to use x2apic MSRs when it should be using xapic MMIO)
Finally, make sure that interrupts are disabled when jumping into the
purgatory code. It would be bad to service interrupts in the Xen
context when the next kernel is booting.
Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
(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-unstable test] 7619: regressions - FAIL,
xen . org <=
|
|
|
| |
|
Home