From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: No warning on resume with different kernel version
Date: Sat, 14 Mar 2009 16:28:59 +0100 [thread overview]
Message-ID: <200903141629.05282.eike-kernel@sf-tec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
Hi,
I'm sure this had worked before. And since I don't do that on a regular basis,
but only by accident, I have no idea when it stopped working. But with my
2.6.28 kernel and everything more recent I don't get a warning if there is a
suspend image of a different kernel version, but simply the new kernel starts
and throws everything away. Is this a kernel fault or something with the
userspace stuff? Whom to blame for this?
Greetings,
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-03-16 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 15:28 Rolf Eike Beer [this message]
2009-03-16 11:38 ` No warning on resume with different kernel version Pavel Machek
2009-03-16 20:33 ` Rafael J. Wysocki
2009-03-16 21:23 ` Pavel Machek
2009-03-16 21:53 ` Rafael J. Wysocki
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=200903141629.05282.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
/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