similar to: Microcode.service error when booting 7.3.1611

On Wed, 11 Jan 2017, Albert McCann wrote: > Anyone else seeing this, or know what the secret fix is? It's not secret: https://bugzilla.redhat.com/show_bug.cgi?id=1411232 jh

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Johnny Hughes > Sent: Friday, November 25, 2016 10:13 AM > To: centos at centos.org > Subject: Re: [CentOS] Recent updates for CentOS7? > Then we will commence work on the OS tree and ISOs. Historically, this > takes 10-21 days for the full tree and ISOs .. but except for the >

On Wed, Jan 24, 2018 at 4:41 PM, Leon Fauster <leonfauster at googlemail.com> wrote: ... > > Comparing microcode-20171117 with microcode-20180108 shows that > from the 94 ucode files only 19 where updated > > $ diff -r --brief microcode-20171117 microcode-20180108 > Files microcode-20171117/intel-ucode/06-3c-03 and microcode-20180108/intel-ucode/06-3c-03 differ > Files

> Am 24.01.2018 um 22:22 schrieb Chris Adams <linux at cmadams.net>: > > Once upon a time, Chris Murphy <lists at colorremedies.com> said: >> "We recommend that OEMs, cloud service providers, system >> manufacturers, software vendors and end users stop deployment of >> current versions." Current versions of what? Microcode? > > Well,

Dropping users and adding pkg-xen-devel and debian-kernel. On Tue, 2012-11-06 at 15:43 +0100, Stephan Seitz wrote: > On Mon, Nov 05, 2012 at 06:12:53PM -0200, Henrique de Moraes Holschuh wrote: > >I would like to bring to your attention the improved support for system > >processor (CPU) microcode updates, for x86/i686/x86-64/amd64 systems > >that was recently added to

On Tue, Jan 23, 2018 at 4:26 AM, Johnny Hughes <johnny at centos.org> wrote: > > Here are a couple of posts for our reading pleasure: > > Intel recommends not installing the microcode now: > http://intel.ly/2DsL9qz Except this doesn't mention microcode at all. I can't even tell WTF they're recommending not doing in this doc, it's that badly written. You have

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: > >> On 01/18/2018 03:41 AM, Pete Biggs wrote: >>> >>>> Look at: >>>> >>>> https://t.co/6fT61xgtGH >>>> >>>> Get the latest microcode.dat file from here: >>>>

On 01/18/2018 03:41 AM, Pete Biggs wrote: > >> Look at: >> >> https://t.co/6fT61xgtGH >> >> Get the latest microcode.dat file from here: >> >> https://t.co/zPwagbeJFY >> >> See how to update the microcode from the links at the bottom of this page: >> >> https://t.co/EOgclWdHCw >> >> An before anyone asks .. I have no

On 01/22/18 09:08, Johnny Hughes wrote: > On 01/18/2018 09:42 AM, Valeri Galtsev wrote: >> >> >> On 01/18/18 03:41, Pete Biggs wrote: >>> >>>> Look at: >>>> >>>> https://t.co/6fT61xgtGH >>>> >>>> Get the latest microcode.dat file from here: >>>> >>>> https://t.co/zPwagbeJFY

On 01/17/2018 03:24 PM, Valeri Galtsev wrote: > Dear All, > > An update just brought on my CenOS 6 boxes updated microcode.dat files: > > ?/lib/firmware/microcode.dat > > Does anybody know off hand what (how critical) is that, as, if it is > related to most famous these days trouble with CPU hardware, I will need > to reboot relevant boxes to have new microcode

On Fri, Nov 25, 2016 at 8:55 AM, Albert McCann <mac358 at newsguy.com> wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Johnny Hughes >> Sent: Friday, November 25, 2016 10:13 AM >> To: centos at centos.org >> Subject: Re: [CentOS] Recent updates for CentOS7? > > >> Then we will commence work on

Hi! System: Debian/testing with selfcompiled kernel 3.5.5 (same error with 3.4 or 3.6) XEN: 4.1.3 After booting the Dom0 I notice the following errors: [ 2.939078] microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.991998] microcode: CPU0 update to revision 0xa0b failed [ 2.992035] microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.995882] microcode: CPU1 update to

On 01/18/18 03:41, Pete Biggs wrote: > >> Look at: >> >> https://t.co/6fT61xgtGH >> >> Get the latest microcode.dat file from here: >> >> https://t.co/zPwagbeJFY >> >> See how to update the microcode from the links at the bottom of this page: >> >> https://t.co/EOgclWdHCw >> >> An before anyone asks .. I have no idea

What's amazing to me is, after "Intel Inside - don't divide" (their 486 debacle), they didn't learn and have a better plan for addressing these kinds of things. ----- Original Message ----- From: "Chris Murphy" <lists at colorremedies.com> To: "centos" <centos at centos.org> Sent: Wednesday, January 24, 2018 12:06:01 PM Subject: Re: [CentOS]

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

On 01/22/2018 10:06 AM, Valeri Galtsev wrote: > > > On 01/22/18 09:08, Johnny Hughes wrote: >> On 01/18/2018 09:42 AM, Valeri Galtsev wrote: >>> >>> >>> On 01/18/18 03:41, Pete Biggs wrote: >>>> >>>>> Look at: >>>>> >>>>> https://t.co/6fT61xgtGH >>>>> >>>>> Get the

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

X86 microcode: add S3 micorcode update When wakeup from S3, use per cpu microcode image to update cpu microcode. Signed-off-by: Liu, Jinsong <jinsong.liu@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I have just installed Centos 5.0 from DVD. I have also run the software updates and I think everything is up to date. The motherboard is a Gigabyte GA945GM-S2 with an Intel E2140 processor. At boot time if I select show details - there is one error shown "in red", Like this: Applying Intel CPU microcode update. FATAL: Module microcode not found. ERROR: Module microcode does not exist

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > "We recommend that OEMs, cloud service providers, system > manufacturers, software vendors and end users stop deployment of > current versions." Current versions of what? Microcode? Well, that's the only thing Intel provides for CPUs, so that's all it can be. > What these means for people who