ATTN!...Intel CPU owners (Spectre,Meltdown,Foreshadow, flaws)

Chat about just about anything else
rene
Level 8
Level 8
Posts: 2181
Joined: Sun Mar 27, 2016 6:58 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by rene » Sat Jan 13, 2018 6:37 pm

neversaynever wrote:I don’t understand why I’m vulnerable by Meltdown, with PTI not enabled, even if I updated without problems to kernel v. 4.4.0.109-132.
You are running 32-bit Linux Mint 18; KPTI is indeed not enabled for 32-bit kernels. This isn't to say a 32-bit x86 CPU or 64-bit x86 CPU in 32-bit mode necessarily isn't affected by the problem; is to say they are low priority.

You're on a second generation Core i7 which is to say that you very likely should not be running a 32-bit OS; unlikely you'd be coupling that CPU with 1G of RAM or less. If you did not elect to run a 32-bit OS explicitly: you'll need to first of all install a 64-bit version of Mint.

User avatar
michael louwe
Level 9
Level 9
Posts: 2692
Joined: Sun Sep 11, 2016 11:18 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by michael louwe » Sun Jan 14, 2018 2:13 am

@ neversaynever, .......
neversaynever wrote:...
.
https://insights.ubuntu.com/2018/01/04/ ... abilities/
Ubuntu users of the 64-bit x86 architecture (aka, amd64) can expect updated kernels by the original January 9, 2018 coordinated release date
It's likely that updated kernels 4.4.109, 4.13.25 and 3.13.139 also patch the Spectre1 bug(CVE-2017-5753) for 32bit Ubuntu systems, but not for the Meltdown bug.
... Similarly, M$ only patched 32bit Windows for Spectre1 and 2 but not for Meltdown.
.
Common Intel microcode updates for Linux systems are sent to nearly all Intel processors but may apply to only a subset of processors. It is up to Linux users to verify this = to install or not to install the microcode update. During installation of the microcode update, applicable processors will be updated while non-applicable processors remain unchanged.
... The 20180108 Intel microcode update to patch Spectre2 only applies to Intel processors that are 3rd-gen IvyTown(Xeon), and 4th-gen Haswell (Core i3, i5 and i7) or newer. So, it does not apply to 3rg-gen IvyBridge or older. You have a 2nd-gen Intel SandyBridge processor.
Last edited by michael louwe on Sun Jan 14, 2018 2:30 am, edited 4 times in total.

User avatar
buffest_overflow
Level 2
Level 2
Posts: 54
Joined: Sun May 07, 2017 8:35 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by buffest_overflow » Sun Jan 14, 2018 2:14 am

thx-1138 wrote:
buffest_overflow wrote:Can you spot the part I'm scared of? Does anyone happen to know what this means? if this is the wrong place for this, I'll go wandering off into the distance.
...i assume you mean the cpu_insecure part? That's exactly what it should report...
https://askubuntu.com/questions/992137/ ... -my-ubuntu
Thank you!

Code: Select all

~ $ grep -q "cpu_insecure\|cpu_meltdown\|kaiser" /proc/cpuinfo && echo "patched :)" \
> || echo "unpatched :("
patched :)

User avatar
buffest_overflow
Level 2
Level 2
Posts: 54
Joined: Sun May 07, 2017 8:35 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by buffest_overflow » Sun Jan 14, 2018 2:24 am

Terryphi wrote:
buffest_overflow wrote:...
Are you sure you have updated the kernel as well as the intel-microcode?
I followed all guidelines to the best of my ability given the confusion present in all parties involved. Per above post, the KAISER (meltdown relevant) part of the patch was addressed in the 4.4 update manager release notes; though I read about KAISER on ycombinator, meltdown was not mentioned in the release notes. I can't say I understand what any of this actually means. I'm a doctor Jim, not a computer scientist.

cat /proc/cpuinfo still tells me bugs:cpu_insecure. Do I need to revert to a different kernel, or is this just something not updating correctly? I did in fact turn my computer off, then I turned it on again. Newer users are indoctrinated with the belief that hopping around different kernels is not the best idea. I do make daily backups in lucky and in timeshift.

edit: I notice I now have the "pti" flag in cpuinfo; I am going to assume that for some reason cpuinfo isn't saying the right thing in the bugs field?

uname:

Code: Select all

Linux synth0 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

User avatar
thx-1138
Level 6
Level 6
Posts: 1154
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by thx-1138 » Sun Jan 14, 2018 3:11 am

