I've reported this issue earlier this month, unfortunately I have no clue what is happening. When you telnet (or ssh) to the board via Ethernet-LAN you can see that the board is suspending and resuming. Output to the serial console works fine. If you do: > echo Hello > /dev/console from the ssh/telnet session, you'll see the message being printed to the serial console. Also, if you have configured the serial console as a wakeup source: > echo enabled > /sys/devices/platform/serial8250.2/tty/ttyS2/wakeup then sending a character over the (USB) console link does resume the Overo. Any character send over the (USB) console link *after* the Overo has resumed will lock up the system in one of two ways: 1) immediate The system is locked completely, and the parallel telnet/ssh session cannot make any progress 2) gradual failure The system becomes sluggish, especially noticable in the parallel telnet/ssh session that makes progress but only slowly. That situation gets worse progressively until there is no noticable progress anymore. The fact that the serial console does produce output should be proof that there is no problem with the UART clocks. In case (2), 'top' running in the parallel telnet/ssh session shows virtually no system load, so the lockup/worsening performance seem to have a kernel origin. I haven't found an effective way to debug this on the Overo. Cheers, Robert > -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Kevin Hilman > Sent: Monday, June 21, 2010 7:41 PM > To: Peter Tseng > Cc: linux-omap@xxxxxxxxxxxxxxx; Han Wang > Subject: Re: Overo serial problems after resume, vs. Beagleboard > > 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. > > Kevin > -- > 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 > -- 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
