On Fri, 2012-02-10 at 19:58 +0100, Peter Zijlstra wrote: > OK, so a 'modern' kernel does it slightly different and I've no idea > what exactly goes wrong in your vintage version. But I can see the > current stuff going at it all wrong. > > What seems to happen is that native_nmi_stop_other_cpus() NMI broadcasts > for smp_stop_nmi_callback()->stop_this_cpu(). Which without any > serialization what so ever marks all remote CPUs offline and calls halt > with IRQs disabled -> dead. > > While we're waiting for this all to complete, the scheduler tries to > no_hz load-balance and kick a cpu it thinks is still around and we get > the above splat because the NMI just marked it offline without telling > anybody about it. > > Now, arguably you don't want to go through the whole hotplug crap to > shut down your machine, esp not on panic, but clearing the online state > without telling anybody about it is bound to lead to these things. > > No immediate solution comes to mind... Don, any reason you wait for the NMI broadcast to complete with IRQs enabled? If you disable IRQs before the broadcast the interrupt can't happen and should side-step this particular problem. Its not like we have 'latency' issues on this path :-) -- 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