Newer users are indoctrinated with the belief that hopping around different kernels is not the best idea.
...they aren't indoctrinated, they are frequently suggested though to not do such...exactly because it isn't the best idea - if it breaks, how are newer users supposed to gather the pieces afterwards?... :)
buffest_overflow wrote: cat /proc/cpuinfo still tells me bugs:cpu_insecure. Do I need to revert to a different kernel, or is this just something not updating correctly? I did in fact turn my computer off, then I turned it on again.
buffest_overflow, you were probably looking at the...'wrong' comments in the askubuntu link that i sent. It explains it pretty clear, and so did michael here as well:
michael louwe wrote:@ buffest_overflow, .......

Seems, the newer Linux kernels now flag all Intel CPUs as cpu_insecure = already patched for the Meltdown bug.

I have a LM 17.3 box running kernel 3.13.107(not yet patched for Meltdown) and Intel Core2Duo CPU which is not flagged as 'bug: cpu_insecure'.
It is meant to say cpu_insecure and that is what it will say so from now on in patched kernels when running under affected processors. It won't say such on: 1) unpatched kernels & 2) corrected processors if / when they appear in the market...

User avatar
michael louwe
Level 9
Level 9
Posts: 2692
Joined: Sun Sep 11, 2016 11:18 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by michael louwe » Sun Jan 14, 2018 6:04 am

http://news.softpedia.com/news/canonica ... 9359.shtml (Canonical Says It'll Release New Ubuntu Kernels to Further Mitigate Spectre Bugs - dated 12 Jan 2018)

I think the coming 15 Jan 2018 kernel 64bit patches from Canonical-Ubuntu will be patching Spectre 1 & 2 (CVE-2017-5753 & 5715), eg the ibrs, ibpb and binary compiler features. Windows 64bit already patched them on 4 Jan 2018. Windows 32bit has not patched Meltdown/kpti but is patched for Spectre 1 & 2.
... Following suit will be the same Meltdown & Spectre patches for 32bit Ubuntu/LM systems.

The Intel microcode update for 3rd-gen Ivybridge processors or older should also be coming. The update apply to both 64bit and 32bit Linux/Ubuntu/LM systems.

https://www.pcworld.com/article/3247847 ... mance.html (Here's how much the Meltdown and Spectre fix hurt my Surface Book performance - dated 13 Jan 2018)

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 11:59 am

rene wrote:
neversaynever wrote:I don’t understand why I’m vulnerable by Meltdown, with PTI not enabled, even if I updated without problems to kernel v. 4.4.0.109-132.
You are running 32-bit Linux Mint 18; KPTI is indeed not enabled for 32-bit kernels. This isn't to say a 32-bit x86 CPU or 64-bit x86 CPU in 32-bit mode necessarily isn't affected by the problem; is to say they are low priority.
You're on a second generation Core i7 which is to say that you very likely should not be running a 32-bit OS; unlikely you'd be coupling that CPU with 1G of RAM or less. If you did not elect to run a 32-bit OS explicitly: you'll need to first of all install a 64-bit version of Mint.
michael louwe wrote:@ neversaynever, .......
neversaynever wrote:...
.
https://insights.ubuntu.com/2018/01/04/ ... abilities/
Ubuntu users of the 64-bit x86 architecture (aka, amd64) can expect updated kernels by the original January 9, 2018 coordinated release date
It's likely that updated kernels 4.4.109, 4.13.25 and 3.13.139 also patch the Spectre1 bug(CVE-2017-5753) for 32bit Ubuntu systems, but not for the Meltdown bug.
... Similarly, M$ only patched 32bit Windows for Spectre1 and 2 but not for Meltdown.
.
Common Intel microcode updates for Linux systems are sent to nearly all Intel processors but may apply to only a subset of processors. It is up to Linux users to verify this = to install or not to install the microcode update. During installation of the microcode update, applicable processors will be updated while non-applicable processors remain unchanged.
... The 20180108 Intel microcode update to patch Spectre2 only applies to Intel processors that are 3rd-gen IvyTown(Xeon), and 4th-gen Haswell (Core i3, i5 and i7) or newer. So, it does not apply to 3rg-gen IvyBridge or older. You have a 2nd-gen Intel SandyBridge processor.
Thanks 'rene' and 'michael louwe' for your explanations.
Unfortunately I had to install Mint 18.0 32-bit because it was impossible to boot my PC with the live-version 64-bit (and nobody helped me in finding a solution). Maybe I could test the last live-version 64-bit of 18.3, but I think that the problem was (and is) on my BIOS (sigh!).
If I understood well, me too I'll receive a kernel pactch and intel microcode for 32-bit, but nobody knows when, because my situation is "low priority". So I have to wait and control Update Manager and Driver Manager in next weeks.
Is this correct?
Thanks a lot for your attention. I appreciated very much.

