omap-pm: no_console_suspend breaks resume

[Cliff Brake <cliff.brake@gmail.com>]

I've been experiementing with the omap-pm branch on a overo.  The
no_console_suspend seems to cause the system to not suspend/resume
properly.  Without the option:

root@ts3:~# echo mem > /sys/power/state
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
PM: suspend of devices complete after 109.710 msecs
PM: late suspend of devices complete after 0.305 msecs
Wake up daisy chain activation failed.
Successfully put all powerdomains to target state
PM: early resume of devices complete after 0.061 msecs
PM: resume of devices complete after 304.229 msecs
Restarting tasks ... done.
root@ts3:~#


With the option:
root@ts3:~# echo mem > /sys/power/state
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: suspend of devices complete after 106.811 msecs
PM: late suspend of devices complete after 0.305 msecs
(the current is quite high at this point, so I don't think we ever got
into suspend)

is no_console_suspend working for other people?

Thanks,
Cliff