All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Brabec <sbrabec@suse.cz>
To: Jason Wang <jason77.wang@gmail.com>
Cc: gregkh@suse.de, alan@linux.intel.com, arnd@arndb.de,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] two serial_core suspend/resume fixes
Date: Mon, 23 Aug 2010 22:06:15 +0200	[thread overview]
Message-ID: <1282593975.3526.9.camel@utx.lan> (raw)
In-Reply-To: <1282374882-6651-1-git-send-email-jason77.wang@gmail.com>

Jason Wang wrote:
> Sorry for resending this thread. Last thread is forgot to CC
> Greg Kroah-Hartman.

Well, I experienced no_console_supend breakage on my PXA270 based Zaurus
SL-C3200 (terrier/spitz) as well.

But your patches did not fix the behavior, serial port remains dead
after resume with no_console_supend.

> 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.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
Lihovarská 1060/12                            tel: +420 284 028 966
190 00 Praha 9                                fax: +420 284 028 951
Czech Republic                                http://www.suse.cz/

--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-08-23 20:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21  7:14 [PATCH RESEND 0/2] two serial_core suspend/resume fixes Jason Wang
2010-08-21  7:14 ` [PATCH RESEND 1/2] serial-core: skip call set_termios/console_start when no_console_suspend Jason Wang
2010-08-21  7:14   ` [PATCH RESEND 2/2] serial-core: restore termios settings when resume console ports Jason Wang
2010-08-23 20:06 ` Stanislav Brabec [this message]
     [not found]   ` <AANLkTikZgAMvODoFB9O9Mrb98f_xMatQfkb+2dgcrGJn@mail.gmail.com>
2010-08-24  9:01     ` [PATCH RESEND 0/2] two serial_core suspend/resume fixes Stanislav Brabec
2010-08-25  3:29       ` wanghui
2010-08-25 10:51         ` Stanislav Brabec
2010-08-25 20:00           ` Stanislav Brabec
2010-08-26  8:50             ` Jason Wang
2010-08-29 22:17               ` Stanislav Brabec
2010-08-30  5:59                 ` Jason Wang
2010-08-26  8:36           ` Jason Wang
2010-08-26 10:55             ` Stanislav Brabec

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1282593975.3526.9.camel@utx.lan \
    --to=sbrabec@suse.cz \
    --cc=alan@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@suse.de \
    --cc=jason77.wang@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.