From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Wang Subject: [PATCH RESEND 0/2] two serial_core suspend/resume fixes Date: Sat, 21 Aug 2010 15:14:40 +0800 Message-ID: <1282374882-6651-1-git-send-email-jason77.wang@gmail.com> Return-path: Received: from mail.windriver.com ([147.11.1.11]:44775 "EHLO mail.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751211Ab0HUHLU (ORCPT ); Sat, 21 Aug 2010 03:11:20 -0400 Sender: linux-serial-owner@vger.kernel.org List-Id: linux-serial@vger.kernel.org To: gregkh@suse.de, alan@linux.intel.com, arnd@arndb.de, sbrabec@suse.cz Cc: linux-serial@vger.kernel.org Sorry for resending this thread. Last thread is forgot to CC Greg Kroah-Hartman. The [1/2] fix this situation: we set no_console_supend and console=ttyS0 to bootargs, then bootup the kernel, the boot logs will print out from ttyS0. When we execute echo mem > /sys/power/state, the system will suspend, we press a key(or other wakeup trigger) to resume the system, but the ttyS0 can't work anymore. The [2/2] fix this situation: we set console=ttyS0 to bootargs, then bootup the kernel, the boot logs will print out from ttyS0, this time we set ttyS1 as tty and login for shell. When we execute echo mem > /sys/power/state, the system will suspend, we press a key(or other wakeup trigger) to resume the system, but the ttyS0 can't work anymore.