Community
cancel
Showing results for 
Search instead for 
Did you mean: 
GBöck
Beginner
1,604 Views

Braswell CPU (Cherry View)

Hallo, i have an intel celeron n3150 cpu. According to my kernel output on linux he has as cpuid 406c3. I followed the microcode update guidance, there should be already a new microcode update 00000367/00000410. But this update is not included in the new microcode data file from 12.03.2018 ...

So i would like to know if there will be this month or in the future a new microcode data file with all cpus included which are mentioned in the microcode update guidance as updated? And if not, have the vendors of the motherboard access to this updates?

0 Kudos
13 Replies
idata
Community Manager
188 Views

Thank you very much for contacting the Intel Communities Team, isndw.

 

 

Please find the link to Microcode Revision Guidance of March 6, 2018, where the CPUID of your processor is mentioned: https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf https://newsroom.intel.com/wp-content/uploads/sites/11/2018/03/microcode-update-guidance.pdf

 

In this case, I recommend you to double check with your OS support and the manufacturer of your system if they have an update for this vulnerability issue.

 

 

 

Antony S.
GBöck
Beginner
188 Views

Thank you for your answer. As i mentioned in my post i had already checked the microcode update guidance. My os is ubuntu 16.04 and there the microcode has been already updated, so the newest microcode is applied. The problem is, in the microcode of 12.03.2018 is my cpu not included:

https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?product=87258 https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?product=87258

So, the problem is not the operating system or the manufacturer, because they have also to wait for intel to deliver the microcode and the microcode for the n3150 is not delivered in the newest microcode file in contradiction to the microcode update guidance where the update should be already there.

So, i ask again, because your answer didn't answer my question: Will be there a new microcode file where all updates are included which are mentioned in the microcode update guidance as updated?

idata
Community Manager
188 Views

Thank you very much for your reply, isndw.

 

 

Regarding your question, the only information available we have is the following:We can not guarantee we will have a microcode file with all the updates included nonetheless, you can check the updated files so far.

 

I recommend you to verify with the Linux* Ubuntu support group for you to get the update for your system as well as your system manufacturer.

 

 

 

Antony S.
GBöck
Beginner
188 Views

Ubuntu delivered already the updates, but Linux depends also on the microcode file. So if intel dont deliver the microcode upates in the file nothing will happen. Ok, linux has also retpoline, so the situation is on linux not so bad.

I contacted already the manufacturer, they also told me they have to wait for intel ... so if intel don't deliver the updates nothing will happen.

The problem was announced in january, now its april ... whats going wrong here? The updates are here but not delivered?

My next computer will not anymore contain a intel cpu, that is for sure ... now there are more alternatives on the market.

idata
Community Manager
188 Views

Thank you for your response, isndw.

 

 

Please find on the https://downloadcenter.intel.com/download/27591/Linux-Processor-Microcode-Data-File?product=87258 Linux* Processor Microcode Data File, on the valid products list, you can see the Intel® Celeron® N3160 listed.

 

 

 

Antony S.
GBöck
Beginner
188 Views

Here, i can show you, in this file is not the update as mentioned in the microcode revision guidance:

microcode-20180312$ iucode_tool -tb -lS ./intel-ucode

iucode_tool: system has processor(s) with signature 0x000406c3

selected microcodes:

The output shows, for the selected processor 0x000406c3 is no update included. But in the microcode revision guidance is this mentioned:

Cherry View (Cherry Trail, Braswell) Intel® Atom® x5-Zxxxx CPU 406C3 01 Production --- --- 00000367

Cherry View (Cherry Trail, Braswell) Intel® Celeron® Processor Jxxxx, Intel® Celeron® Processor N3xxx, Intel® Pentium® Processor J3xxx, Intel® Pentium® Processor N3xxx, Intel® Atom® x5-E8000 Processor 406C4 01 Production --- --- 00000410

Only this processors got a update in the last microcode update file from intel (microcode-20180312.tgz):

microcode-20180312$ iucode_tool -tb -l ./intel-ucode

selected microcodes:

001: sig 0x00000650, pf mask 0x01, 1999-05-25, rev 0x0040, size 2048

002: sig 0x00000650, pf mask 0x02, 1999-05-25, rev 0x0041, size 2048

003: sig 0x00000650, pf mask 0x08, 1999-05-25, rev 0x0045, size 2048

004: sig 0x00000651, pf mask 0x01, 1999-05-25, rev 0x0040, size 2048

005: sig 0x00000652, pf mask 0x01, 1999-05-12, rev 0x002a, size 2048

006: sig 0x00000652, pf mask 0x02, 1999-05-17, rev 0x002c, size 2048

007: sig 0x00000652, pf mask 0x04, 1999-05-12, rev 0x002b, size 2048

008: sig 0x00000653, pf mask 0x01, 1999-06-28, rev 0x0010, size 2048

009: sig 0x00000653, pf mask 0x02, 1999-05-18, rev 0x000c, size 2048

010: sig 0x00000653, pf mask 0x04, 1999-05-20, rev 0x000b, size 2048

011: sig 0x00000653, pf mask 0x08, 1999-05-18, rev 0x000d, size 2048

012: sig 0x00000660, pf mask 0x01, 1999-05-05, rev 0x000a, size 2048

013: sig 0x00000665, pf mask 0x10, 1999-05-05, rev 0x0003, size 2048

014: sig 0x0000066a, pf mask 0x02, 1999-05-05, rev 0x000c, size 2048

015: sig 0x0000066a, pf mask 0x08, 1999-05-05, rev 0x000d, size 2048

016: sig 0x0000066a, pf mask 0x20, 1999-05-05, rev 0x000b, size 2048

017: sig 0x0000066d, pf mask 0x02, 1999-03-12, rev 0x0005, size 2048

018: sig 0x0000066d, pf mask 0x08, 1999-03-12, rev 0x0006, size 2048

019: sig 0x0000066d, pf mask 0x20, 1999-05-05, rev 0x0007, size 2048

020: sig 0x00000671, pf mask 0x04, 1998-08-11, rev 0x0014, size 2048

021: sig 0x00000672, pf mask 0x04, 1999-09-22, rev 0x0038, size 2048

022: sig 0x00000673, pf mask 0x04, 1999-09-10, rev 0x002e, size 2048

023: sig 0x00000681, pf mask 0x01, 1999-09-21, rev 0x000d, size 2048

024: sig 0x00000681, pf mask 0x04, 1999-09-21, rev 0x0010, size 2048

025: sig 0x00000681, pf mask 0x08, 1999-09-21, rev 0x000f, size 2048

026: sig 0x00000681, pf mask 0x10, 1999-09-21, rev 0x0011, size 2048

027: sig 0x00000681, pf mask 0x20, 1999-09-21, rev 0x000e, size 2048

028: sig 0x00000683, pf mask 0x08, 1999-10-15, rev 0x0008, size 2048

029: sig 0x00000683, pf mask 0x20, 1999-10-15, rev 0x0007, size 2048

030: sig 0x00000686, pf mask 0x01, 2000-05-05, rev 0x0007, size 2048

031: sig 0x00000686, pf mask 0x02, 2000-05-04, rev 0x000a, size 2048

032: sig 0x00000686, pf mask 0x04, 2000-05-04, rev 0x0002, size 2048

033: sig 0x00000686, pf mask 0x10, 2000-05-05, rev 0x0008, size 2048

034: sig 0x00000686, pf mask 0x80, 2000-05-04, rev 0x000c, size 2048

035: sig 0x0000068a, pf mask 0x10, 2000-11-02, rev 0x0001, size 2048

036: sig 0x0000068a, pf mask 0x20, 2000-12-07, rev 0x0004, size 2048

037: sig 0x0000068a, pf mask 0x80, 2000-12-07, rev 0x0005, size 2048

038: sig 0x00000695, pf mask 0x10, 2004-11-09, rev 0x0007, size 2048

039: sig 0x00000695, pf mask 0x20, 2004-11-09, rev 0x0007, size 2048

040: sig 0x00000695, pf mask 0x80, 2004-11-09, rev 0x0047, size 2048

041: sig 0x000006a0, pf mask 0x04, 2000-01-10, rev 0x0003, size 2048

042: sig 0x000006a1, pf mask 0x04, 2000-03-06, rev 0x0001, size 2048

043: sig 0x000006b1, pf mask 0x10, 2001-02-15, rev 0x001c, size 2048