User avatar
michael louwe
Level 9
Level 9
Posts: 2692
Joined: Sun Sep 11, 2016 11:18 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by michael louwe » Sun Jan 14, 2018 2:24 pm

@ neversaynever, .......
neversaynever wrote:...
.
Users of 32bit systems are made to wait for the Meltdown & Spectre patches because they have minority desktop OS world market share. ["Majority rules".] This was because most new OEM Win 8.x/10 computers since 2012 came with UEFI technology which requires 64bit OS. Hence, Google have stopped supporting 32bit Chrome for Linux since March 2016. Likely, Ubuntu will also stop support for 32bit Ubuntu 18.04 LTS in April 2018.

It's odd that your 2nd-gen Intel Sandybridge processor could not install 64bit LM 18.x. Maybe, it's your BIOS settings. My older 2008 Intel Core2Duo processor can run 64bit Lubuntu 14.04.

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 3:29 pm

@ michael lowve, …..
michael louwe wrote:@ neversaynever, .......
neversaynever wrote:...
...
It's odd that your 2nd-gen Intel Sandybridge processor could not install 64bit LM 18.x. Maybe, it's your BIOS settings. My older 2008 Intel Core2Duo processor can run 64bit Lubuntu 14.04.
Thank you ‘Michael’.
Yes it’s very odd. I could install LM 64-bit on an older machine (Acer Travelmate 6592 dated 2008) with the almost same BIOS (and same settings) of my actual PC (Acer Travelmate 8573TG dated 2012).
On it I use Windows 7 SP1 64-bit (I’m trying to switch from Windows and I don’t want Windows 8 or 10) and Linux Mint 18.0 “32-bit” (unfortunately).
With the live CD 64-bit, after reading for some seconds the CD at boot, the screen remained total black … “forever”; no beeps, no Grub, nothing. Nobody was able to advise me how to solve the problem.
Now if Ubuntu will stop support for 32-bit in 2018 I have to face the problem again or I’ll have to change my PC with a newer one …
If you can advise me a forum of experts on which I can try again to subject my problem, I will be happy.
In two days I leave for two weeks without smart-phone or computer devices to detoxify: but when I’ll come back I could ask for help once more.
Thanks for your attention.

User avatar
Moem
Level 16
Level 16
Posts: 6777
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by Moem » Sun Jan 14, 2018 3:34 pm

neversaynever wrote: Unfortunately I had to install Mint 18.0 32-bit because it was impossible to boot my PC with the live-version 64-bit (and nobody helped me in finding a solution).
I can't find the forum thread where you asked for help with this... am I missing something?
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 4:14 pm

@Moem....
Moem wrote:
neversaynever wrote: Unfortunately I had to install Mint 18.0 32-bit because it was impossible to boot my PC with the live-version 64-bit (and nobody helped me in finding a solution).
I can't find the forum thread where you asked for help with this... am I missing something?
Hi Moem. I asked here: https://forum.ubuntu-it.org/viewtopic.php?f=38&t=613881
I had only one answer, but not very usefull. After testing for a few days, after contacting two 'apparently experts' by phone without usefull solutions, I found that the live 32-bit version was OK. So I installed 32-bit instead of 64: I thought it was almost the same ... but evidently I made a mistake.
Thanks for your attention.

User avatar
Moem
Level 16
Level 16
Posts: 6777
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by Moem » Sun Jan 14, 2018 4:21 pm

neversaynever wrote:Hi Moem. I asked here: https://forum.ubuntu-it.org/viewtopic.php?f=38&t=613881
I had only one answer, but not very usefull.
Okay, so if you're still interested: give us a go, we may be able to help.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 4:43 pm

@Moem ....
Moem wrote:
neversaynever wrote:Hi Moem. I asked here: https://forum.ubuntu-it.org/viewtopic.php?f=38&t=613881
I had only one answer, but not very usefull.
Okay, so if you're still interested: give us a go, we may be able to help.
Thank you very much Moem, i’m still interested.
As I told, in two days I leave for two weeks without smart-phone or computer devices to detoxify: but when I’ll come back, if you tell me where I can post my problem, I will be happy to ask for help again.
Thanks a lot (and sorry for my poor English)

User avatar
michael louwe
Level 9
Level 9
Posts: 2692
Joined: Sun Sep 11, 2016 11:18 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by michael louwe » Sun Jan 14, 2018 4:48 pm

