From: Johannes Stezenbach <js@sig21.net>
To: linux-pm@vger.kernel.org, x86@kernel.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: x86 hibernate, resume with different kernel version
Date: Thu, 16 Jun 2016 12:03:30 +0200 [thread overview]
Message-ID: <20160616100330.GA4954@sig21.net> (raw)
Hi,
it's not important for me but I hibernated kernel v4.5.7
and inadvertantly resumed using v4.6.2, and ISTR this
should work (confirmed by looking into git where I found
commit cc456c4e7cac3837a86aaa7ca3cb9f488d44d196).
My swap is an LVM volume inside dm-crypt, on boot the kernel read
the resume image but then immediately reset and invalidated it.
I'm using Debian sid, the initrd calls /bin/resume from
klibc-utils package.
So, should this still work? I couldn't find any
information about it.
Thanks,
Johannes
next reply other threads:[~2016-06-16 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 10:03 Johannes Stezenbach [this message]
2016-06-16 12:11 ` x86 hibernate, resume with different kernel version Rafael J. Wysocki
2016-06-16 19:06 ` Johannes Stezenbach
2016-06-16 22:00 ` Rafael J. Wysocki
2016-06-17 0:53 ` Rafael J. Wysocki
2016-06-17 7:35 ` Johannes Stezenbach
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=20160616100330.GA4954@sig21.net \
--to=js@sig21.net \
--cc=konrad.wilk@oracle.com \
--cc=linux-pm@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).