044: sig 0x000006b1, pf mask 0x20, 2001-02-20, rev 0x001d, size 2048

045: sig 0x000006b4, pf mask 0x10, 2002-01-10, rev 0x0001, size 2048

046: sig 0x000006b4, pf mask 0x20, 2002-01-11, rev 0x0002, size 2048

047: sig 0x000006d6, pf mask 0x20, 2004-10-17, rev 0x0018, size 2048

048: sig 0x000006e8, pf mask 0x20, 2005-11-15, rev 0x0039, size 4096

049: sig 0x000006ec, pf mask 0x20, 2006-05-01, rev 0x0054, size 4096

050: sig 0x000006ec, pf mask 0x80, 2006-09-12, rev 0x0059, size 4096

051: sig 0x000006f2, pf mask 0x01, 2010-10-02, rev 0x005d, size 4096

052: sig 0x000006f2, pf mask 0x20, 2010-10-02, rev 0x005c, size 4096

053: sig 0x000006f6, pf mask 0x01, 2010-09-30, rev 0x00d0, size 4096

054: sig 0x000006f6, pf mask 0x04, 2010-10-01, rev 0x00d2, size 4096

055: sig 0x000006f6, pf mask 0x20, 2010-10-01, rev 0x00d1, size 4096

056: sig 0x000006f7, pf mask 0x10, 2010-10-02, rev 0x006a, size 4096

057: sig 0x000006f7, pf mask 0x40, 2010-10-02, rev 0x006b, size 4096

058: sig 0x000006fa, pf mask 0x80, 2010-10-02, rev 0x0095, size 4096

059: sig 0x000006fb, pf mask 0x01, 2010-10-03, rev 0x00ba, size 4096

060: sig 0x000006fb, pf mask 0x04, 2010-10-03, rev 0x00bc, size 4096

061: sig 0x000006fb, pf mask 0x08, 2010-10-03, rev 0x00bb, size 4096

062: sig 0x000006fb, pf mask 0x10, 2010-10-03, rev 0x00ba, size 4096

063: sig 0x000006fb, pf mask 0x20, 2010-10-03, rev 0x00ba, size 4096

064: sig 0x000006fb, pf mask 0x40, 2010-10-03, rev 0x00bc, size 4096

065: sig 0x000006fb, pf mask 0x80, 2010-10-03, rev 0x00ba, size 4096

066: sig 0x000006fd, pf mask 0x01, 2010-10-02, rev 0x00a4, size 4096

067: sig 0x000006fd, pf mask 0x20, 2010-10-02, rev 0x00a4, size 4096

068: sig 0x000006fd, pf mask 0x80, 2010-10-02, rev 0x00a4, size 4096

069: sig 0x00000f07, pf mask 0x01, 2002-07-16, rev 0x0012, size 2048

070: sig 0x00000f07, pf mask 0x02, 2000-11-15, rev 0x0008, size 2048

071: sig 0x00000f0a, pf mask 0x01, 2002-07-16, rev 0x0013, size 2048

072: sig 0x00000f0a, pf mask 0x02, 2002-08-21, rev 0x0015, size 2048

073: sig 0x00000f0a, pf mask 0x04, 2002-07-16, rev 0x0014, size 2048

074: sig 0x00000f12, pf mask 0x04, 2003-05-02, rev 0x002e, size 2048

075: sig 0x00000f24, pf mask 0x02, 2003-06-05, rev 0x001f, size 2048

076: sig 0x00000f24, pf mask 0x04, 2003-06-05, rev 0x001e, size 2048

077: sig 0x00000f24, pf mask 0x10, 2003-06-10, rev 0x0021, size 2048

078: sig 0x00000f25, pf mask 0x01, 2004-08-11, rev 0x0029, size 2048

079: sig 0x00000f25, pf mask 0x02, 2004-08-11, rev 0x002a, size 2048

080: sig 0x00000f25, pf mask 0x04, 2004-08-11, rev 0x002b, size 2048

081: sig 0x00000f25, pf mask 0x10, 2004-08-26, rev 0x002c, size 2048

082: sig 0x00000f26, pf mask 0x02, 2004-08-05, rev 0x0010, size 2048

