(In reply to comment #10)
Just to make this fully clear: do we talk about (the sequence) kernel update, suspend and resume
no. In this case we won't suspend, since we know we cannot resume.
or kernel update, reboot, suspend and resume?
I was thinking about "boot, install 5 additional kernel versions, suspend". Well, then this scenario is as well unsupported as you didn't reboot after
https://bugzilla.novell.com/show_bug.cgi?id=223722 ------- Comment #13 from fseidel@novell.com 2006-12-04 03:15 MST ------- (In reply to comment #12) those kernelupdates.
As the entries in menu.lst seem to be random, i would not bet that the index is still correct :-) .as above: and if you reboot (supported sequence) you have known indexes (as written in comment #8 if grub tells us which entry/index was used).
Of course if you suspend directly after the kernel update (without reboot) this'll still be tricky. But do we really support resuming with a updated kernel a image created with the old one?
No, the changed kernel won't even be able to resume. That's why we refuse to suspend in this case.
Then it should also be refused in your case above where you have 5 kernelupdates. I really have the feeling we're talking at cross-purposes here. Stefan, i think we should discuss this on 1:1 today and give a our outcome here afterwards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.