[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable-smoke test] 105283: regressions - trouble: broken/fail/pass
On 02/02/17 13:56, osstest service owner wrote: > flight 105283 xen-unstable-smoke real [real] > http://logs.test-lab.xenproject.org/osstest/logs/105283/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-qemuu-debianhvm-i386 6 xen-boot fail REGR. vs. > 105218 > test-amd64-amd64-libvirt 6 xen-boot fail REGR. vs. > 105218 From http://logs.test-lab.xenproject.org/osstest/logs/105283/test-amd64-amd64-xl-qemuu-debianhvm-i386/serial-elbling1.log around Feb 2 12:33:05.733614 (XEN) CPU Vendor: Intel, Family 6 (0x6), Model 62 (0x3e), Stepping 4 (raw 000306e4) (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.7 present. (XEN) Using APIC driver bigsmp (XEN) Assertion 'vm_low[t] == vm_top[t] || !test_bit(vm_low[t], vm_bitmap(t))' failed at vmap.c:67 (XEN) ----[ Xen-4.9-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82d0801387a0>] __vmap+0xa4/0x3af (XEN) RFLAGS: 0000000000010086 CONTEXT: hypervisor (XEN) rax: ffff82c000000000 rbx: 000000000000034c rcx: ffff82d0802ed800 (XEN) rdx: 00000000ffffffff rsi: 0000000000000000 rdi: ffff82d08030564e (XEN) rbp: ffff82d08030fd28 rsp: ffff82d08030fcc8 r8: 0000000000800173 (XEN) r9: 0000000000000000 r10: 0000000000000001 r11: 00000000ffffffff (XEN) r12: 0000000000000000 r13: 0000000000000001 r14: 0000000000000000 (XEN) r15: 0000000000000001 cr0: 0000000080050033 cr4: 00000000000000a0 (XEN) cr3: 00000000cd104000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: e008 (XEN) Xen code around <ffff82d0801387a0> (__vmap+0xa4/0x3af): (XEN) a3 10 19 d2 85 d2 74 02 <0f> 0b 44 89 e0 48 8d 15 2c a5 1e 00 8b 1c 82 eb (XEN) Xen stack trace from rsp=ffff82d08030fcc8: (XEN) ffff82d08030fcf8 0080017380133e04 0000000100000001 ffff82d08030fd40 (XEN) ffff82d080342da0 00000000ffffffff ffff82d08030fd08 000000000000034c (XEN) ffff82d08030fdb0 ffff82d08024b000 0000000000000000 ffff82d08029d000 (XEN) ffff82d08030fd58 ffff82d08015e2fd 0000000000000000 00000000000cd335 (XEN) ffff82d08030fd78 ffff8300cd2ef040 ffff82d08030fd78 ffff82d0802b6f41 (XEN) 0000000000000000 0000000000000040 ffff82d08030fd98 ffff82d0802b713c (XEN) ffff82d0802d54e0 ffff82d0802c7e88 ffff82d08030fdc8 ffff82d0802b874c (XEN) 00ffffffffffff27 0000000000000000 000000000022ffff ffff82d0802ea000 (XEN) ffff82d08030fdf8 ffff82d0802c87a5 ffff82d08030fdf8 000000000022ffff (XEN) ffff82d0802ea000 ffff82d08024b000 ffff82d08030ff08 ffff82d0802c4898 (XEN) 0000000000000000 0000000000100000 00000000000001ff 0000000000000001 (XEN) 0000000000000001 0000000000000001 0000000000000001 0000000000000001 (XEN) 0000000000000001 0000000000000001 0000000000000000 00000000011f3000 (XEN) 0000000000230000 0000000000800163 fffffffffffff001 0000000100000000 (XEN) 0000000000000000 ffff83000008bdc0 ffff83000008bf10 ffff83000008bfb0 (XEN) 0000000000000000 0000000000000000 0000000800000000 000000010000006e (XEN) 0000000000000003 00000000000002f8 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffff82d080100073 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) Xen call trace: (XEN) [<ffff82d0801387a0>] __vmap+0xa4/0x3af (XEN) [<ffff82d08015e2fd>] acpi_os_map_memory+0xcf/0xe0 (XEN) [<ffff82d0802b6f41>] acpi_tb_verify_table+0x2f/0x62 (XEN) [<ffff82d0802b713c>] acpi_get_table+0x5b/0xa6 (XEN) [<ffff82d0802b874c>] acpi_table_parse+0x62/0x8c (XEN) [<ffff82d0802c87a5>] acpi_boot_init+0x3b/0x32f (XEN) [<ffff82d0802c4898>] __start_xen+0x1fca/0x2878 (XEN) [<ffff82d080100073>] __high_start+0x53/0x55 (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) Assertion 'vm_low[t] == vm_top[t] || !test_bit(vm_low[t], vm_bitmap(t))' failed at vmap.c:67 (XEN) **************************************** (XEN) Boris: looks like your vmap changes weren't safe. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |