From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Karol Kozimor <sziwan@hell.org.pl>
Cc: swsusp-devel <swsusp-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Announce: Software Suspend 2.0rc3 for 2.4 and 2.6.
Date: Fri, 12 Dec 2003 10:07:36 +1300 [thread overview]
Message-ID: <1071176855.2157.1.camel@laptop-linux> (raw)
In-Reply-To: <20031211201444.GA18122@hell.org.pl>
My fault for using Bootsplash too much :> When it's stopping on
'Freezing processes' during resume that's because as well as freezing
the processes, it's copying the original kernel back. I'll make it
display the correct message.
Regards,
Nigel
On Fri, 2003-12-12 at 09:14, Karol Kozimor wrote:
> Thus wrote Nigel Cunningham:
> > This is to announce 2.0-rc3, now being uploaded to swsusp.sf.net.
>
> Hi,
> I've just tested it on 2.4.23 as well -- no problems found, although the
> XFS option patch needs updating -- probably as much as the 2.6 XFS code
> (though the latter seems to suspend... I'll get to it later today).
> Attached is the patch to bring the XFS code for 2.4 up to date (note: this
> is not the whole xfs-option, it should be applied on top of the latter; I
> can prepare a complete xfs-option if you care).
>
> Oh, BTW: the slowdown I mentioned for 2.6 seems to hit this version also,
> but in a different manner: I/O is fine, but the resuming kernel spends some
> time on displaying "Freezing processes" -- what was unnoticeable under rc2
> is somewhat awkward with rc3.
>
> Best regards,
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
prev parent reply other threads:[~2003-12-11 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 4:22 Announce: Software Suspend 2.0rc3 for 2.4 and 2.6 Nigel Cunningham
2003-12-11 20:14 ` [Swsusp-devel] " Karol Kozimor
2003-12-11 21:07 ` Nigel Cunningham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1071176855.2157.1.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=sziwan@hell.org.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox