Software suspend support in Fedora.

[Dave Jones <davej@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

On Wed, Aug 03, 2005 at 11:23:01AM +0200, Pavel Machek wrote:

 > > The outcome: I'm no more enthusiastic about enabling this in Red Hat
 > > kernels than I ever was before.  It seems to have real issues with LVM
 > > setups (which is default on Red Hat/Fedora installs these days).
 > > After convincing it where to suspend/resume from by feeding it
 > > the major/minor of my swap partition, it did actually seem
 > > to suspend. And resume (though it did spew lots of 'sleeping whilst
 > > atomic warnings, but thats trivial compared to whats coming up
 > > next).
 > 
 > I do not know much about LVM. How exactly did you resume= command line
 > look like? You were not resuming from initrd, right?

Indeed, this was very likely the problem. Doing a resume if I had
any partition mounted was *bad* news.  We implemented the necessary
bits in our initrd today to detect resume partitions, and erm.. resume them.
So far so good, no repeats of the corruption I saw.

As of tomorrow rawhide kernels (for the unenlightened: these will
eventually be FC5) will have software suspend support.

Our initial experiments with it have been fairly positive, though as
expected there are a number of drivers that don't survive the resume
correctly. http://www.livejournal.com/users/kernelslacker/22975.html
has more info on this.  As we start getting users jumping on this, I
imagine more of these bugs will appear. But without testing, these are
never going to get fixed eh ? :)

 > Could you try to suspend on plain old swap-partition, first, to verify
 > that your drivers cooperate?
 
So, we've tested in on a /dev/hdaX, /dev/sdaX, and /dev/mapper/VolGroup00-LogVol01
so far, and its done the right thing every time.

It's looking pretty good, and unless something catastrophic happens,
we'll be supporting this feature from now on.
Whilst it's likely still got some niggles that need working out, 
It's come a long way since I last spent time looking into this, and
I'm sure it'll get there.  Kudos to all involved.

		Dave


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]