Re: [Xen-devel] [xen-unstable test] 33690: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 24.01.15 at 13:54, <Ian.Jackson@xxxxxxxxxxxxx> wrote:
> flight 33690 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/33690/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-rumpuserxen-amd64 11 rumpuserxen-demo-xenstorels/xenstorels 
> fail REGR. vs. 33637
>  test-amd64-i386-freebsd10-i386  8 guest-start             fail REGR. vs. 
> 33637
>  test-amd64-amd64-xl-qemut-debianhvm-amd64 7 debian-hvm-install fail REGR. 
> vs. 33637
>  test-amd64-i386-pair          7 xen-boot/src_host         fail REGR. vs. 
> 33637
>  test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 
> 33637
>  test-amd64-i386-xl-qemut-winxpsp3  7 windows-install      fail REGR. vs. 
> 33637
>  test-amd64-i386-xl-qemuu-winxpsp3  7 windows-install      fail REGR. vs. 
> 33637
>  test-amd64-amd64-xl-winxpsp3  7 windows-install           fail REGR. vs. 
> 33637
>  test-amd64-i386-xl-qemut-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 
> 33637
>  test-amd64-amd64-xl-qemut-win7-amd64  7 windows-install   fail REGR. vs. 
> 33637

Jan 24 00:35:16.262627 (XEN) ----[ Xen-4.6-unstable  x86_64  debug=y  Not 
tainted ]----
Jan 24 00:35:16.478599 (XEN) CPU:    1
Jan 24 00:35:16.478624 (XEN) RIP:    e008:[<0000000000000000>] 0000000000000000
Jan 24 00:35:16.486596 (XEN) RFLAGS: 0000000000010082   CONTEXT: hypervisor
...
Jan 24 00:35:16.678620 (XEN) Xen call trace:
Jan 24 00:35:16.678650 (XEN)    [<ffff82d0801d36d0>] vpmu_do_interrupt+0x2f/0x8a
Jan 24 00:35:16.686605 (XEN)    [<ffff82d08015e242>] 
pmu_apic_interrupt+0x33/0x35
Jan 24 00:35:16.698582 (XEN)    [<ffff82d080171bf0>] do_IRQ+0x9c/0x624
Jan 24 00:35:16.698615 (XEN)    [<ffff82d080234062>] common_interrupt+0x62/0x70
Jan 24 00:35:16.698653 (XEN)    [<ffff82d08012c6fe>] _spin_unlock_irq+0x30/0x31
Jan 24 00:35:16.706604 (XEN)    [<ffff82d08012bcf1>] __do_softirq+0x81/0x8c
Jan 24 00:35:16.706638 (XEN)    [<ffff82d08012bd49>] do_softirq+0x13/0x15
Jan 24 00:35:16.718591 (XEN)    [<ffff82d0801ec4da>] 
vmx_asm_do_vmentry+0x2a/0x50

Others look similar. Please advise which of the 8 patches that went
in on Friday from the beginning of your vPMU series need to be
reverted. Please also explain how, with vPMU support being off by
default, execution reaches vPMU code in the first place.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel