From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Kernel 4.9.95
Date: Fri, 27 Apr 2018 08:01:09 +0100 [thread overview]
Message-ID: <2881739.bcodu7ZSZg@dell_xps> (raw)
In-Reply-To: <pbud4u$j6$1@blaine.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
On Friday, 27 April 2018 06:42:56 BST Nikos Chantziaras wrote:
> On 26/04/18 14:42, Mick wrote:
> > Hmm ... why is my Intel system missing 'IBPB' & 'IBRS_FW' ?
> >
> > $ grep . /sys/devices/system/cpu/vulnerabilities/*
> > /sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
> > /sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user
> > pointer sanitization
> > /sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full
> > generic
> > retpoline
> >
> > Are there some kernel options I should have selected manually?
>
> Do you have the latest sys-firmware/intel-microcode installed and
> configured correctly? You need to enable the "early microcode" kernel
> option, and you also need to add /boot/intel-uc.img to your list of
> initrds to load in grub2. Alternatively, a BIOS update for your
> mainboard (if one exists; most older mainboards won't get updates from
> the likes of Asus, MSI, Gigabyte, etc, etc, etc, so for older boards,
> you need the microcode package.)
Ahh! If the 'IBPB' & 'IBRS_FW' components come from the microcode this
probably explains why I don't have them. I am (still) running an early i7
Intel, which means it won't get any more microcode updates. The latest
available is 'intel-ucode/06-1e-05' and as we know Intel has abandoned all
older owners of their hardware. One good reason for me to abandon them in
turn. :-)
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-27 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 16:06 [gentoo-user] Kernel 4.9.95 Peter Humphrey
2018-04-26 9:52 ` Helmut Jarausch
2018-04-26 9:57 ` John Covici
2018-04-26 10:13 ` Adam Carter
2018-04-26 10:28 ` Peter Humphrey
2018-04-26 10:43 ` Adam Carter
2018-04-26 11:42 ` Mick
2018-04-27 5:42 ` [gentoo-user] " Nikos Chantziaras
2018-04-27 7:01 ` Mick [this message]
2018-04-27 17:20 ` Klaus Ethgen
2018-04-27 18:51 ` Nikos Chantziaras
2018-04-27 18:53 ` Nikos Chantziaras
2018-04-27 5:44 ` Nikos Chantziaras
2018-04-26 10:15 ` [gentoo-user] " Peter Humphrey
2018-04-26 20:44 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2881739.bcodu7ZSZg@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox