Re: pm-susend on 2.6.30-rc5

[David Brownell <david-b@pacbell.net>]

On Wednesday 13 May 2009, Luis R. Rodriguez wrote:
> When trying suspend on 2.6.30-rc5 I get the following WARN and also
> cannot use my write to my file system. I cannot even reboot:
> 
> mcgrof@pogo ~ $ sudo reboot
> sudo: unable to execute /sbin/reboot: Success
> mcgrof@pogo ~ $ echo $?
> 127
> 
> Granted, I've never tried to suspend on this box, its a development
> desktop, but still think you'd like to know about it. The actual WARN
> in question is:
> 
>         /* Warning on suspend means the RTC alarm period needs to be
>          * larger -- the system was sooo slooowwww to suspend that the
>          * alarm (should have) fired before the system went to sleep!
>          *
>          * Warning on either suspend or resume also means the system
>          * has some performance issues.  The stack dump of a WARN_ON
>          * is more likely to get the right attention than a printk...
>          */
>         WARN(msec > (TEST_SUSPEND_SECONDS * 1000), "Component: %s\n", label);

None of that was supposed to be executing *except* during
(a) initial boot, when (b) the command line parameter was
set to enable that test during boot ... see test_suspend().

If we can't enter standby/suspend/hibernate then, it's
either a regression or a bug to fix; ergo the warning.

Clearly that's been changed at some point, and this problem
relates to those changes.