From: brian@worldcontrol.com
To: Pavel Machek <pavel@ucw.cz>
Cc: alan@redhat.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Make swsusp actually work
Date: Mon, 8 Apr 2002 14:15:59 -0700 [thread overview]
Message-ID: <20020408211558.GA1864@top.worldcontrol.com> (raw)
In-Reply-To: <20020407233725.GA15559@elf.ucw.cz>
On Mon, Apr 08, 2002 at 01:37:26AM +0200, Pavel Machek wrote:
> Hi!
>
> There were two bugs, and linux/mm.h one took me *very* long to
> find... Well, those bits used for zone should have been marked. Plus I
> hack ide_..._suspend code not to panic, and it now seems to
> work. [Sorry, 2pm, have to get some sleep.]
I've applied both this patch and the earlier one, and now my
2.4.19-pre5-ac3 system can suspend and it can resume. However,
when it resumed, I was stuck in the kernel SysRq function.
Couldn't get out of it.
And nothing seemed to work, other than it kept displaying the
help each time I touched a key.
On the other hand, the swsusp in 2.4.18-WOLK3.3 works correctly.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
next prev parent reply other threads:[~2002-04-08 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-07 23:37 Make swsusp actually work Pavel Machek
2002-04-08 7:47 ` Make swsusp actually work better brian
2002-04-08 10:12 ` Pavel Machek
2002-04-08 17:43 ` Eric W. Biederman
2002-04-08 8:25 ` Make swsusp actually work Ed Sweetman
2002-04-08 10:25 ` Pavel Machek
2002-04-08 14:21 ` Ed Sweetman
2002-04-08 15:00 ` Pavel Machek
2002-04-08 15:18 ` Ed Sweetman
2002-04-08 20:51 ` Pavel Machek
2002-04-08 20:53 ` Pavel Machek
2002-04-08 21:15 ` brian [this message]
2002-04-08 21:27 ` Ed Sweetman
2002-04-08 21:32 ` Pavel Machek
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=20020408211558.GA1864@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.