1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Real fixes for Spectre and Meltdown?

Discussion in 'General Linux Discussion' started by cloasters, Jan 9, 2018.

  1. ThunderRd

    ThunderRd Irreverent Query Chairman Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    1,875
    Likes Received:
    65
    Trophy Points:
    48
    Location:
    Northern Thailand, the Land of Smiles
    Home page:
    Yeah, that's better; it might not actually say 'microcode updated'

    George, I gave you too many terms to grep for in that command, use Kaitain's.
  2. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    Very interesting! Thank you Kaitain! No, the previous response had no "microcode updated" all of the return is there in post #39.


    myname@myname ~ $ sudo dmesg | grep -i "microcode"
    [sudo] password for myname:
    [ 0.665048] microcode: CPU0 sig=0x506e3, pf=0x2, revision=0x23
    [ 0.665052] microcode: CPU1 sig=0x506e3, pf=0x2, revision=0x23
    [ 0.665103] microcode: CPU2 sig=0x506e3, pf=0x2, revision=0x23
    [ 0.665133] microcode: CPU3 sig=0x506e3, pf=0x2, revision=0x23
    [ 0.665247] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
    myname@myname ~ $

    Hmm, the four "microcode" responses starting with[ 0.665048]" have "microcode" in red. Dun, duhn, duhn.
  3. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    Thank you ThunderRd! Kaitain's suggestion worked. Some of the response as noted in post #42 was in red. A bit disconcerting, what?

    I'm reluctant to update the microcode using any of Intel's updates released so far. Linus sez they hain't no good.
    But what do I know? See how it's blank after the first question mark?
  4. ThunderRd

    ThunderRd Irreverent Query Chairman Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    1,875
    Likes Received:
    65
    Trophy Points:
    48
    Location:
    Northern Thailand, the Land of Smiles
    Home page:
    It's perfect. You're done.

    The word 'microcode' appears in red because that is the word we grepped for with the command. It's perfectly normal.

    You are as updated as you can be at this time. We just have to watch for other updates as time goes on.
    Last edited: Jan 31, 2018
  5. Gizmo

    Gizmo Chief Site Administrator Staff Member

    Joined:
    Dec 6, 2012
    Messages:
    2,073
    Likes Received:
    117
    Trophy Points:
    63
    Location:
    Webb City, Missouri
    Home page:
    I've got some Lynnfield Xeons (Nehalem cores) that are showing:

    [ 0.000000] microcode: microcode updated early to revision 0x7, date = 2013-08-20
    [ 0.402263] microcode: sig=0x106e5, pf=0x2, revision=0x7
    [ 0.402402] microcode: Microcode Update Driver: v2.2.

    With the latest updates, so apparently there hasn't been a microcode update for the old stuff yet.
  6. ThunderRd

    ThunderRd Irreverent Query Chairman Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    1,875
    Likes Received:
    65
    Trophy Points:
    48
    Location:
    Northern Thailand, the Land of Smiles
    Home page:
    And mine is even older than yours; I've never updated the microcode on this CPU:

    [ 0.000000] microcode: microcode updated early to revision 0x60f, date = 2010-09-29
    [ 0.232309] microcode: sig=0x10676, pf=0x10, revision=0x60f
    [ 0.234050] microcode: Microcode Update Driver: v2.2.

    There were some updates applied, but none from the newest bundle. We just have to wait and see.
  7. Gizmo

    Gizmo Chief Site Administrator Staff Member

    Joined:
    Dec 6, 2012
    Messages:
    2,073
    Likes Received:
    117
    Trophy Points:
    63
    Location:
    Webb City, Missouri
    Home page:
    I've also got a Sandy Bridge system that has firmware 2013-06-12.
  8. Kaitain

    Kaitain Active Member

    Joined:
    Jul 24, 2016
    Messages:
    349
    Likes Received:
    27
    Trophy Points:
    28
    At least the Intel patch loader tells you that, the AMD one gives something like:

    [ 2.116002] microcode: CPU0: patch_level=0x08101004
    [ 2.116019] microcode: CPU1: patch_level=0x08101004
    [ 2.116050] microcode: CPU2: patch_level=0x08101004
    [ 2.116077] microcode: CPU3: patch_level=0x08101004
    [ 2.116088] microcode: CPU4: patch_level=0x08101004
    [ 2.116113] microcode: CPU5: patch_level=0x08101004
    [ 2.116148] microcode: CPU6: patch_level=0x08101004
    [ 2.116169] microcode: CPU7: patch_level=0x08101004
    [ 2.116256] microcode: Microcode Update Driver: v2.2.
    Slightly more helpful that a teapot made of chocolate... but only marginally so
  9. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48

    Xeons, always desired never genuinely needed for me. I think these security holes were wanted by the powers that be, Intel was only too happy to comply. I could be wrong, always.
  10. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48

    Thank you VERY much ThunderRd! Good to know that red means grepped for and not "prepare for the final trump" as one of PG Wodehouse's characters was fond of saying. Nothing to do with the Capitalized name at all.
  11. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    Thank you for your help with this knotty subject, Kaitain!
    "Teapot made of chocolate," that's a great saying that's of course new to me.
    Sorry that AMD can be seen as worse than Intel about this. Go AMD! Boo you know who!
    Last edited: Feb 1, 2018
  12. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48

    I think, forget aboud it. All of those Intel procs are hard to keep track of. AMD for me next time.
  13. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    6,836
    Likes Received:
    99
    Trophy Points:
    48
    Location:
    Greenwater WA
    Home page:
    Guys Mint installs micro code in Drivers manger (Main Menu)

    "sudo apt-get install -s intel-microcode"
    It says I'm already updated.

    As far a the kernel goes the newest offered by Mint 18.3 i is 4.13.0-36, I'm at 410.0-36 should I install the newest?


    . Screenshot from 2018-02-22 12-39-20.png

    Attached Files:

    Last edited: Feb 22, 2018
  14. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    6,836
    Likes Received:
    99
    Trophy Points:
    48
    Location:
    Greenwater WA
    Home page:
    I tried installing kernel 4.13.0-36.... It claimed to fail, but now says I'm using it and standing tall...I'll keep a watch on future updates for our kernels...go figure! ":O}

    Unless all gathered here think I need a more aggressive approach?
  15. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    6,836
    Likes Received:
    99
    Trophy Points:
    48
    Location:
    Greenwater WA
    Home page:
    Hmmmm

    I tried to follow with an install of a class 1 office update ...fell on it's face

    E: linux-image-extra-4.13.0-36-generic: subprocess installed post-installation script returned error exit status 1

    So here's what it wants to tell me...can some one translate for me?

    (Reading database ... 438830 files and directories currently installed.)
    Preparing to unpack .../libreoffice-ogltrans_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-ogltrans (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../ure_5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking ure (5.1.6~rc2-0ubuntu1~xenial3) over (5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../uno-libs3_5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking uno-libs3 (5.1.6~rc2-0ubuntu1~xenial3) over (5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-calc_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-calc (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-impress_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-impress (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-draw_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-draw (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-gnome_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-gtk_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-gtk (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-writer_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-writer (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../python3-uno_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking python3-uno (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-sdbc-hsqldb_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-sdbc-hsqldb (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-sdbc-firebird_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-sdbc-firebird (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-java-common_1%3a5.1.6~rc2-0ubuntu1~xenial3_all.deb ...
    Unpacking libreoffice-java-common (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-common_1%3a5.1.6~rc2-0ubuntu1~xenial3_all.deb ...
    Unpacking libreoffice-common (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-pdfimport_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-pdfimport (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-math_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-math (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-base-core_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-base-core (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-avmedia-backend-gstreamer_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-avmedia-backend-gstreamer (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-base_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-base (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-core_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-core (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../libreoffice-base-drivers_1%3a5.1.6~rc2-0ubuntu1~xenial3_amd64.deb ...
    Unpacking libreoffice-base-drivers (1:5.1.6~rc2-0ubuntu1~xenial3) over (1:5.1.6~rc2-0ubuntu1~xenial2) ...
    Preparing to unpack .../fonts-opensymbol_2%3a102.7+LibO5.1.6~rc2-0ubuntu1~xenial3_all.deb ...
    Unpacking fonts-opensymbol (2:102.7+LibO5.1.6~rc2-0ubuntu1~xenial3) over (2:102.7+LibO5.1.6~rc2-0ubuntu1~xenial2) ...
    Processing triggers for libc-bin (2.23-0ubuntu10) ...
    Processing triggers for mime-support (3.59ubuntu1) ...
    Processing triggers for desktop-file-utils (0.22+linuxmint1) ...
    Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
    Processing triggers for man-db (2.7.5-1) ...
    Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
    Processing triggers for gnome-icon-theme (3.12.0-1ubuntu3) ...
    Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
    Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
    Setting up linux-image-extra-4.13.0-36-generic (4.13.0-36.40~16.04.1) ...
    run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    Error! Bad return status for module build on kernel: 4.13.0-36-generic (x86_64)
    Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.
    run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    update-initramfs: Generating /boot/initrd.img-4.13.0-36-generic
    Warning: No support for locale: en_US.utf8

    gzip: stdout: No space left on device
    E: mkinitramfs failure cpio 141 gzip 1
    update-initramfs: failed for /boot/initrd.img-4.13.0-36-generic with 1.
    run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
    dpkg: error processing package linux-image-extra-4.13.0-36-generic (--configure):
    subprocess installed post-installation script returned error exit status 1
    Setting up uno-libs3 (5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up ure (5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-common (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Installing new version of config file /etc/bash_completion.d/libreoffice.sh ...
    Setting up fonts-opensymbol (2:102.7+LibO5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-core (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-draw (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-impress (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-ogltrans (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-base-core (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-calc (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-gtk (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-writer (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up python3-uno (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-java-common (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-sdbc-hsqldb (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-sdbc-firebird (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-pdfimport (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-math (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-avmedia-backend-gstreamer (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-base-drivers (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Setting up libreoffice-base (1:5.1.6~rc2-0ubuntu1~xenial3) ...
    Processing triggers for libc-bin (2.23-0ubuntu10) ...
    Errors were encountered while processing:
    linux-image-extra-4.13.0-36-generic
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install. Trying to recover:
    Setting up linux-image-extra-4.13.0-36-generic (4.13.0-36.40~16.04.1) ...
    run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    Error! Bad return status for module build on kernel: 4.13.0-36-generic (x86_64)
    Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information.
    run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-36-generic /boot/vmlinuz-4.13.0-36-generic
    update-initramfs: Generating /boot/initrd.img-4.13.0-36-generic
    Warning: No support for locale: en_US.utf8

    gzip: stdout: No space left on device
    cpio: write error: Broken pipe
    E: mkinitramfs failure cpio 1 gzip 1
    update-initramfs: failed for /boot/initrd.img-4.13.0-36-generic with 1.
    run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
    dpkg: error processing package linux-image-extra-4.13.0-36-generic (--configure):
    subprocess installed post-installation script returned error exit status 1
    Errors were encountered while processing:
    linux-image-extra-4.13.0-36-generic
  16. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    Wow! I am so stoked! Intel just released ANOTHER update to ""fix"" Spectre. I sure ain't gonna go after it. Up your's Schmintel, lyin' sacks of nevermind!
  17. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    6,836
    Likes Received:
    99
    Trophy Points:
    48
    Location:
    Greenwater WA
    Home page:
    Personally I think the world is judging Intel to harshly,

    This is a mistake made while giving us truly kick-ass performance. I make bigger mistakes every day...it' just that my mistakes don't walk out into the world effecting the great unwashed a Intel's do.
    Remember how teeny tiny the mistake they made was (literally) We can't even see it and point and say" there it is!!!"

    Look how many years no one even noticed it!

    On the other hand when did anyone gain kick-a performance from me?
    If we want the big leap, we must accept that we will fall on our face from time to time.

    or...

    whose got the band-aids?
  18. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    Perhaps we are being too hard on Intel. B-B-but it's a huge corporation, always demanding of our scrutiny and ripe for condemnation at all times.
    But seriously, I think Mister Gummint told them to put the security flaws in their processors. And being good corporate citizens(of the rich, by the rich, for the rich) they responded "how high Master?"

    Of course I could be wrong about this. And many other things as well.
  19. Daniel~

    Daniel~ Chief BBS Administrator Staff Member

    Joined:
    Dec 17, 2012
    Messages:
    6,836
    Likes Received:
    99
    Trophy Points:
    48
    Location:
    Greenwater WA
    Home page:
    The rich have to use these processors too and they have much more to hide.":O}
  20. cloasters

    cloasters Well-Known Member

    Joined:
    Jul 3, 2013
    Messages:
    2,982
    Likes Received:
    52
    Trophy Points:
    48
    And can afford the best security people to look after their interests 24/7. Dang it, I'm unable to cut the rich any slack atm.

Share This Page