Skip to contentSkip to conversation

No warning on resume with different kernel version

DISCUSSION Rolf Eike Beer 3 participants 5 messages Mar 16, 2009

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 8 lines · Rolf Eike Beer

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...
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#2 lore raw
Quoted 10 lines · Pavel Machek
Quoted 8 lines · Rolf Eike Beer

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?

Quoted 2 lines

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?

Thanks,
Rafael

#3 lore raw
Quoted 11 lines · Rafael J. Wysocki
Quoted 10 lines · Pavel Machek
Quoted 8 lines · Rolf Eike Beer

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?

Quoted 8 lines
Quoted 2 lines

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 :-).
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#4 lore raw
Quoted 15 lines · Pavel Machek
Quoted 14 lines · Rafael J. Wysocki
Quoted 12 lines · Pavel Machek
Quoted 8 lines · Rolf Eike Beer

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...

Quoted 8 lines
Quoted 5 lines

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