There is a new guidance document from Intel here
https://newsroom.intel.com/wp-content/uploads/sites/11/2018/04/microcode-update-guidance.pdf
Changes since the previous release are highlighted in yellow.
Unfortunately, the latest microcode here
On Wed, Jan 24, 2018 at 4:41 PM, Leon Fauster
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
> Am 24.01.2018 um 22:22 schrieb Chris Adams :
>
> Once upon a time, Chris Murphy said:
>> "We recommend that OEMs, cloud service providers, system
>> manufacturers, software vendors and end users stop deployment of
>> current versions." Current
Once upon a time, Chris Murphy 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
mark
> - Original Message -
> From: "Chris Murphy" <li...@colorremedies.com>
> To: "centos" <centos@centos.org>
> Sent: Wednesday, January 24, 2018 12:06:01 PM
> Subject: Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6
>
&g
n't plan to address
these things at all ;-)
Valeri
>
> - Original Message -
> From: "Chris Murphy" <li...@colorremedies.com>
> To: "centos" <centos@centos.org>
> Sent: Wednesday, January 24, 2018 12:06:01 PM
> Subject: Re: [CentOS] /lib/firmw
os@centos.org>
Sent: Wednesday, January 24, 2018 12:06:01 PM
Subject: Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6
On Tue, Jan 23, 2018 at 4:26 AM, Johnny Hughes <joh...@centos.org> wrote:
>
> Here are a couple of posts for our reading pleasure:
>
> Intel re
On Tue, Jan 23, 2018 at 4:26 AM, Johnny Hughes 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
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 latest microcode.dat file from
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
See how to update the microcode from the links at the
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
On 01/18/18 12:55, Matthew Miller wrote:
On Thu, Jan 18, 2018 at 11:45:42AM -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.
On 18/01/18 18:55, Matthew Miller wrote:
On Thu, Jan 18, 2018 at 11:45:42AM -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.
On Thu, Jan 18, 2018 at 11:45:42AM -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
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.
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.
> OK, so color me confused about the timing in all this.
>
> Do we update the microcode now or do we wait until the latest microcode_ctl
> rpm is available and then tackle this issue?
The message is: stay away from microcode updates because they're broken right
now. Intel may or may not
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.
--
Matthew Miller
On Thu, 18 Jan 2018 04:03:48 -0600
Johnny Hughes 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
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 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
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 why Red
On Thu, Jan 18, 2018 at 9:01 AM, Johnny Hughes wrote:
> On 01/18/2018 07:51 AM, Phelps, Matthew wrote:
> > On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes
> wrote:
> >
> >> On 01/18/2018 03:41 AM, Pete Biggs wrote:
> >>>
> Look at:
>
>
On 01/18/2018 07:51 AM, Phelps, Matthew wrote:
> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes 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 Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes 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
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
> 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
> Am 17.01.2018 um 23:22 schrieb Johnny Hughes :
>
> 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
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
On 17/01/18 21:24, 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
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
30 matches
Mail list logo