Andrey Borzenkov wrote:
� Wed, 09 Jan 2013 03:37:09 -0800 Linda Walsh
�����: Andrey Borzenkov wrote:
I have quite strange effect on current Factory installation. Any attempt to reboot (including systemctl --force --force reboot, which /should/ just directly execute syscall) behave as if I requested kexec. I never see usual firmware initial screen, or bootloader (GRUB2). After small delay I am presented with booting kernel.
This is VMware Player running with EFI firmware. 12.2 is OK.
Anyone experiences the same?
-andrey
Yes.
I had to chkconfig kexec to 'off' to fix the problem.
The bug, was (is?) due to code that tries to boot from the next oldest kernel on a reboot from the most current kernel.
Could you give a hint where this code is located? :)
Um....it's been a bit... it all used to be in the /etc/rc scripts, but with 12.3 things for boot are even in /usr/share/<some dirs>... I'd look in the boot/reboot control scripts -- it has to do some last minute check... I don't have 12.3 installed so much -- trying to get to a stable 12.1 config --- I'm still afraid to reboot my server -- since ever since I tried putting parts of 12.2/.3 on it, have had to baby-sit it coming up...often using a recovery disk. The actual reboot is likely at the end of the /etc/rc.d/halt script (or it's systemd equiv...)... it tests there to see if it should do a warm reboot or not.. but something before that...(which I don't have on my system anymore) tried loading the "next kernel" after your current kernel -- as though it assumed a the current boot didn't work, so it is trying to recover by rebooting from the previous version. But I've got 0 time to look into those issues right now. Unless you are doing kernel devel, I don't see why you'd need "kexec" enabled (i.e. "chkconfig kexec off" should stop the wayward behavior). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org