From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>, Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: No warning on resume with different kernel version
Date: Mon, 16 Mar 2009 22:53:55 +0100 [thread overview]
Message-ID: <200903162253.55940.rjw@sisk.pl> (raw)
In-Reply-To: <20090316212329.GA12308@elf.ucw.cz>
On Monday 16 March 2009, Pavel Machek wrote:
> On Mon 2009-03-16 21:33:10, Rafael J. Wysocki wrote:
> > On Monday 16 March 2009, Pavel Machek wrote:
> > > On Sat 2009-03-14 16:28:59, Rolf Eike Beer wrote:
> > > > 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?
> > >
> > > Actually, it should now be possible to resume with different kernel
> > > than the one that did the suspendding...
> >
> > As long as it is 64-bit.
> >
> > Something broke if that doesn't work.
> >
> > Rolf, is your kernel 64-bit?
>
> And in 32-bit case, we should refuse to load the image. Something
> broke if that does not work :-).
Well, the description suggests the boot kernel didn't load the image, but
just continued to boot. That really depends on what "throws everything away"
means in the original report. Rolf?
Rafael
prev parent reply other threads:[~2009-03-16 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 15:28 No warning on resume with different kernel version Rolf Eike Beer
2009-03-16 11:38 ` 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 [this message]
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=200903162253.55940.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=eike-kernel@sf-tec.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox