On Wed, Dec 14, 2011 at 08:17:45AM -0600, Nate Custer wrote: > > On Dec 14, 2011, at 8:06 AM, Marcelo Tosatti wrote: > > I don't know. Its a hang ? It could be memory corruption (of the timer > > olist) instead of a bogus NMI actually, the second. > > > What is pasted in the second paste is what came scrolling across the console right before the end of all responsiveness. It came from a dmesg dump, the next dmesg command was not accepted via ssh and the console attached showed the same stack trace. At that point the system refused to respond to any direct keyboard input, including the SysRq commands that I expected to work after a core dump. > > The issue happened with two servers (same hardware, same build group so there is a chance of a bad hardware batch). Switching to an older kernel/kvm setup in RHEL 6.2 has corrected the issue, which suggests a software issue to me. Right. Perhaps try an older upstream kernel to find a culprit then. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
