search for: microcoded

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

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,

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

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 loaded. But if it is not that critical, it can wait till next reboot. Thanks a lot and

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]

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: > >> > >> https://t.co/zPwagbeJFY > >> > >> See how to update the microcode

> 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 why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)

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

i'm running on vmware system and HP proliant DL360 G5 servers on wmware, on boot i have the following message: ----------------------------- Applying Intel Microcode update: don't know to make device "cpu/microcode" [OK] ----------------------------- and on a HP proliant DL360 G5 server , on boot i have too the following message: ----------------------------- Applying

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 >>> >>> See how to update the microcode from the links at the bottom of this

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

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Hi all, This series adds a new microcode driver for Xen. The Xen hypervisor can deal with all the low-level details of doing a microcode update (Intel vs AMD, doing all the physical CPUs present on the system, current and future, etc), so all the driver has to do is make a hypercall to upload the microcode into Xen. This only

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 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 Tue, Sep 24, 2013 at 12:43:46PM -0700, Dave Airlie wrote: ... > > Hey Andy, > > this is great news, > > I suppose the question I have is there any known upfront limits on > what you can release or is it going to be a per-request type thing? Hi Dave. I think we're going to have to deal with things on a case-by-case basis. I wouldn't take anything off the table,

Hi, is there any guide for CPU microcode updates on CentOS6, Xen 4.10, kernel 4.9 ? Thanks Karel

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/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

Hi can someone say me how to update the ?code of the cpu with xen? I have added the ucode=scan parameter to xen but it does not seem to work... the ?code version of my xeon is really old :/ model name : Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz microcode : 0x10 -- ------ Greetz