* Serial console not working after waking up from sleep @ 2010-06-16 3:21 Han Wang 2010-06-16 6:09 ` Michael Trimarchi 0 siblings, 1 reply; 8+ messages in thread From: Han Wang @ 2010-06-16 3:21 UTC (permalink / raw) To: linux-omap 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...) Thanks, -- Han Wang -- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 3:21 Serial console not working after waking up from sleep Han Wang @ 2010-06-16 6:09 ` Michael Trimarchi 2010-06-16 8:43 ` Jean Pihet 2010-06-16 14:40 ` Han Wang 0 siblings, 2 replies; 8+ messages in thread From: Michael Trimarchi @ 2010-06-16 6:09 UTC (permalink / raw) To: Han Wang; +Cc: linux-omap 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 6:09 ` Michael Trimarchi @ 2010-06-16 8:43 ` Jean Pihet 2010-06-16 14:37 ` Han Wang 2010-06-16 14:40 ` Han Wang 1 sibling, 1 reply; 8+ messages in thread From: Jean Pihet @ 2010-06-16 8:43 UTC (permalink / raw) To: Michael Trimarchi; +Cc: Han Wang, linux-omap Hi, On Wed, Jun 16, 2010 at 08:09, Michael Trimarchi <michael@panicking.kicks-ass.org> wrote: > 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, Did you look at http://elinux.org/OMAP_Power_Management? There is some info on the current problems with the UART and sleep modes, as well a workaround for UART wake-up. Regards, Jean > > -- > 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 > -- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 8:43 ` Jean Pihet @ 2010-06-16 14:37 ` Han Wang 0 siblings, 0 replies; 8+ messages in thread From: Han Wang @ 2010-06-16 14:37 UTC (permalink / raw) To: Jean Pihet; +Cc: Michael Trimarchi, linux-omap Hi, Jean, Yes I looked at the the OMAP_Power_management page, but the known problem section doesn't seem to describe my problem. What I am encountering is that the serial console does output correctly after resume, but everything goes south after a few lines, thus, the garbage strings... any ideas？ Han On Wed, Jun 16, 2010 at 4:43 AM, Jean Pihet <jpihet@mvista.com> wrote: > Hi, > > On Wed, Jun 16, 2010 at 08:09, Michael Trimarchi > <michael@panicking.kicks-ass.org> wrote: >> 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, > > Did you look at http://elinux.org/OMAP_Power_Management? There is some > info on the current problems with the UART and sleep modes, as well a > workaround for UART wake-up. > > Regards, > Jean > > >> >> -- >> 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 >> > -- Han Wang Electrical and Computer Engineering Cornell University M: 1-607-280-4995 -- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 6:09 ` Michael Trimarchi 2010-06-16 8:43 ` Jean Pihet @ 2010-06-16 14:40 ` Han Wang 2010-06-16 14:47 ` Michael Trimarchi 1 sibling, 1 reply; 8+ messages in thread From: Han Wang @ 2010-06-16 14:40 UTC (permalink / raw) To: Michael Trimarchi; +Cc: linux-omap Hi, michael, I have the no_console_suspend option in my boot command line, I am not sure if that is the option you were trying to point me to in the last email? anyway, I added no_debug_console into my boot command arg, but that doesn't seem to help with my problem. any ideas? Thanks, Han On Wed, Jun 16, 2010 at 2:09 AM, Michael Trimarchi <michael@panicking.kicks-ass.org> wrote: > 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, > > -- Han Wang Electrical and Computer Engineering Cornell University M: 1-607-280-4995 -- 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 14:40 ` Han Wang @ 2010-06-16 14:47 ` Michael Trimarchi 2010-06-16 20:53 ` Sapiens, Rene 0 siblings, 1 reply; 8+ messages in thread From: Michael Trimarchi @ 2010-06-16 14:47 UTC (permalink / raw) To: Han Wang; +Cc: linux-omap Hi Han Wang wrote: > Hi, michael, > > I have the no_console_suspend option in my boot command line, I am > not sure if that is the option you were trying to point me to in the > last email? I have said that i have no problem when I remove that option. Can you try to echo 0 to timeout of the serial device? Michael > > anyway, I added no_debug_console into my boot command arg, but that > doesn't seem to help with my problem. > > any ideas? > > Thanks, > Han > On Wed, Jun 16, 2010 at 2:09 AM, Michael Trimarchi > <michael@panicking.kicks-ass.org> wrote: >> 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: Serial console not working after waking up from sleep 2010-06-16 14:47 ` Michael Trimarchi @ 2010-06-16 20:53 ` Sapiens, Rene 2010-07-22 21:09 ` Tyler 0 siblings, 1 reply; 8+ messages in thread From: Sapiens, Rene @ 2010-06-16 20:53 UTC (permalink / raw) To: Michael Trimarchi, Han Wang; +Cc: linux-omap@vger.kernel.org You can do a telnet to the device... you should be able to work with it but your serial session will show the garbage. Regards, Rene > -----Original Message----- > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap- > owner@vger.kernel.org] On Behalf Of Michael Trimarchi > Sent: Wednesday, June 16, 2010 9:47 AM > To: Han Wang > Cc: linux-omap@vger.kernel.org > Subject: Re: Serial console not working after waking up from sleep > > Hi > > Han Wang wrote: > > Hi, michael, > > > > I have the no_console_suspend option in my boot command line, I am > > not sure if that is the option you were trying to point me to in the > > last email? > > I have said that i have no problem when I remove that option. > Can you try to echo 0 to timeout of the serial device? > > Michael > > > > > anyway, I added no_debug_console into my boot command arg, but that > > doesn't seem to help with my problem. > > > > any ideas? > > > > Thanks, > > Han > > On Wed, Jun 16, 2010 at 2:09 AM, Michael Trimarchi > > <michael@panicking.kicks-ass.org> wrote: > >> 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 ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Serial console not working after waking up from sleep 2010-06-16 20:53 ` Sapiens, Rene @ 2010-07-22 21:09 ` Tyler 0 siblings, 0 replies; 8+ messages in thread From: Tyler @ 2010-07-22 21:09 UTC (permalink / raw) To: linux-omap Sapiens, Rene <rene.sapiens <at> ti.com> writes: > > You can do a telnet to the device... you should be able to work with it but your serial session will show the garbage. > > Regards, > Rene > Hello, I am in essentially the same position, but currently working off of the pm-head branch. I am just using an initramfs, and have tried a few variations. With no_console_suspend set, I can trigger a wakeup using the wakeup_timer_seconds. The power usage goes back to the pre-suspend level, and I see text indicating a successful wakeup, but the console never comes back. Without no_console_suspend set, I can trigger the wakeup again with wakeup_timer_seconds, a console prompt comes back, but is unresponsive. I saw Rene's response about using Telnet, but this implies that there is an ethernet interface available. I have a custom board that only has a serial interface for external visibility, so at this point I lose insight into what is happening on the board. I have two questions, if people would be so willing to oblige: 1) Does anyone know why the console doesn't come back after wakeup? Is this something that may work in the future? 2) Does the console freezing mean that the other COM ports also don't work? Would communication on other interfaces continue to work? For example, a GPS plugged into one of the other COM ports? Thanks, Tyler ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2010-07-22 21:15 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2010-06-16 3:21 Serial console not working after waking up from sleep Han Wang 2010-06-16 6:09 ` Michael Trimarchi 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox