Comment # 63 on bug 913996 from Brian Richter

(In reply to Borislav Petkov from comment #61)
> (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.