On 07/08/2019 14:26, Marek Marczykowski-Górecki wrote:
> Hi,
>
> Xen 4.12 crashes when booting on UEFI (with multiboot2) unless I disable
> runtime services. The crash happens shortly after starting dom0 kernel.
> Unfortunately I don't have serial console there, so the only log I have
> is a photo of VGA console (attached). Below I retype part of the message:
>
> (XEN) ----[ Xen-4.12.0-3.fc29  x86_64  debug=n   Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<00000000000000f6>] 00000000000000f6
> (XEN) RFLAGS: 0000000000010287   CONTEXT: hypervisor (d0v0)
> ...
> (XEN) Xen call trace:
> (XEN)    [<00000000000000f6>] 00000000000000f6
> (XEN)    [<ffff82d08026c6ad>] flushtlb.c#pre_flush+0x3d/0x80
> (XEN)    [                  ] efi_runtime_call+0x493/0xbd0
> (XEN)    [                  ] efi_runtime_call+0x441/0xbd0
> (XEN)    [                  ] vcpu_restore_fpu_nonlazy+0xe7/0x180
> (XEN)    [                  ] do_platform_op+0/0x1880
> (XEN)    [                  ] do_platform_op+0xb9c/0x1880
> (XEN)    [                  ] do_platform_op+0xb9c/0x1880
> (XEN)    [                  ] sched_credit2.c#csched2_schedule+0xcd0/0x13a0
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] do_platform_op+0/0x1880
> (XEN)    [                  ] pv_hypercall+0x152/0x220
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0xa2/0x120
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0xa2/0x120
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0xa2/0x120
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0xa2/0x120
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0xa2/0x120
> (XEN)    [                  ] lstar_enter+0xae/0x120
> (XEN)    [                  ] lstar_enter+0x10c/0x120
> (XEN)
> (XEN)
> (XEN) *****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL TRAP: vector = 0 (divide error)
> (XEN) [error_code=0000]
> (XEN) *****************************************
>
> Any idea?

Very weird.

You got a #DE because the instruction under %rip is `div %bh`, but
judging from the photo, that page is poisoned anyway.

The chances are that something jumped to 0 and has executed it this far
through the poisoned page before actually faulting.

Can you disassemble pre_flush() ?  I don't see anything interesting at
the C level.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to