Description of problem: After applying the updates that included kernel 2.6.38.8-desktop-2.mga2, without restarting, I hibernated. Waking up from hibernation ignored the fact that the system was hibernated, and the newest kernel was booted instead. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Update to a newer kernel. Do not restart immediately as suggested. 2. Hibernate the system. 3. Wake up the computer from hibernation. It will act as if no hibernation was performed.
Hi Radu, Sorry for responding so late. I'm not really sure this is a bug, because after a kernel update we are always told we should reboot. I'll leave that up to a developer to decide, but one question before I do that: Is the bug still valid with the last kernel update?
Keywords: (none) => NEEDINFOCC: (none) => marja11
@ tmb Am I correct to think this isn't a bug, but user error (or should letting your system hibernate and wake up after a kernel update instead of rebooting it, work as if you never installed the new kernel)?
CC: (none) => tmb
In my opinion, the default settings of /etc/sysconfig/installkernel which has both NO* entries set to null, which means that on the next reboot, the new kernel will be used, whether the system is recovering from reboot, or is a normal reboot, it is a bug. How it should be handled, I'm not sure. Either we tell the user on a new kernel install, that they must reboot normally, before using the option to hibernate, or we modify the hibernate routine to ensure the old kernel will be used on the resume. I think telling the user to reboot before using the hibernate option is easier, and safer.
CC: (none) => davidwhodgins
(In reply to comment #3) > > I think telling the user to reboot before using > the hibernate option is easier, and safer. You interpret the line: "You should restart your computer for kernel-desktop-*" very different than I do. I thought it was a command: reboot your computer So what does "You should restart your computer for kernel-desktop-*" really mean? Is the hibernation issue all that can go wrong if you don't reboot?
Keywords: (none) => USABILITY
well the reporter didn't replay, I'am for closing this bug.
@ Manuel I agree, but I would still like to know whether I misunderstand "You should restart your computer for kernel-desktop-*"
The word should is not the same as the word must. Installing a new kernel doesn't mean it ever has to be booted. If you're using the bootloader menu entry that points to symlink /boot/vmlinuz, and use hibernation, the resume will be broken, as it will automatically select the new version. If you're manually selecting the kernel version, and keep selecting the same version (not the new one), you'll keep using the old kernel, and resume will continue working. There is no real reason for anyone to change to a new kernel, unless the new kernel fixes a problem that affects their system. As Mageia does default to using the /boot/vmlinux symlink, I think the message displayed about rebooting, should simply have an additional statement. "You should restart your computer for kernel-desktop-*. Do not use hibernation until the new kernel is running".
(In reply to comment #7) > I think > the message displayed about rebooting, should simply have an additional > statement. > > "You should restart your computer for kernel-desktop-*. Do not use > hibernation until the new kernel is running".
Source RPM: (none) => kernel-desktop
(In reply to comment #7) > I think > the message displayed about rebooting, should simply have an additional > statement. > > "You should restart your computer for kernel-desktop-*. Do not use > hibernation until the new kernel is running". OK. assigning to tmb
Assignee: bugsquad => tmbKeywords: NEEDINFO => (none)
CC: (none) => doc-bugsHardware: i586 => All
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ tmb Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
This bug affects the warning displayed to the user when installing a kernel update, so all versions are affected.
Whiteboard: (none) => MGA2TOO, MGA1TOOKeywords: NEEDINFO => (none)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Could we get that message enhanced as proposed, and close this bug? > "You should restart your computer for kernel-desktop-*. Do not use > hibernation until the new kernel is running".
CC: (none) => fri
(In reply to Morgan Leijström from comment #14) > Could we get that message enhanced as proposed, and close this bug? > > > "You should restart your computer for kernel-desktop-*. Do not use > > hibernation until the new kernel is running". isn't this something for urpmi ? cc thierry
CC: (none) => thierry.vignaud
ping...
I regularly do hibernation with a newer kernel installed and it always boot the one used by the hibernated system (but I usually don't boot the "Mageia" generic entry but a specific "3.x" entry which may helps PM finds the right kernel on resume)
Great -if we for mga3, mga4, and cauldron can be sure that when hibernated it always boot the kernel that was running, then we can set this bug resolved fixed (or worksforme) Can someone work to confirm it works like that on vanilla unaltered installs?
I will try next time I have a kernel update on Cauldron.
CC: (none) => remi
I think it sometimes boot wrong kernel, but that may be because the hibernation process have severe issues, bug 14392.
Trying to summarise: 1) after kernel update a dialog tells user he should reboot. - not *must* 2) Updating take long time in some cases of amount and download speeds so user may go for coffee, telephone, other work, and system decide to hibernate, so we simply can not tell if the user see it. /!\ Do we even have a lock to hinder that the system suspends or hibernates automatically, when update is in progress and user not active? So as i see it, the system *must* be able to hibernate and resume without having been rebooted since last kernel update. @Rémi or anyone: did you try?
rpm has a systemd_inhibit plugin so every transaction shouldn't not be "interrupted" by shutdown/sleep This is trye for Mga5 for those who have updated to rpm-4.12.0.1-20.7.mga5
Super :) And thanks for the quick reply Thierry. That answered my "/!\" above. What still need to be validated is reliability of resuming with correct kernel after kernel update, before reboot.
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.
Assignee: tmb => kernel
I guess this one can be closed. We are long time past kernel 2.6.38.8-desktop-2.mga2. Please reopen if I'm wrong.
CC: (none) => micheelsenStatus: NEW => RESOLVEDResolution: (none) => OLD