similar to: CentOS-announce Digest, Vol 172, Issue 2

CentOS Errata and Enhancement Advisory 2019:1414 Upstream details at : https://access.redhat.com/errata/RHEA-2019:1414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9de387cb9c61f7f46f1261820646ffa2579704ec0ab2fecae27a98a9ae6bd2bd microcode_ctl-1.17-33.13.el6_10.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2019:1390 Upstream details at : https://access.redhat.com/errata/RHEA-2019:1390 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 053fb3f1939753f74636c2acd1df57c299af8785d5097df8b05ba2ae9385e7d4 microcode_ctl-2.1-47.4.el7_6.x86_64.rpm Source:

Today when I ran yum update two packages came up microcode_ctl and unbound-libs. The updating process went fine until it outputted Running transaction Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 then it just froze. I could no longer ssh to the machine and the console was just blank. I had to shut down it hard. It came back up seemingly fine. But yum update doesn't work anymore. It

it is working thx a lot... but it has included the GenuineIntel.bin only in actually used kernel... do I need to reinstall microcode_ctl every time I update the kernel? And second question, I quess I still need the ucode = scan as xen parameter right? Am 2018-09-19 20:08, schrieb Kevin Stange: > On 9/19/18 1:55 AM, Christoph wrote: >> >> Hi >> >> can someone say me

Not sure about CentOS 6, but this was covered previously (at least for 7...not sure how much they differ)...not that I can find the message now, but here's what I recall/pieced together from bash history that works on CentOS 7: If the microcode you want is in the microcode_ctl package: mkdir -p /etc/microcode_ctl/ucode_with_caveats/ touch /etc/microcode_ctl/ucode_with_caveats/force yum

CentOS Errata and Bugfix Advisory 2019:1339 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1339 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f27bea79f341f5f6fe0fe2b65ced2c0f58c26403c2d84e6848a341f5ca939f65 bpftool-3.10.0-957.21.2.el7.x86_64.rpm

On Mon, 2020-06-15 at 22:25 +0200, Robin Lee wrote: > On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > Running transaction > > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > > > > then

On 01/18/18 11:31, Matthew Miller wrote: > On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: >> Do we update the microcode now or do we wait until the latest >> microcode_ctl rpm is available and then tackle this issue? > Check with your hardware vendor for BIOS/EFI firmware updates. Apply > those. > > > Thanks for the reply, but you missed what I was

On 01/18/18 09:01, Johnny Hughes wrote: > On 01/18/2018 07:51 AM, Phelps, Matthew wrote: >> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: >> >> So, if we applied the previous microcode update, and all our machines >> rebooted OK, then we don't need to fallback? >> >> Also, do we know if the updated CentOS microcode RPM

/etc/init.d/microcode_ctl start /etc/init.d/microcode_ctl: microcode device /dev/cpu/microcode doesn't exist? This is on a clean install from the 4.1 x86 ISO. This is the 2nd box that is reporting this error. Adam Breaux Sr. Network Administrator Domain Bank, Inc. 23 W 4th St. Bethlehem, PA 18015 Phone: 610.317.9606 Fax: 610.317.9570 abreaux at domainbank.com

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 does that process take place, and, can I affect it by adding microcode_ctl-2.1-18 ? On Wed, Jan 4,

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On 1/22/20 3:57 PM, Gary Stainburn wrote: > I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated > > The log below shows: > > [root at vps2 ~]# yum history info 22 > Loaded plugins:

CentOS Errata and Enhancement Advisory 2018:2300 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2300 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 274d9da87e0ec117315739c978ed0e60b95dd537d16a009752382439cf5ecdd4 microcode_ctl-1.17-33.3.el6_10.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2018:2675 Upstream details at : https://access.redhat.com/errata/RHEA-2018:2675 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6d40eac28340c2041aea1775a75ec383b7f780ca639adfe80af7e4bf792f87ef microcode_ctl-1.17-33.9.el6_10.i686.rpm x86_64: