Skip to contentSkip to conversation

Announce: Software Suspend Core Patch 2.0 rc4.

PREVIEW Nigel Cunningham 4 participants 6 messages Jan 16, 2004 – Jan 18, 2004

lore
Share & tools
lore
#0 lore raw

Hi all.

Release candidate 4 is ready for you to test and now being uploaded to Sourceforge. It should be used with the following updated version specific patches, which are also now available:

- 2.4.21 revision 1
- 2.4.22 revision 1
- 2.4.23 revision 5.
- 2.4.24
- 2.6.1 revision 1

Changes since rc3A:

- Fixed issues with preemption resulting in 'bad: scheduling while
atomic' messages in 2.6.
- Lots of cleanups and new documentation in the code.
- Fixed broken automatic swapon/off support. Now also used in debug_info proc entry.
- Preliminary SMP support for 2.4. 2.6 support is coming.
- LZF compression (thanks to Marc Lehmann) and readahead support.
Suspend and resume in half the time!
- Fixed long standing oops when aborting during writing the image
header. Thanks to Bernard Blackham. (I would have done it eventually!)
- Serial port power management support (Thanks Michael Frank). MTRR support converted to PM support.
- Many other small fixes and improvements.

Further documentation is to be added and one minor quirk addressed, but codewise, I'm wondering if this might be 2.0 by another name.

Nigel

Signature · 2 lines
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
#1 lore raw

Hi again.

Of course [PREVIEW] wasn't supposed to be in the subject line any more :> The patches are all uploaded to Sourceforge now and in their proper places.

Regards,

Nigel

Signature · 2 lines
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
#2 lore raw
In reply to Nigel Cunningham
Quoted 2 lines · Nigel Cunningham

- Fixed issues with preemption resulting in 'bad: scheduling while atomic' messages in 2.6.

Just gave it a shot. It works like a charm. :>

Quoted 2 lines

Further documentation is to be added and one minor quirk addressed, but codewise, I'm wondering if this might be 2.0 by another name.

Looks really good, congrats, Nigel and everyone else.

regards,

sebas

- - - - - -

Magic is always the best solution, especially reliable magic.

#3 lore raw
In reply to Nigel Cunningham

including urls might be nice.

also the feature comparison webpage
does not mention bios at all.
Till now I used SOFTWARE_SUSPEND because it works fine, whereas PM_DISK somehow uses the bios, and does not work (dell latitude c600, I don't have that magic partition the dell bios expects).

SWSUSP2 will be like SWSUSP concerning this issue?

regards, Andreas

#4 lore raw

Hi.

Quoted 4 lines · Andreas Jellinghaus

including urls might be nice.

also the feature comparison webpage
does not mention bios at all.

True. Feel free to produce a column; I don't have any experience with BIOS support for suspending, so don't know what it can/can't do and whether this varies from computer to computer.

Quoted 7 lines

Till now I used SOFTWARE_SUSPEND because it works fine, whereas PM_DISK somehow uses the bios, and does not work (dell latitude c600, I don't have that magic partition the dell bios expects).

SWSUSP2 will be like SWSUSP concerning this issue?

I'm not sure that PM_DISK does use the bios. In fact, I'm pretty sure it doesn't. Feel free to prove me wrong.

Regarding the relationship with SOFTWARE_SUSPEND, the answer is yes. Software Suspend 2 works in a very similar way to Software Suspend.

Nigel

Signature · 2 lines
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
#5 lore raw
In reply to Andreas Jellinghaus

Hi!

Quoted 7 lines

including urls might be nice.

also the feature comparison webpage
does not mention bios at all.
Till now I used SOFTWARE_SUSPEND because it works fine, whereas PM_DISK somehow uses the bios, and does not work (dell latitude c600,

Its simple bug somewhere in PM_DISK code... it should not use the bios...

Quoted 1 line

SWSUSP2 will be like SWSUSP concerning this issue?

Yes.

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]