Suspend problem on 2.6.x

Suspend problem on 2.6.x

[Ben Dooks]

mtdblockd when running on 2.6 is either ignorning or
not dealing with the suspend-to-memory request, and therefore
the system is not shutting down when asked to.

bash-2.05a# echo mem > /sys/power/state
Stopping tasks: ==
 stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, mtdblockd not stopped
 done
bash-2.05a#

I have worked round this for the moment by
adding PF_NOFREEZE to the current->flags at the start of 
mtd_bldevs.c:mtd_blktrans_thread()

-- 
Ben (ben@fluff.org, http://www.fluff.org/)

  'a smiley only costs 4 bytes'

Re: Suspend problem on 2.6.x

[Todd Poynor]

Ben Dooks wrote:
> mtdblockd when running on 2.6 is either ignorning or
> not dealing with the suspend-to-memory request, and therefore
> the system is not shutting down when asked to.
> 
> bash-2.05a# echo mem > /sys/power/state
> Stopping tasks: ==
>  stopping tasks failed (1 tasks remaining)
> Restarting tasks...<6> Strange, mtdblockd not stopped
>  done
> bash-2.05a#
> 
> I have worked round this for the moment by
> adding PF_NOFREEZE to the current->flags at the start of 
> mtd_bldevs.c:mtd_blktrans_thread()

Right, this same fix was committed to infradead cvs a few weeks ago.  It 
is the freeze execution signal that is being ignored (the thread does 
not enable or poll for such signals).  Since mtdblockd/ftld might need 
to perform I/O to save state during a suspend, and since these probably 
doesn't need to access resources that are impaired during the state save 
phase, exempting these from execution freeze via PF_NOFREEZE seems the 
right solution.

-- 
Todd