[Bug 913996] New: Applying Critical Updates Causes System to no longer boot
http://bugzilla.opensuse.org/show_bug.cgi?id=913996 Bug ID: 913996 Summary: Applying Critical Updates Causes System to no longer boot Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 32bit OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: philbrown@llcareer.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- - H/W: VirtualBox 4.3.20 r96997 with snippets from log: 00:00:03.959144 Log opened 2015-01-20T22:01:28.803982000Z 00:00:03.959146 Build Type: release 00:00:03.959149 OS Product: Windows XP Professional 00:00:03.959151 OS Release: 5.1.2600 00:00:03.959152 OS Service Pack: 3 00:00:04.664908 DMI Product Name: A740GM-M 00:00:04.671200 DMI Product Version: 8.x 00:00:04.671220 Host RAM: 1919MB total, 1061MB available 00:00:04.671225 Package type: WINDOWS_32BITS_GENERIC 00:00:04.804741 Guest OS type: 'OpenSUSE' 00:00:04.818327 File system of 'openSUSE-13.2-DVD-i586.iso' (DVD) is ntfs - successfully run installation - after installation run ZYPPER='zypper --no-cd --non-interactive --no-gpg-checks' $ZYPPER refresh $ZYPPER update --auto-agree-with-licenses - if I reboot at this point system hangs with: Loading initial ramdisk... Do not know update causing problem, but problem only occurred within last week (today is 1/20/2015). Probably within last 3 days. Will attempt to gather more info if possible, but system fails after installing updates. Not sure how to get zypper/YaST to only install critical updates from a specific date. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
Charles-David Hebert
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
Brian Richter
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #49 from Brian Richter
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #51 from Brian Richter
(In reply to Brian Richter from comment #49)
I'm also having this same issue on my HP Pavilion DV4 at home. I'm going to try everything listed here and reply back with my findings.
Just try the kernel of the day here:
http://kernel.opensuse.org/packages/openSUSE-13.2
Thanks.
Currently I'm sitting at the loading initial ramdisk.... I will go ahead and regen then install the KOTD then apply all the updates needed Do you want me to grab any dmesg or cpuinfo prior to installing the KOTD and then possibly after install it and then also after i apply the updates (assuming i'm not bricked again) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #53 from Brian Richter
(In reply to Brian Richter from comment #51)
Currently I'm sitting at the loading initial ramdisk....
That's the broken kernel after the updates, correct?
I will go ahead and regen then install the KOTD then apply all the updates needed Do you want me to grab any dmesg or cpuinfo prior to installing the KOTD and then possibly after install it and then also after i apply the updates (assuming i'm not bricked again)
Just boot into a working kernel, install the KOTD as the URL above says and boot into that KOTD kernel. It should boot fine... (famous last words :-))
Thanks.
My steps. 1. do a clean installation 2. install the Kernel Of The Day zypper ar http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard \ Kernel:openSUSE-13.2 zypper in --from Kernel:openSUSE-13.2 kernel-desktop kernel installed 3.16.7-51.gea5ed9c-desktop 3. Reboot using the updated kernel: worked 4. Run all the security updates and recommended updates that are listed (165) 5. Reboot 6. Failed to load initial ramdisk again. - booting to recovery mode wouldn't work and also the old kernel didn't work. 7. I then added dis_ucode_ldr to the kernel command line and it worked. For the time being i'm going to add it to the bootloader config to always run this way until we can find a permanent fix. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #54 from Brian Richter
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
Borislav Petkov
2. install the Kernel Of The Day zypper ar http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard \ Kernel:openSUSE-13.2 zypper in --from Kernel:openSUSE-13.2 kernel-desktop kernel installed 3.16.7-51.gea5ed9c-desktop 3. Reboot using the updated kernel: worked 4. Run all the security updates and recommended updates that are listed (165) 5. Reboot 6. Failed to load initial ramdisk again.
Could it be that the update overwrote your KOTD kernel which you installed previously? When you reboot after applying the updates, which kernel are you booting into? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #56 from Brian Richter
(In reply to Brian Richter from comment #53)
2. install the Kernel Of The Day zypper ar http://download.opensuse.org/repositories/Kernel:/openSUSE-13.2/standard \ Kernel:openSUSE-13.2 zypper in --from Kernel:openSUSE-13.2 kernel-desktop kernel installed 3.16.7-51.gea5ed9c-desktop 3. Reboot using the updated kernel: worked 4. Run all the security updates and recommended updates that are listed (165) 5. Reboot 6. Failed to load initial ramdisk again.
Could it be that the update overwrote your KOTD kernel which you installed previously? When you reboot after applying the updates, which kernel are you booting into?
Thanks.
It doesn't look like it overwrote it, it's still pointing at the 3.16.7-51 that was pulled down. in the boot options I'm also making sure to specify it as well. May i ask what the ramifications are of adding dis_ucode_ldr to the boot option? Let me know what else you want like from that machine. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #57 from Philip Brown
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #58 from Brian Richter
FWIW - You know that the bit about using KOTD never solved the original problem either. The only way I got around it was to disable the ucode updates in zypper.
just wanted to try what was mentioned. As stated I was able to get around it without disabling the ucode in zypper by just adding the dis_ucode_ldr to the kernel command line. i'm actually performing another install right now on a desktop pc. Going to see if it affects that as well. Thanks Philip. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #59 from Brian Richter
(In reply to Philip Brown from comment #57)
FWIW - You know that the bit about using KOTD never solved the original problem either. The only way I got around it was to disable the ucode updates in zypper.
just wanted to try what was mentioned. As stated I was able to get around it without disabling the ucode in zypper by just adding the dis_ucode_ldr to the kernel command line.
i'm actually performing another install right now on a desktop pc. Going to see if it affects that as well.
Thanks Philip.
No issues running a fresh install on my desktop pc. i ran all the updates after the install and didn't run into an issue. I didn't use the KOTD just ran the default updates and it worked. Just my laptop is having the issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #60 from Brian Richter
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #61 from Borislav Petkov
It doesn't look like it overwrote it, it's still pointing at the 3.16.7-51 that was pulled down. in the boot options I'm also making sure to specify it as well.
Let me make sure I understand you correctly here: you're booting the 3.16.7-51 KOTD kernel and it fails. When you add "dis_ucode_ldr" to that same kernel, it boots fine. Correct?
May i ask what the ramifications are of adding dis_ucode_ldr to the boot option?
It disables the early microcode loader.
Let me know what else you want like from that machine.
Please boot the original kernel with which you've installed it with "log_buf_len=16M ignore_loglevel" on its command line, catch full dmesg and upload it here please. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #62 from Borislav Petkov
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #63 from Brian Richter
(In reply to Brian Richter from comment #56)
you're booting the 3.16.7-51 KOTD kernel and it fails. When you add "dis_ucode_ldr" to that same kernel, it boots fine. Correct?
That is correct. After performing the system upgrades even with the KOTD kernel i'm unable to load EITHER kernel without adding the dis_ucode_ldr to the kernel line. The original kernel no longer boots without adding the dis_ucode_ldr to the line. So my understanding would be that when the upgrade to the ucode-amd or ucode-intel happens it breaks regardless of what Kernel i have tried. I had followed the steps of using the rescue cd and performing the rpm -e ucode-intel ucode-amd on a system that was stuck and i was able to boot just fine without having to add the dis_ucode_ldr to the kernel line. I can go ahead and perform a regen on the spare harddrive i was working on and prior to performing the upgrades i can add the "log_buf_len=16M ignore_loglevel" to the kernel line. My question to you regarding DMESG is when do i perform that? do i perform that after the machine is booted up and open up a terminal to type it in? I want to make sure i capture the dmesg in the correct place. my understanding of dmesg is that i would need to capture it DURING the boot process not after. if so i'll have to figure out how to do this. All that said, after performing the upgrade to the ucode-amd and ucode-intel i'm not sure i can ever capture a proper dmesg because no kernel works after the upgrade without adding the dis_ucode_ldr to the kernel line. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #64 from Borislav Petkov
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #65 from Borislav Petkov
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #66 from Borislav Petkov
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
Adam Liebermann
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #84 from Adam Liebermann
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #85 from Adam Liebermann
in my opinion the updated (ucode-intel and ucode-amd) should be blocked because it'll crash a lot of systems and users will turn away.
I mean until the issue is resolved.. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
--- Comment #99 from Adam Liebermann
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
Rafael M Redondo
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c108
--- Comment #108 from Rafael M Redondo
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c109
--- Comment #109 from Rafael M Redondo
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c114
Ashfaqur Rahman
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c116
--- Comment #116 from Ashfaqur Rahman
By host you mean virtual box?
By host I meant the 'Host Operating System' or the 'Physical/Real machine' By Guest I meant the 'Virtual Operating System' or the 'Virtual Machine'
Can you try the latest kernel of the day here:
I will try, but where do I install the kernel? In the Host OS or the Guest OS? or both? Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c118
--- Comment #118 from Ashfaqur Rahman
I know what those mean. I wanted to know what kind of virtualization you're using: kvm, virtual box, xen...?
Oh, sorry about that, my bad. I am using VirtualBox (Version 4.3.30)
You replace the kernel which fails booting. You sad "Guest Hangs" and that dis_ucode_ldr fixes the issue so it seems you should install this in the guest...
Thanks for explaining that. Added the repo for the kernel in YaST Updated everything to the latest version Now the kernel is Kernel-Desktop(3.16.7-97.gec183cc) Removed "dis_ucode_ldr" Guest hangs! Just like before :( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c120
--- Comment #120 from Ashfaqur Rahman
Oh well, I can try to reproduce it but it'll take a while since I'm on vacation currently.
OK, thanks. Enjoy your time, best of luck. Will be looking forward to your feedback. BTW: I don't mean to pry on your personal schedule, but any approximate idea/date when you might be able to look into this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c121
--- Comment #121 from Ashfaqur Rahman
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c122
--- Comment #122 from Ashfaqur Rahman
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c123
--- Comment #123 from Ashfaqur Rahman
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c124
--- Comment #124 from Ashfaqur Rahman
First I Updated Host
Rebooted
Then I restored a snapshot of the Guest
If you check the logs carefully you will notice that I had actually updated the Guest first.!! Sorry, was caught up in the excitement of things. Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c126
--- Comment #126 from Ashfaqur Rahman
So I guess something wasn't regenerated properly with the new kernel during your first try. initrd needed recreation, probably (I'm only just guessing...).
I am not sure what you meant by the words "new kernel"... If you meant "kernel of the day" in the Guest, which I had upgraded; then that kernel is not involved here cos I started the Guest machine from a snapshot, which was taken before upgrading to that kernel (or adding that repo). Also... why is the initrd being recreated *on the Host* ??? Did the Host kernel change?? It seems only the pkg "virtualbox-guest-kmp-desktop" when upgraded (in the Host), initiated the initrd being recreated!! Is that supposed to happen?? "virtualbox-guest-kmp-desktop" is also the common pkg that got upgraded in both the Host & Guest; and it seems to have fixed all the problems (..just guessing..) Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=913996
http://bugzilla.opensuse.org/show_bug.cgi?id=913996#c127
--- Comment #127 from Ashfaqur Rahman
participants (1)
-
bugzilla_noreply＠novell.com