Thank you for giving me the feedback. > > So it appears the problem occurs because the other CPUs are not offlined > correctly, and still have pending work which may generate > wakeup IPIs to them?
Right. > > The fix would be to either offline them properly - or, if we don't want to do > that to keep panicking simple, why do we mark them > offline? They aren't really offline in a proper way. To offline cpus properly, it should be done with threads like stop_machine(). But I don't think it is reasonable to kick the threads in panic case. Therefore, I will make a patch keeping cpus online. Also, to inform a panicked cpu that other cpus stopped surely, I will introduce a new cpu_mask like cpu_stopped_mask. Seiji -- 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/
