On Wed, Dec 23, 2009 at 1:06 PM, Robert Nelson <[email protected]> wrote: > On Wed, Dec 23, 2009 at 2:59 PM, Steve Sakoman <[email protected]> wrote: >> I'm seeing some strange behavior with my console serial port with 2.6.32. >> >> Output seems fine -- no errors in the boot messages. >> >> However it seems that quite often the first character typed in a >> console session is garbled -- subsequent characters are OK: >> >> r...@omap3:~# �s -l >> -sh: �s: not found >> >> If commands are typed in rapid succession this issue doesn't show up, >> but if several seconds pass since the last keystroke the first >> character is garbled once again. >> >> Anyone else seeing this? A search of this list didn't turn anything >> up, but perhaps my google mojo is just bad today. >> >> Steve > > Hey Steve, > > I saw something similar while testing 2.6.32, by chance are you using > any power management patches? > > I had to disable CONFIG_CPU_IDLE: > > -CONFIG_CPU_IDLE=y > -CONFIG_CPU_IDLE_GOV_LADDER=y > -CONFIG_CPU_IDLE_GOV_MENU=y > +# CONFIG_CPU_IDLE is not set
Now power management patches, but CPU_IDLE is indeed enabled. I'll give it a try with CPU_IDLE disabled. Does this just work around a bug that ought to be fixed, or is enabling CPU_IDLE just a bad idea? Steve -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
