From: Stefan Seyfried <seife@suse.de>
To: ncunningham@cyclades.com
Cc: Russell Miller <rmiller@duskglow.com>,
erik.andren@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>
Subject: Re: Suspend-to-disk woes
Date: Mon, 21 Mar 2005 08:38:07 +0100 [thread overview]
Message-ID: <423E79DF.3030603@suse.de> (raw)
In-Reply-To: <1111364066.9720.2.camel@desktop.cunningham.myip.net.au>
Nigel Cunningham wrote:
> Hi.
>
> On Sun, 2005-03-20 at 08:29, Pavel Machek wrote:
>> boot with "noresume", then mkswap.
>
> Yuck! Why panic when you know what is needed? A better solution is to
Ok, so let's
printk("You booted another kernel than you suspended with.\n");
printk("You have two options now:\n");
printk(" - boot the kernel you suspended with\n");
printk(" - pass 'noresume' at boot and mkswap your swap partition "
" later\n");
printk("Try again, player 1!\n");
panic();
> tell the user they've messed up and give them the option to (1) reboot
> and try another kernel or (2) have swsusp restore the original swap
> signature and continue booting. This is what suspend2 does (with a
> timeout for the prompt). It's not that hard.
yes, but you need user input etc. Not considered a good idea IIRC.
Anyway, the hard thing to do is to find out when to bail out and when
not. The part that handles the user interface is the easier one :-)
Regards,
Stefan
next prev parent reply other threads:[~2005-03-21 8:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 16:28 Suspend-to-disk woes Erik Andrén
2005-03-18 17:54 ` Stefan Seyfried
2005-03-18 22:04 ` Nigel Cunningham
2005-03-19 13:26 ` Pavel Machek
2005-03-19 20:20 ` Russell Miller
2005-03-19 21:29 ` Pavel Machek
2005-03-19 21:44 ` Russell Miller
2005-03-21 0:14 ` Nigel Cunningham
2005-03-21 0:17 ` Matthew Garrett
2005-03-21 5:59 ` Nigel Cunningham
2005-03-21 9:33 ` Stefan Seyfried
2005-03-21 21:38 ` Nigel Cunningham
2005-03-21 7:38 ` Stefan Seyfried [this message]
2005-03-21 11:23 ` Nigel Cunningham
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=423E79DF.3030603@suse.de \
--to=seife@suse.de \
--cc=erik.andren@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--cc=rmiller@duskglow.com \
/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