All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Swsusp, resume and kernel versions
Date: Wed, 16 Feb 2005 23:46:25 -0500	[thread overview]
Message-ID: <200502162346.26143.dtor_core@ameritech.net> (raw)

Pavel,

First of all I must say that swsusp has progressed alot and now works
very reliably, at least for my configuration, and I use it a lot. Great
job!

But I think there is one pretty severe issue present - even if swsusp
is not enabled kernel should check if there is an image in swap and
erase it. Today I has somewhat unpleasant experience - after suspending
I accidentially loaded a vendor kernel. I was in hurry and decided that
resume just failed for some reason so I did couple of things and left
the box running. In the evening I realized that I am running vendor kernel
and decided to reboot into my devel. version. What I did not expect is for
the kernel to find a valid suspend image and restore it. As you might
imagine messed up my disk somewhat.

Any chance this can be done?

-- 
Dmitry

             reply	other threads:[~2005-02-17  4:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17  4:46 Dmitry Torokhov [this message]
2005-02-17  5:15 ` Swsusp, resume and kernel versions Nigel Cunningham
2005-02-17  5:38   ` Dmitry Torokhov
2005-02-17  8:09     ` Nigel Cunningham
2005-02-17 21:05       ` Stefan Seyfried
2005-02-18 10:34         ` Nigel Cunningham
2005-02-18 11:23           ` Stefan Seyfried
2005-02-17 11:07 ` Pavel Machek
2005-02-17 16:28   ` John M Flinchbaugh
2005-02-17 17:30     ` Dmitry Torokhov
2005-02-17 19:56       ` Pavel Machek
2005-02-17 20:09         ` Dmitry Torokhov
2005-02-18  2:02         ` Bernard Blackham
2005-02-18 11:24           ` Pavel Machek
2005-02-18 12:26             ` Bernard Blackham

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=200502162346.26143.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --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.