similar to: [PATCH] linux-2.6.18/x86: refuse to initialize the microcode driver in DomU

Changeset 762:a070228ac76e ("add hvc compatibility mode to xencons" added this call just for the HVC case, without giving any reason why HVC would be special in this regard. Use the call for all cases. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/drivers/xen/console/console.c +++ b/drivers/xen/console/console.c @@ -214,8 +214,6 @@ static int __init xen_console_init(void)

This patch syncs up the microcode driver with linux 2.6.17 and adds on top of this enhancements (yet to be submitted to lkml) to prevent the driver from disabling interrupts for long periods of time. This is done by IPI-ing all remote CPUs sequentially rather than at once so they don''t all race for the same spin lock(s). Additionally, redundant updates on multiple siblings of the same

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

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

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

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

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

In 7.3.1611, running kernel "3.10.0-514.2.2.el7.centos.plus.x86_64 #1 SMP Wed Dec 7 19:10:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux" with microcode_ctl-2.1-16.1.el7_3.x86_64, I'm seeing the following error when booting: systemd[1]: [/usr/lib/systemd/system/microcode.service:10] Trailing garbage, ignoring. systemd[1]: microcode.service lacks both ExecStart= and ExecStop= setting.

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]

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

Subject: Obtain VESA capabilities and attributes of VESA mode Also, move some more common code to dom0_init_screen_info(). This was tested on 2.6.22.1, and only made apply to 2.6.18 without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2007-08-07/arch/i386/kernel/setup-xen.c =================================================================== ---

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