From: Michael Trimarchi <michael@panicking.kicks-ass.org>
To: Han Wang <hwan122@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Serial console not working after waking up from sleep
Date: Wed, 16 Jun 2010 08:09:27 +0200 [thread overview]
Message-ID: <4C186A97.5040208@panicking.kicks-ass.org> (raw)
In-Reply-To: <AANLkTind1hzgSWIfzNBxjCXPpdPhMYgUkSqYA0WjjYjR@mail.gmail.com>
Han Wang wrote:
> Hi,
>
> I am testing the 2.6.35-rc1 pm branch code on Overo. The system
> boots ok. (I can provide booting log if that is necessary) However,
> when I use "echo mem > /sys/power/state" to send overo to sleep and
> wake it up by enter a key into serial console. I got garbage
> characters in the serial console, and I can not enter anything into
> the console anymore. I wonder if anyone has encountered a similar
> problem, and please give me some suggestion.
>
> I have appended command log below.
>
> root@overo:~# echo mem > /sys/power/state
> PM: Syncing filesystems ... done.
> PM: Preparing system for mem sleep
> PM: Adding info for No Bus:vcs63
> PM: Adding info for No Bus:vcsa63
> Freezing user space processes ... (elapsed 0.02 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
> PM: Entering mem sleep
> i2c_omap i2c_omap.1: preparing suspend
> i2c_omap i2c_omap.3: preparing suspend
> platform overo_lcd: preparing suspend
> serial8250 serial8250.0: preparing suspend, may wakeup
> serial8250 serial8250.1: preparing suspend, may wakeup
> serial8250 serial8250.2: preparing suspend, may wakeup
> platform omap2-nand: preparing suspend
> platform musb_hdrc: preparing suspend
> platform smsc911x.0: preparing suspend
> platform smsc911x.1: preparing suspend
> platform omap2_mcspi.1: preparing suspend
> platform omap2_mcspi.2: preparing suspend
> platform omap2_mcspi.3: preparing suspend
> platform omap2_mcspi.4: preparing suspend
> arm-pmu arm-pmu.0: preparing suspend
> platform omap_rng: preparing suspend
> platform omapfb: preparing suspend
> twl4030_gpio twl4030_gpio: preparing suspend
> mmci-omap-hs mmci-omap-hs.0: preparing suspend
> mmci-omap-hs mmci-omap-hs.1: preparing suspend
> twl_reg twl_reg.17: preparing suspend
> twl_reg twl_reg.18: preparing suspend
> twl_reg twl_reg.19: preparing suspend
> twl4030_usb twl4030_usb: preparing suspend, may wakeup
> twl_reg twl_reg.6: preparing suspend
> serial8250 serial8250: preparing suspend
> mmcblk mmc0:fb2a: legacy suspend
> serial8250 serial8250: suspend
> i2c i2c-3: suspend
> twl_reg twl_reg.6: suspend
> twl4030_usb twl4030_usb: suspend, may wakeup
> twl_reg twl_reg.19: suspend
> twl_reg twl_reg.18: suspend
> twl_reg twl_reg.17: suspend
> mmci-omap-hs mmci-omap-hs.1: suspend
> mmci-omap-hs mmci-omap-hs.0: suspend
> twl4030_gpio twl4030_gpio: suspend
> dummy 1-004b: suspend
> dummy 1-004a: suspend
> dummy 1-0049: suspend
> twl 1-0048: suspend, may wakeup
> i2c i2c-1: suspend
> platform omapfb: suspend
> platform omap_rng: suspend
> arm-pmu arm-pmu.0: suspend
> platform omap2_mcspi.4: suspend
> platform omap2_mcspi.3: suspend
> platform omap2_mcspi.2: suspend
> platform omap2_mcspi.1: suspend
> platform smsc911x.1: suspend
> platform smsc911x.0: suspend
> platform musb_hdrc: suspend
> platform omap2-nand: suspend
> serial8250 serial8250.2: suspend, may wakeup
> serial8250 serial8250.1: suspend, may wakeup
> serial8250 serial8250.0: suspend, may wakeup
> platform overo_lcd: suspend
> i2c_omap i2c_omap.3: suspend
> i2c_omap i2c_omap.1: suspend
> PM: suspend of devices complete after 201.965 msecs
> serial8250 serial8250: LATE suspend
> i2c i2c-3: LATE suspend
> twl_reg twl_reg.6: LATE suspend
> twl4030_usb twl4030_usb: LATE suspend, may wakeup
> twl_reg twl_reg.19: LATE suspend
> twl_reg twl_reg.18: LATE suspend
> twl_reg twl_reg.17: LATE suspend
> mmci-omap-hs mmci-omap-hs.1: LATE suspend
> mmci-omap-hs mmci-omap-hs.0: LATE suspend
> twl4030_gpio twl4030_gpio: LATE suspend
> dummy 1-004b: LATE suspend
> dummy 1-004a: LATE suspend
> dummy 1-0049: LATE suspend
> twl 1-0048: LATE suspend, may wakeup
> i2c i2c-1: LATE suspend
> platform omapfb: LATE suspend
> platform omap_rng: LATE suspend
> arm-pmu arm-pmu.0: LATE suspend
> platform omap2_mcspi.4: LATE suspend
> platform omap2_mcspi.3: LATE suspend
> platform omap2_mcspi.2: LATE suspend
> platform omap2_mcspi.1: LATE suspend
> platform smsc911x.1: LATE suspend
> platform smsc911x.0: LATE suspend
> platform musb_hdrc: LATE suspend
> platform omap2-nand: LATE suspend
> serial8250 serial8250.2: LATE suspend, may wakeup
> serial8250 serial8250.1: LATE suspend, may wakeup
> serial8250 serial8250.0: LATE suspend, may wakeup
> platform overo_lcd: LATE suspend
> i2c_omap i2c_omap.3: LATE suspend
> i2c_omap i2c_omap.1: LATE suspend
> PM: late suspend of devices complete after 103.088 msecs
> Successfully put all powerdomains to target state
> i2c_omap i2c_omap.1: EARLY resume
> i2c_omap i2c_omap.3: EARLY resume
> platform overo_lcd: EARLY resume
> serial8250 serial8250.0: EARLY resume
> serial8250 serial8250.1: EARLY resume
> serial8250 serial8250.2: EARLY resume
> platform omap2-nand: EARLY resume
> platform musb_hdrc: EARLY resume
> platform smsc911x.0: EARLY resume
> platform smsc911x.1: EARLY resume
> platform omap2_mcspi.1: EARLY resume
> platform omap2_mcspi.2: EARLY resume
> platform omap2_mcspi.3: EARLY resume
> platform omap2_mcspi.4: EARLY resume
> arm-pmu arm-pmu.0: EARLY resume
> platform omap_rng: EARLY resume
> platform omapfb: EARLY resume
> i2c i2c-1: EARLY resume
> twl 1-0048: EARLY resume
> dummy 1-0049: EARLY resume
> dummy 1-004a: EARLY resume
> dummy 1-004b: EARLY resume
> twl4030_gpio twl4030_gpio: EARLY resume
> mmci-omap-hs mmci-omap-hs.0: EARLY resume
> mmci-omap-hs mmci-omap-hs.1: EARLY resume
> twl_reg twl_reg.17: EARLY resume
> twl_reg twl_reg.18: EARLY resume
> twl_reg twl_reg.19: EARLY resume
> twl4030_usb twl4030_usb: EARLY resume
> twl_reg twl_reg.6: EARLY resume
> i2c i2c-3: EARLY resume
> serial8250 serial8250: EARLY resume
> PM: early resume of devices complete after 97.625 msecs
> i2c_omap i2c_omap.1: resume
> i2c_omap i2c_omap.3: resume
> platform overo_lcd: resume
> serial8250 serial8250.0: resume
> serial8250 serial8250.1: resume
> serial8250 serial8250.2: resume
> ×uV=V=ý_½hþ¼þ¼.?ýR®HlÒÒ¾»®=¾=½´®¿Q*^¼þQ¾99:¾ÒÒýRN÷õt®¨¨:;;T»?ÉQQ·´Ö´Ë\¿véÝÿ
> (garbage string...)
The problem is releated to no_debug_console option.
Michael Trimarchi
>
> Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-16 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 3:21 Serial console not working after waking up from sleep Han Wang
2010-06-16 6:09 ` Michael Trimarchi [this message]
2010-06-16 8:43 ` Jean Pihet
2010-06-16 14:37 ` Han Wang
2010-06-16 14:40 ` Han Wang
2010-06-16 14:47 ` Michael Trimarchi
2010-06-16 20:53 ` Sapiens, Rene
2010-07-22 21:09 ` Tyler
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=4C186A97.5040208@panicking.kicks-ass.org \
--to=michael@panicking.kicks-ass.org \
--cc=hwan122@gmail.com \
--cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox