Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

2017-01-04 Thread Paul Heinlein
On Wed, 4 Jan 2017, Locane wrote: Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How does that process take place, and, can I affect it by adding

Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

2017-01-04 Thread Locane
Thanks for the breakdown Paul - I've had to learn all my sysadmin stuff through organic interactions like this. Still though - someone manages the default repositories - so my question is, who decides when a package gets an update from whatever CentOS ships with default to a newer version? How

Re: [CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

2017-01-04 Thread Paul Heinlein
On Wed, 4 Jan 2017, Locane wrote: My questions are, who decides what packages are current for CentOS when I "yum upgrade"? That's determined by the repositories defined and enabled in /etc/yum.conf and /etc/yum.repos.d/*.repo. To see the repositories enabled by your system, ask yum: yum

[CentOS] microcode_ctl-2.1-16 hard crash on Intel E5 2667 v4 CPUs

2017-01-04 Thread Locane
Hello all! I'm brand new to the mailing list, and I've encountered an issue with the microcode_ctl package version 2.1-16 being installed during the CentOS 7.3 upgrade. It causes my servers to hard stop and they need to be forcibly powered off and back on again with the power button to continue.