Messages in this thread Patch in this message | | | From | Mandeep Singh Baines <> | Subject | [PATCH 2/2] panic: do not unblank_screen when panic_timeout < 0 | Date | Mon, 20 Jun 2011 16:22:09 -0700 |
| |
Avoid risk (of screen_unblank) and wasted cycles unblanking if you intend to reboot immediately.
Signed-off-by: Mandeep Singh Baines <msb@chromium.org> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Huang Ying <ying.huang@intel.com> Cc: Andi Kleen <ak@linux.intel.com> Cc: Hugh Dickins <hughd@chromium.org> Cc: Olaf Hering <olaf@aepfle.de> Cc: Jesse Barnes <jbarnes@virtuousgeek.org> Cc: Dave Airlie <airlied@gmail.com> --- lib/bust_spinlocks.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lib/bust_spinlocks.c b/lib/bust_spinlocks.c index 9681d54..6a5c7e0 100644 --- a/lib/bust_spinlocks.c +++ b/lib/bust_spinlocks.c @@ -21,7 +21,8 @@ void __attribute__((weak)) bust_spinlocks(int yes) ++oops_in_progress; } else { #ifdef CONFIG_VT - unblank_screen(); + if (panic_timeout >= 0) + unblank_screen(); #endif console_unblank(); if (--oops_in_progress == 0) -- 1.7.3.1
| |