Le mercredi 07 novembre 2012 à 10:24 +0000, Frederic Crozat a écrit :
Le mercredi 07 novembre 2012 à 10:58 +0100, Jiri Slaby a écrit :
On 11/07/2012 09:34 AM, Frederic Crozat wrote:
Le mercredi 07 novembre 2012 à 09:09 +0100, Jiri Slaby a écrit :
On 11/05/2012 11:42 AM, Frederic Crozat wrote:
Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION.
Hi, I tried in a VM though. Installing systemd 195 kills process 1 (init) which indeed causes a panic: Installing: systemd-195-4.1 ....................................<100%> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
And unfortunately, this is something I can't reproduce reliably: got it one time while doing a full upgrade with 195-3.1 and I thought fixing the various udev instances running when upgrading would fix it but apparently, it doesn't.
From which state did you upgrade your VM ?
Just factory before the systemd update: systemd-44. I think it is related to libudev. libudev0 is removed, systemd is reexec'ed => boom. Or maybe other way around. systemd 195 is installed while libudev1 is not installed yet; reexec => boom. Is that a possible scenario?
systemd reexec is supposed to happen in %post of systemd, and systemd is upgraded only after both udev and libudev1 has been upgraded so it shouldn't be a problem.
I'll try again to duplicate this issue.
Ok, the latest fixes for the grub2 and kernel panic are now in Factory.
As Jiri suspected, zypper was removing libudev0 under packages foot,
causing this mess. We have restored libudev0 to Factory, which will also
allow people installing some proprietary programs (like Google Chrome)
which are still requiring libudev0.
--
Frederic Crozat