printk: Don't take console semaphore in atomic context
The CPU HOTPLUG take_cpu_down path is invokved with preemption disabled via stop_machine. This causes a "Scheduling while atomic" BUG when there is contention for the console semaphore. The solution is to defer the console flush until it's not in scheduling violation. Change-Id: I2d0d58576a4db308ee40850a18a6bb9784ca4e4b Signed-off-by:Michael Bohan <mbohan@codeaurora.org> [mattw@codeaurora.org: adjust for moved location of printk.c] Signed-off-by:
Matt Wagantall <mattw@codeaurora.org>
Loading
Please register or sign in to comment