[Suspend2-devel] 2.2.7.4

[Jim Crilly]

On 07/25/06 08:56:15AM +0200, Matthias Hensler wrote:
> On Tue, Jul 25, 2006 at 08:34:21AM +1000, Nigel Cunningham wrote:
> > On Monday 24 July 2006 22:31, Matthias Hensler wrote:
> > > > echo > /sys/power/suspend2/do_resume
> > >
> > > It should be: echo 1 > /sys/power/suspend2/do_resume
> > >
> > > The new sysfs-interface seems to ignore an empty echo into
> > > do_resume.
> > 
> > Hmm. I didn't think it did. I'll double check.
> 
> At least something is different, either with sysfs, or 2.2.7.4.
> 
> I am perfectly able to reproduce this:
> 
> [...]
> echo Trying to resume from target specified as resume2 on cmdline.
> echo > /sys/power/suspend2/do_resume
> sleep 10
> echo second try
> echo 1 > /sys/power/suspend2/do_resume
> sleep 10
> [...]
> 
> The first (empty) echo does not do anything, there is no message from
> Suspend or the kernel. 10 seconds later with the "1" echoed, resume fires
> right ahead.
> 
> However, it could be some strange behaviour of the nash, I have to check
> this. Still, it worked that way up to 2.6.17.4/2.2.7.3 when echoing to
> /proc/.
> 

Without having anymore information I would point at nash as well. I'm
currently using 2.6.18-rc2 patched with suspend2 2.2.7.4 and my initramfs
uses dash and it works fine with the resume portion looking like:

if [ "$noresume" != "yes" ]
then
                echo -n "/usr/sbin/suspend2ui_text" > /sys/power/suspend2/user_interface/program
                echo > /sys/power/suspend2/do_resume
fi

Jim.