@ neversaynever, .......
neversaynever wrote:...
.
Please check out this link about the 64bit installing problem ... https://ubuntuforums.org/showthread.php?t=2164484

Try installing 64bit in Legacy BIOS mode, ie enable CSM or Legacy BIOS in BIOS setup.(= need to convert disk mode from GPT to MBR/ms-dos)

Seems Virtualization features in BIOS settings can disable 64bit.

User avatar
Moem
Level 16
Level 16
Posts: 6777
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by Moem » Sun Jan 14, 2018 4:53 pm

neversaynever wrote:when I’ll come back, if you tell me where I can post my problem, I will be happy to ask for help again.
The 'Installation and Boot' section comes to mind. Please don't worry about your English, it's fine.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 5:14 pm

@michael louwe....
michael louwe wrote:@ neversaynever, .......

Please check out this link about the 64bit installing problem ... https://ubuntuforums.org/showthread.php?t=2164484
.
Thanks Michael. I apologize and I realized I'm Off Thread: maybe I should post in another Thread, but I don't know where.
I checked out the link, but is too "difficult" for a newbie like me. Maybe is not the same problem because their PC booted, badly (without mouse) but booted. In my case it doesn't boot: it seems blocked with black screen.

neversaynever
Level 1
Level 1
Posts: 20
Joined: Sat Jan 13, 2018 4:26 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by neversaynever » Sun Jan 14, 2018 5:19 pm

Moem wrote:
neversaynever wrote:when I’ll come back, if you tell me where I can post my problem, I will be happy to ask for help again.
The 'Installation and Boot' section comes to mind. Please don't worry about your English, it's fine.
Thanks a lot Moem. I'll open a new trhead in 'Installation and Boot'.
Thank you all. I appreciated your help very much.

rene
Level 8
Level 8
Posts: 2181
Joined: Sun Mar 27, 2016 6:58 pm

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by rene » Sun Jan 14, 2018 6:27 pm

neversaynever wrote:If I understood well, me too I'll receive a kernel pactch and intel microcode for 32-bit, but nobody knows when, because my situation is "low priority". So I have to wait and control Update Manager and Driver Manager in next weeks. Is this correct?
The 32-bit Linux kernel will indeed also be patched for both Meltdown and Spectre, and microcode updates will on a 64-bit capable CPU such as yours in fact likely not discriminate between 64-bit and 32-bit code. Can not at this time find definitive confirmation of that latter statement but something else would seem to technically make limited sense. Microcode updates for your CPU haven't been released yet by Intel, nor are Linux kernel-side changes to make use of them even if they had present in a current "enduser kernel". I do believe that most of that which is coming in that sense is currently present in the still to be released upstream 4.15 kernel...

As to microcode updates for non 64-bit capable x86 CPU's: anything Core 2 and up is 64-bit capable so we're at that point talking about more than 10 year old CPU's; Pentium 4 or Core Duo/Solo at best. Intel might provide a microcode update and an OEM like HP might release new BIOS versions incorporating it for a few select 32-bit business models if they happen to have an important customer still using them, but yes, certainly the least that can be said is that this would be low-priority.

More so in fact because it's unclear if the Pentium 4 architecture even suffers from the problem beyond the generic speculation one; beyond how AMD does. It was at that exact point in time that AMD was kicking major Intel butt per megahertz and it wouldn't surprise me if Intel had introduced their specific additional exposure to the issue as part of the reason why Core 2 then kicked AMD square in the mouth just a bit later. For the lawyer types: that bit's interesting in a class-action lawsuit sense since if the Pentium 4 did the right thing wrt. enforcing memory protection also for speculative code in the manner that AMD has said they have always done, then it can be argued that Intel apparently knew what they were doing when they stopped doing said right thing.

In any case...

What seems to not be making 4.15 is 32-bit versions/equivalents of what is currently already present in the released Ubuntu updates; the Meltdown-mitigating KPTI patches. It's currently being worked on, e.g. https://www.mail-archive.com/linux-kern ... 85332.html, but I would not expect any of that before 4.16. At the earliest, but if the same KPTI principles as on 64-bit can be extended to 32-bit, then probably also at the latest. Regression-testing might take a few folks digging through their basements for 32-bit systems though...

But directly as to your "is that correct?" query then: well, yes, but no in the sense that you should first and foremost try and get a 64-bit system up and running on your 2nd gen. Core i7. The issue is probably that you have a 32-bit UEFI implementation; if you're not dual-booting with Windows or can re-install that as well, certainly booting in legacy mode would be a workaround. Other and/or better workarounds may be available: this forum's "Installation & Boot" section is likely useful in that sense; I don't myself have extensive UEFI experience.