083: sig 0x00000f27, pf mask 0x02, 2003-06-04, rev 0x0038, size 2048

084: sig 0x00000f27, pf mask 0x04, 2003-06-04, rev 0x0037, size 2048

085: sig 0x00000f27, pf mask 0x08, 2003-06-04, rev 0x0039, size 2048

086: sig 0x00000f29, pf mask 0x02, 2004-08-11, rev 0x002d, size 2048

087: sig 0x00000f29, pf mask 0x04, 2004-08-11, rev 0x002e, size 2048

088: sig 0x00000f29, pf mask 0x08, 2004-08-11, rev 0x002f, size 2048

089: sig 0x00000f32, pf mask 0x0d, 2004-05-11, rev 0x000a, size 2048

090: sig 0x00000f33, pf mask 0x0d, 2005-04-21, rev 0x000c, size 2048

091: sig 0x00000f34, pf mask 0x1d, 2005-04-21, rev 0x0017, size 7168

092: sig 0x00000f41, pf mask 0x02, 2005-04-21, rev 0x0016, size 5120

093: sig 0x00000f41, pf mask 0xbd, 2005-04-22, rev 0x0017, size 5120

094: sig 0x00000f43, pf ...

idata
Community Manager
188 Views

Thank you very much for your reply, isndw.

 

 

The only information we have available at this moment is the one I shared with you above. If your processor is not having this update yet it can be that either your processor was not affected or the update it has not been provided or achieved with your mainboard manufacturer. Please keep an eye on the links I attached and on the https://newsroom.intel.com/ newsroom.intel.com for any update on this vulnerability issue.

 

 

 

Antony S.
GBöck
Beginner
188 Views

"If your processor is not having this update yet it can be that either your processor was not affected"

If you ever read my comments you should know that my processor is affected.

"or the update it has not been provided or achieved with your mainboard manufacturer"

If you ever read my comments you should know that there is a update but the update is not in the microcode data file.

It is not the responsibility of the manufacturer to deliver a update, it is the responsability of intel because intel produced a bad product. The manufacturer can only deliver updates if intel delivers updates. And the microcode data file only shows that intel did not deliver the updates. So intel providing fake news if they tell us they have updates but they don't deliver them and in the microcode revision guidance they tell that there is a update.

So in the future i will never by a intel product again, the future lie in arm processors.

AlHill
Super User
188 Views

Well, in the future, when you are not buying Intel products, consider that the other manufacturers have issues as well:

https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/ https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/

And, nothing is immune from future hacks - nothing. So, throw a tantrum if you must.

Doc (not an Intel employee)

GBöck
Beginner
188 Views

It is not about that one product is better then an other ... there will be in the future other security problems. It is about how intel manage them and will manage them in the future. Intel was informed about meltdown and spectre already last year and had long time to react. They inform the customers that there are updates, but there are no updates. How intel handels their customers is the problem. I am not the only one who is disappointed from intel:

https://lkml.org/lkml/2018/1/3/797 https://lkml.org/lkml/2018/1/3/797

https://lkml.org/lkml/2018/1/21/192 https://lkml.org/lkml/2018/1/21/192

AlHill
Super User
188 Views

You should do whatever makes you happy. Since you are not happy here, perhaps someplace else will provide you with what you need.

Doc (no longer following this thread)

GBöck
Beginner
188 Views

I only hoped to get answers here ... intel does not provide a other way ...

b-
Beginner
188 Views

I had the same issue for my Atom x5-Z8300 based Linux system. Eventually, I found the microcode file I needed from a user in the BIOS modding community. It has presumably been extracted from some OEM's BIOS update. That doesn't matter though as the file should be identical to what Intel could've released publically.

I've renamed them in a way that gets picked up by the intel microcode update facility provided by the intel-microcode package in Debian/Ubuntu and presumably the equivalent packages in other distributions as well. Just put the appropriate file in /usr/share/misc/ and update your initramfs by running "sudo update-initramfs -u".

intel-microcode-406c3-0x367.bin: https://www.mediafire.com/?wcc5vmka6njllp3 https://www.mediafire.com/?wcc5vmka6njllp3

intel-microcode-406c4-0x410.bin: https://www.mediafire.com/?2hp44mn8g82mctn https://www.mediafire.com/?2hp44mn8g82mctn