> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Mike Rapoport > Sent: Tuesday, June 22, 2010 10:56 AM > To: Kevin Hilman > Cc: Peter Tseng; linux-omap@xxxxxxxxxxxxxxx; Han Wang > Subject: Re: Overo serial problems after resume, vs. Beagleboard > > Kevin Hilman wrote: > > Peter Tseng <tsenpet09@xxxxxxxxx> writes: > > > >> I am seeing some discrepancies between the Overo (I > believe I have a > >> Water) and the Beagleboard (I have a Rev. B5) when > resuming after a > >> suspend to RAM. > > > > Not that it is much comfort, but I have the same problem on > Overo but > > don't see it on any other OMAP3 board. > > > > I have yet to debug this particular issue further. > > I had the same issue on CM-T35 and when I've disabled > CONFIG_CPU_IDLE in the kernel configuration the issue > disappeared. Maybe it'll be of some help. I just tried that. It helps. I no longer experience this lockup of the console. Thanks. I'll make a note to try to figure out why this actually helps. Regards, Robert -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
