"Brandeburg, Jesse" <jesse.brandeburg@intel.com> writes:
Hi Jesse,
Were you able to reproduce it?
it looks like two bugs: oprofile didn't catch a NMI that belongs to
it (most likely) and the NMI watchdog referenced a NULL pointer
while processing an NMI.
Did you have the nmi watchdog enabled on the command line?
I don't get the same code as you. But the oopsing instruction in your
oops is
2b:* 44 0f a3 28 bt %r13d,(%rax) <-- trapping instruction
with rax == 0 and I suspect it's one of the new cpu mask checks
I would try reverting
fcc5c4a2feea3886dc058498b28508b2731720d5
2f537a9f8e82f55c241b002c8cfbf34303b45ada
fcef8576d8a64fc603e719c97d423f9f6d4e0e8b
and see which one causes it. That would only fix the NMI watchdog bug
of course.
The oprofile not catching a event problem would be still open then.
I think the checks for overflowed counters are not 100% perfect
so that could happen. I have some patches in the works to use the new
global status register on arch perfmon 2, with that the overflow
check is somewhat more reliable. But that's more work.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
