Re: Software suspend support in Fedora.

[Nigel Cunningham <ncunningham@cyclades.com>]

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

Hi.

On Mon, 2005-08-15 at 22:20, Pavel Machek wrote:
> Hi!
> 
> Actually, more responses to the fedora discussion:
> 
> No, swsusp can not yet resume from swap file. It would need to mount
> the filesystem, first, and as you know that is not good idea. (Even
> read-only mount replays journal on ext3, beware).

Pavel, could you please stop saying that? What it really needs is to
record the devices and blocks to read from in the image header. Suspend2
has done this for ages and it does work, as you know.

> SMP support is way more experimental than UP support. It uses cpu
> hotplug infrastructure, etc...

It works fine. Hotplug cpu was a little flakey for a while, but it's up
to standard now. I've recently switched from the old method after giving
it good testing, and the only problems I've seen have been in
combination with dynticks, and there the fault was dynticks, not
hotplug.

> We have some ppc support, but it was not officially blessed by BenH,
> and it it did not get much testing. No chance for ppc/SMP support for
> example.
> 
> [Cc-ing alan cox]
> 
> Suspend should work okay on PATA [what areas do you think it is
> incomplete in?]. Recently, it was made to work on SATA, too
> [experimental, I'd say]. It did not eat data recently due to SATA/PATA
> problems. It is broken on most SCSI drivers (well, probably all of
> them), but it is likely that you'll "just" get a crash in such case.

I'm always bemused when I see reports of problems with SATA. I've been
using it for 18 months with suspending and it's always just worked.
Maybe I just have a good chipset.

Regards,

Nigel

-- 
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.


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