similar to: [LLVMdev] LLVM suitability for implementation in microcode/hardware?

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 reply, but you missed what I was asking.? I've > already

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

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

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

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

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 everyone, I?m a graduate student in a Brazilian Intitute of Technology, and I?m doing some academic research regarding secure voice transmission over phone lines. One of our reserach goals is to implement a hardware vocoder, with low bit rates, and a preferably free algorithm, to be used in this secure voice system. Actually, there is a functional system using a proprietary AMBE

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. Apply > those. > > > Thanks for the reply, but you missed what I was

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 <mattdm at fedoraproject.org> Fedora Project Leader

> 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

Respected Sir/Madam, I am working as Research Scholar at IIT, Bhubaneshwar, which is one of the pioneer educational organization in India. ( http://www.iitbbs.ac.in ) My assigned task is to transfer voice signal (Audio in future) over wireless sensor network. I have Arduino DUE, Arduino Mega, TMS320C6713 DSP board, TMS320F28379D Lunch pad, FPGA boards and necessary Microphone, filter, amplifier,

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

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 Wed, Mar 11, 2009 at 3:21 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > Now that I have HLVM up and running on x86 and x64 I am interested in > testing > it out on an ARM in preparation for their imminent world domination. I > believe LLVM already has excellent support for the ARM thanks to Apple's > ARM-based products. However, I'd really like an ARM-based

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

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