On Thu, Nov 13, 2014 at 5:20 PM, Luck, Tony <tony.l...@intel.com> wrote: > "worst == > MCE_AR_SEVERITY but regs->cs == 0 (i.e. in kernel)" > > This can't happen. We can only declare AR severity for a user mode fault.
I believe you, and I see that in the code, but the code is mightily twisted. Anyway, my v3 will also catch a failure in which my asm fails to switch to the right stack for some other reason. Without the scheduling in the idle thread warning, I'd believe that the problem is that some cpu is going out to lunch or failing to receive the #MC, which would make me want to consider IRET issues (w/ my patch, there might not be an IRET until after memory_failure, and maybe it sometimes takes a really long time). But I don't see why that would cause a scheduling in the idle thread warning. > > Sent from my iPhone > >> On Nov 13, 2014, at 16:50, Andy Lutomirski <l...@amacapital.net> wrote: >> >> worst == >> MCE_AR_SEVERITY but regs->cs == 0 (i.e. in kernel) -- Andy Lutomirski AMA Capital Management, LLC -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/