On 20/06/18 00:24, osstest service owner wrote: > flight 124372 xen-unstable real [real] > http://logs.test-lab.xenproject.org/osstest/logs/124372/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-pvhv2-intel 7 xen-boot fail REGR. vs. > 124090 > test-amd64-amd64-xl-credit2 7 xen-boot fail REGR. vs. > 124090 > test-amd64-amd64-xl-xsm 7 xen-boot fail REGR. vs. > 124090 > test-amd64-amd64-xl-pvshim 7 xen-boot fail REGR. vs. > 124090
Andrew, Jan, could you please look into this? This is a blocker for 4.11 Jun 19 17:00:31.408007 (XEN) *** Serial input -> DOM0 (type 'CTRL-x' three times to switch input to Xen) Jun 19 17:00:32.092057 (XEN) Freed 492kB init memory Jun 19 17:00:32.104055 mapping kernel into physical memory Jun 19 17:00:32.104073 about to get started... Jun 19 17:00:32.104084 (XEN) Assertion '!v->arch.fully_eager_fpu' failed at i387.c:259 Jun 19 17:00:32.116061 (XEN) ----[ Xen-4.11-rc x86_64 debug=y Not tainted ]---- Jun 19 17:00:32.116083 (XEN) CPU: 0 Jun 19 17:00:32.116092 (XEN) RIP: e008:[<ffff82d08028b97d>] vcpu_restore_fpu_lazy+0x25/0xe8 Jun 19 17:00:32.128056 (XEN) RFLAGS: 0000000000010202 CONTEXT: hypervisor (d0v0) Jun 19 17:00:32.128077 (XEN) rax: ffff83046ccf6000 rbx: ffff83008effc000 rcx: 0000000000000000 Jun 19 17:00:32.140058 (XEN) rdx: ffff82d0802b97b5 rsi: 0000000000000000 rdi: ffff83008effc000 Jun 19 17:00:32.152052 (XEN) rbp: ffff8300864a7ee8 rsp: ffff8300864a7ec0 r8: 0000000000000000 Jun 19 17:00:32.152075 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 Jun 19 17:00:32.164058 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: ffff8300864a7fff Jun 19 17:00:32.164079 (XEN) r15: 0000000000000000 cr0: 0000000080050033 cr4: 0000000000372660 Jun 19 17:00:32.176057 (XEN) cr3: 000000045e20a000 cr2: 0000000000000000 Jun 19 17:00:32.176076 (XEN) fsb: 0000000000000000 gsb: ffffffff82729000 gss: 0000000000000000 Jun 19 17:00:32.188058 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 Jun 19 17:00:32.200055 (XEN) Xen code around <ffff82d08028b97d> (vcpu_restore_fpu_lazy+0x25/0xe8): Jun 19 17:00:32.200078 (XEN) bf 69 0b 00 00 00 74 02 <0f> 0b 55 48 89 e5 53 48 83 ec 08 48 89 fb 8b 05 Jun 19 17:00:32.212059 (XEN) Xen stack trace from rsp=ffff8300864a7ec0: Jun 19 17:00:32.212079 (XEN) ffff82d0802b97fa ffff82d080387969 ffff82d08038795d ffff82d080387969 Jun 19 17:00:32.224058 (XEN) ffff83008effc000 00007cff79b580e7 ffff82d080387a2f 0000000000000000 Jun 19 17:00:32.236056 (XEN) ffffffff82203f30 0000000000000000 0000000001000000 ffffffff82203ec0 Jun 19 17:00:32.236077 (XEN) ffffffff82203e90 ffffffff81fbffbd ffffffff82803140 0000000000000000 Jun 19 17:00:32.248059 (XEN) 0000000000000000 ffffffff82885180 0000000000000000 0000000000000000 Jun 19 17:00:32.248080 (XEN) 0000000000000001 0000000000000000 0000000700000000 ffffffff81092e59 Jun 19 17:00:32.260059 (XEN) 000000000000e033 0000000000010202 ffffffff82203e78 000000000000e02b Jun 19 17:00:32.272056 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 Jun 19 17:00:32.272076 (XEN) 0000000000000000 ffff83008effc000 0000000000000000 0000000000372660 Jun 19 17:00:32.284056 (XEN) 0000000000000000 80000004617fb002 0000040000000000 0000000000000000 Jun 19 17:00:32.296054 (XEN) Xen call trace: Jun 19 17:00:32.296071 (XEN) [<ffff82d08028b97d>] vcpu_restore_fpu_lazy+0x25/0xe8 Jun 19 17:00:32.296086 (XEN) [<ffff82d080387a2f>] x86_64/entry.S#handle_exception_saved+0x68/0x94 Jun 19 17:00:32.308060 (XEN) Jun 19 17:00:32.308074 (XEN) Jun 19 17:00:32.308082 (XEN) **************************************** Jun 19 17:00:32.308093 (XEN) Panic on CPU 0: Jun 19 17:00:32.320012 (XEN) Assertion '!v->arch.fully_eager_fpu' failed at i387.c:259 Jun 19 17:00:32.320034 (XEN) **************************************** Juergen _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
