[opensuse-factory] buggy kernel update
I recently updated my factory to the latest repo and zipper updated the kernel, everything did look fine but the modules were not installed!! After running a rescue, installing the kernel rpms from a usb, everything seems back to normal. Two things: - I thought the kernel updates should add another kernel instead of updating? It seems these updates can be touchy. - Where can I find a log of what happened? Erik. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 18 November 2008 18:16:41 Putrycz, Erik wrote:
I recently updated my factory to the latest repo and zipper updated the kernel, everything did look fine but the modules were not installed!! After running a rescue, installing the kernel rpms from a usb, everything seems back to normal.
Two things: - I thought the kernel updates should add another kernel instead of updating? It seems these updates can be touchy.
No, only if you have set multiversion option in /etc/zypp/zypp.conf
- Where can I find a log of what happened?
Check /var/log/zypper.log and /var/log/zypp/history Stano -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 18 November 2008 18:16:41 Putrycz, Erik wrote:
I recently updated my factory to the latest repo and zipper updated
the
kernel, everything did look fine but the modules were not installed!! After running a rescue, installing the kernel rpms from a usb, everything seems back to normal.
Two things: - I thought the kernel updates should add another kernel instead of updating? It seems these updates can be touchy.
No, only if you have set multiversion option in /etc/zypp/zypp.conf
Thanks! So what about having this on by default? I had quite a struggle just to copy the kernel rpm from a usb key to my system and then reinstall them.
- Where can I find a log of what happened?
Check /var/log/zypper.log and /var/log/zypp/history
Nothing looks odd there concerning the kernel installation... Very odd... Erik. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 18 November 2008 22:38:23 Putrycz, Erik wrote:
On Tuesday 18 November 2008 18:16:41 Putrycz, Erik wrote:
I recently updated my factory to the latest repo and zipper updated
the
kernel, everything did look fine but the modules were not
installed!!
After running a rescue, installing the kernel rpms from a usb, everything seems back to normal.
Two things: - I thought the kernel updates should add another kernel instead of updating? It seems these updates can be touchy.
No, only if you have set multiversion option in /etc/zypp/zypp.conf
Thanks! So what about having this on by default? I had quite a struggle just to copy the kernel rpm from a usb key to my system and then reinstall them.
No, because libzypp will not care for the number of the kernels installed in parallel - in the end, you will run out of space or hit other limits. I don't think it makes any sense to add any logic into handling number of kernels, because no software can automatically detect that it can remove kernel X - only user can. Stano -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
No, because libzypp will not care for the number of the kernels installed in parallel - in the end, you will run out of space or hit other limits.
Ideally, it would be nice for a kernel update to keep the previous version and ask the user after reboot to remove the previous version. It usually doesn't require very much to see if network and storage are working.
I don't think it makes any sense to add any logic into handling number of kernels, because no software can automatically detect that it can remove kernel X - only user can.
Agreed, it should be up to the user to decide that. However, a little logic to ease this would be nice. A repair or rollback after a buggy update (I've seen network or storage controllers failing in some kernel versions) can be quite time consuming. Erik. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wednesday 19 November 2008 17:01:21 Putrycz, Erik wrote:
No, because libzypp will not care for the number of the kernels
installed
in parallel - in the end, you will run out of space or hit other limits.
Ideally, it would be nice for a kernel update to keep the previous version and ask the user after reboot to remove the previous version. It usually doesn't require very much to see if network and storage are working.
The problem is to define 'working'. Also, some apps are influenced by kernel and do not work with the new one. How to identify those? etc...
I don't think it makes any sense to add any logic into handling number
of
kernels, because no software can automatically detect that it can
remove
kernel X - only user can.
Agreed, it should be up to the user to decide that. However, a little logic to ease this would be nice. A repair or rollback after a buggy update (I've seen network or storage controllers failing in some kernel versions) can be quite time consuming.
Maybe some help could be done in the software management YaST module. Any idea welcome! Stano -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Ideally, it would be nice for a kernel update to keep the previous version and ask the user after reboot to remove the previous version. It usually doesn't require very much to see if network and storage are working.
The problem is to define 'working'. Also, some apps are influenced by kernel and do not work with the new one. How to identify those? etc...
I'm not sure this can be done automatically so somekind of dialog after the reboot with the new kernel might be more appropriate: "Your kernel has been recently updated, would you like to keep the previous version?" Having the multiversion on by default is IMO good, but there should be somekind of mechanism to prevent ending with 10 versions. Maybe simply limiting the number of versions would do the trick? This shouldn't be too difficult to handle? I'm not sure why one would need more than 2 kernel versions. Erik. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Putrycz, Erik wrote:
Having the multiversion on by default is IMO good, but there should be somekind of mechanism to prevent ending with 10 versions. Maybe simply limiting the number of versions would do the trick? This shouldn't be too difficult to handle? I'm not sure why one would need more than 2 kernel versions.
Kernel development, specifically regression testing... building for
multiple compatible platforms and using TFTP/NFS?
I have 8 kernels on my Pegasos.. I make sure I keep around every one
I build and every one I install (although until now I have been
forcing the installation of the original kernel RPM and restoring
backups etc., multiversion would save me about a billion hours..)
--
Matt Sealey
On Wednesday 19 November 2008 11:13:59 am Putrycz, Erik wrote:
Having the multiversion on by default is IMO good, but there should be somekind of mechanism to prevent ending with 10 versions. Maybe simply limiting the number of versions would do the trick? This shouldn't be too difficult to handle? I'm not sure why one would need more than 2 kernel versions.
Making that as one of YaST configuration options. Keep n kernels. In another thread "design question" is discussed how to improve YaST. One way would be to add menu item "Configure YaST" where we can squeeze among other things how YaST Software Management acting when it comes to kernel installation. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Matt Sealey -
Putrycz, Erik -
Rajko M. -
Stanislav Visnovsky