Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751280AbbLUGb4 (ORCPT ); Mon, 21 Dec 2015 01:31:56 -0500 Received: from hqemgate15.nvidia.com ([216.228.121.64]:16050 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751123AbbLUGbq (ORCPT ); Mon, 21 Dec 2015 01:31:46 -0500 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Sun, 20 Dec 2015 22:28:05 -0800 From: Bibek Basu To: rjw@rjwysocki.net, len.brown@intel.com, pavel@ucw.cz CC: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, bbasu@nvidia.com Subject: [PATCH] PM / sleep: console flush during suspend if no_console_suspend enabled Date: Mon, 21 Dec 2015 12:01:40 +0530 Message-ID: <1450679500-6185-1-git-send-email-bbasu@nvidia.com> X-Mailer: git-send-email 2.1.4 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1270 Lines: 40 On multicore CPUs, sometimes debug console logs are not flushed if you have VT consoles also enabled. Reason being console_lock is taken by secondary/nonboot cpus which are disabled as part of suspend.This patch flushes the console before disabling nonboot cpus Signed-off-by: Bibek Basu --- kernel/power/suspend.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c index f9fe133..42c5912 100644 --- a/kernel/power/suspend.c +++ b/kernel/power/suspend.c @@ -352,6 +352,16 @@ static int suspend_enter(suspend_state_t state, bool *wakeup) goto Platform_wake; } + /* + * Flush console buffer if console_suspend_enabled cleared. + * This will enable console flush if console_lock is taken + * by nonboot cpus which will soon be disabled below. + */ + if (!console_suspend_enabled) { + console_lock(); + console_unlock(); + } + error = disable_nonboot_cpus(); if (error || suspend_test(TEST_CPUS)) goto Enable_cpus; -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/