On Fri, Feb 26, 2016 at 12:56 AM, Jiri Slaby <jslaby@xxxxxxx> wrote: > > Sure, both vmlinux w/ its separated .debuginfo sections vmlinux.debug > are at: > http://labs.suse.cz/jslaby/bug-968218/ I'm not seeing anything odd there. It does feel like CPU state corruption - either due to a qemu bug, or due to some odd trap/interrupt handling bug of ours. Or possibly a CPU/microcode bug. You wouldn't happen to run this on an AMD Piledriver-based CPU with the 0x06000832 microcode? Because we do have a pending qemu-related bug-report that turned out to be a AMD microcode problem with NMI delivery. Looking at that bug report, it actually looks rather similar - also due to a confused RIP. Linus -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html