Hi Alex and all,
Our nightly testing system report last night testing met Xen
crashing. The problem changeset would before 15556. I think the issue was
brought in by 32 side’s codes.
After manually checking, the crashing would happen when
destroy a VTI domain.
The serial log:
(XEN) Xen BUG at event_channel.c:912x20000000200a0026,
ip=0x000000006011dc10
(XEN) FIXME: implement ia64 dump_execution_state()02e,
ip=0x000000006011dc10
(XEN) m(9715): unaligned access to 0x20000000200a0036,
ip=0x000000006011dc10
(XEN) ****************************************ddf7816,
ip=0x000000006011dc10
(XEN) Panic on CPU 4:ned access to 0x200000001ddf781e,
ip=0x000000006011dc10
(XEN) Xen BUG at event_channel.c:912x200000001ddf7826,
ip=0x000000006011dc10
(XEN) ****************************************ddf782e,
ip=0x000000006011dc10
(XEN) m(9715): unaligned access to 0x200000001ddf7836,
ip=0x000000006011dc10
(XEN) Reboot in five seconds...
Even before destroy VTI domain, Qemu report a lot of
unaligned access:
qemu-dm(9715): unaligned access to 0x2000000020a9c82e,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x2000000020a9c836,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x200000001d7bd016,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x200000001d7bd01e,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x200000001d7bd026,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x200000001d7bd02e,
ip=0x000000006011dc10
qemu-dm(9715): unaligned access to 0x200000001d7bd036,
ip=0x000000006011dc10
Best Regards,