With 3.7, hyperv guest shutdown no longer works. Instead, guest kernel throws a bunch of "BUG: scheduling-while-atomic" errors and then dies.
reverting commit 6c0c0d4d1080840eabb3d055d2fd81911111c5fd Author: hongfeng <hongf...@marvell.com> Date: Thu Oct 4 17:12:25 2012 -0700 poweroff: fix bug in orderly_poweroff() fixes this problem. Greping for users of orderly_poweroff() shows that hyperv isn't the only caller that invokes the function from irq context. In fact, kdoc for orderly_poweroff says: * This may be called from any context to trigger a system shutdown. * If the orderly shutdown fails, it will force an immediate shutdown. Any suggestions on how to properly fix this? Thanks, Florian -- 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/