And other than any of the above: please note that while this may all be very entertaining to the technically minded and/or the mindlessly paranoid, none of it will affect you in an actual sense. Exploiting either issue requires on your system executing code, requires "malware". On Linux you are now and were always to a high degree immune to malware even in the general sense; are if you are using a recent patched browser fully immune to dynamic web-content exploits in the meltdown/spectre-specific sense. If you're not in the habit of installing unverified stuff from the internet feel free to just not worry about any of it.

blueredgreen
Level 2
Level 2
Posts: 79
Joined: Sun Jun 17, 2012 12:14 am

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by blueredgreen » Sun Jan 14, 2018 9:33 pm

Microcode update is confusing.

release announcement says
Please use the Update Manager to upgrade intel-microcode to version 3.20180108.0.
Note: If intel-microcode isn’t installed on your computer, run the Driver Manager to see if it’s needed


I turned on level 4 and 5 updates and updated kernel, but did not see any microcode update - driver manager showed the update but did not say it was needed - took a chance and applied it anyway and it now shows up in my package manager, but, if i run

netbook@blueblue ~ $ dmesg | grep microcode
[ 0.000000] microcode: CPU0 microcode updated early to revision 0x4, date = 2013-06-28
[ 0.232267] microcode: CPU2 microcode updated early to revision 0x4, date = 2013-06-28
[ 2.114244] microcode: CPU0 sig=0x20655, pf=0x10, revision=0x4
[ 2.114265] microcode: CPU1 sig=0x20655, pf=0x10, revision=0x4
[ 2.114293] microcode: CPU2 sig=0x20655, pf=0x10, revision=0x4
[ 2.114311] microcode: CPU3 sig=0x20655, pf=0x10, revision=0x4
[ 2.114512] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba

i suspect nothing has updated at all - in terminal, "microcode" is all in red



my cpu is an i3 u 380 and i am not sure if this exact cpu is even affected

netbook@blueblue ~ $ inxi -F
System: Host: blueblue Kernel: 4.4.0-109-generic x86_64 (64 bit)
Desktop: MATE 1.14.1 Distro: Linux Mint 18 Sarah
Machine: System: Acer (portable) product: TravelMate 8172 v: V1.16
Mobo: Acer model: TravelMate 8172 v: PSMBOU-1234567
Bios: Acer v: V1.16 date: 04/28/2011
CPU: Dual core Intel Core i3 U 380 (-HT-MCP-) cache: 3072 KB
clock speeds: max: 1333 MHz 1: 799 MHz 2: 933 MHz 3: 1333 MHz
4: 666 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1366x768@60.00hz
GLX Renderer: Mesa DRI Intel Ironlake Mobile
GLX Version: 2.1 Mesa 11.2.0
Audio: Card Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.4.0-109-generic
Network: Card-1: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express)
driver: ath9k
IF: wlp1s0 state: up mac: c0:f8:da:64:53:2f
Card-2: Broadcom NetXtreme BCM57760 Gigabit Ethernet PCIe
driver: tg3
IF: enp3s0 state: down mac: 00:1e:33:29:c2:ed
Drives: HDD Total Size: 515.7GB (4.3% used)
ID-1: /dev/sda model: WDC_WD5000BPVX size: 500.1GB
ID-2: USB /dev/sdb model: USB_Flash_Memory size: 15.6GB
Partition: ID-1: / size: 455G used: 18G (4%) fs: ext4 dev: /dev/dm-1
ID-2: /boot size: 472M used: 113M (26%) fs: ext2 dev: /dev/sda1
ID-3: swap-1 size: 3.95GB used: 0.00GB (0%) fs: swap dev: /dev/dm-2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 46.0C mobo: 5.8C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 189 Uptime: 41 min Memory: 1385.8/3625.1MB
Client: Shell (bash) inxi: 2.2.35
Image

User avatar
thx-1138
Level 6
Level 6
Posts: 1154
Joined: Fri Mar 10, 2017 12:15 pm
Location: Athens, Greece

Re: ATTN!...Intel CPU owners (Spectre & Meltdown flaws)

Post by thx-1138 » Sun Jan 14, 2018 9:43 pm

blueredgreen, for the microcode update to have an effect:

1) you have to reboot first...and then run dmesg | grep microcode to verify it's date.
2) even then, it might just be that the latest microcode update doesn't yet provide support for your processor; theoritically, it should report a date later then 2017-06-01...

Post Reply

Return to “Open chat”