>>> On 07.11.17 at 09:23, <xudong....@intel.com> wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: Tuesday, November 7, 2017 4:09 PM >> >>> On 07.11.17 at 02:37, <xudong....@intel.com> wrote: >> >> From: Jan Beulich [mailto:jbeul...@suse.com] >> >> Sent: Monday, November 6, 2017 5:17 PM >> >> >>> On 03.11.17 at 09:29, <xudong....@intel.com> wrote: >> >> > We figured out the problem, some corner scripts triggered the error >> >> > injection at the same page (pfn 0x180020) twice, i.e. "./xen-mceinj >> >> > -t 0" run over one time, which resulted in Dom0 crash. >> >> >> >> But isn't this a valid scenario, which shouldn't result in a kernel crash? >> > What if >> >> two successive #MCs occurred for the same page? >> >> I.e. ... >> >> >> > >> > Yes, it's another valid scenario, the expect result is kernel crash. >> >> Kernel _crash_ or rather kernel _panic_? Of course without any kernel >> messages >> we can't tell one from the other, but to me this makes a difference >> nevertheless. >> > Exactly, Dom0 crash.
I don't believe a crash is the expected outcome here. > And I didn't see any "kernel panic" message from the log -- attach the > original log again. Well, as said - there _no_ kernel log message at all, and hence we can't tell whether it's a crash or a plain panic. Iirc Xen's "Hardware Dom0 crashed" can't distinguish the two cases. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
