> 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 pa
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 anyo
Send CentOS-announce mailing list submissions to
centos-annou...@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-requ.
Hello everyone -
I have a minor problem with yum-cron. It has been doing this for a long time,
and finally today I got annoyed enough to want to fix it.
The problem: When yum-cron sends an email notification, the message is sent
without a date field. Therefore it shows up in my inbox as "dat
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 microcode from the links a
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:
https://t.co/zPwagbeJFY
>
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:
>
> https://t.co/6fT61xgtGH
>
> Get the
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 H
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 know if the updated Cen
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 microcode from the li
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
Fedora Pr
> 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 releas
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. App
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. App
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 re
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. Apply
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. App
17 matches
Mail list logo
