[Bug 913996] Applying Critical Updates Causes System to no longer boot (ucode-intel / ucode-amd problem?)
11 May
2015
11 May
'15
20:58
http://bugzilla.suse.com/show_bug.cgi?id=913996 --- Comment #89 from James Moe <jimoe@sohnen-moe.com> --- On 2015-05-03 I upgraded our main server. It has the same motherboard as the other systems (asus m3a78-em) with the AMD CPU 630 4-core. It has exhibited the same microcode issue as the other systems but with a more restrictive twist. Disabling the modules ucode-intel and ucode-amd in the Software Manager was not sufficient to prevent a catatonic system. It is a necessary requirement to include "dis_ucode_ldr" in the kernel parameters at boot time (GRUB2). -- You are receiving this mail because: You are on the CC list for the bug.
3513
Age (days ago)
3513
Last active (days ago)
0 comments
1 participants
participants (1)
-
bugzilla_noreply@novell.com