>
> Hmm ... My last line looks the same like Rich's, but different to yours:
>
> # cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> Mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
>
> I don't have IBPB mentioned in there at all. I'm on
> gentoo-sources-4.19.57.
> Are you
On 7/17/19 5:58 AM, Mick wrote:
> Hmm ... My last line looks the same like Rich's, but different to yours:
>
> # cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> Mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
>
> I don't have IBPB mentioned in there at all. I'm on
On Wednesday, 17 July 2019 04:21:07 BST Corbin wrote:
> On 7/14/19 8:26 AM, Mick wrote:
> > Then I came across this old message regarding Piledriver CPUs:
> > https://lists.debian.org/debian-security/2016/03/msg00084.html The
> > post refers to model 2 of cpu family 21. Not all models in the same
On 7/14/19 8:26 AM, Mick wrote:
> Then I came across this old message regarding Piledriver CPUs:
> https://lists.debian.org/debian-security/2016/03/msg00084.html The
> post refers to model 2 of cpu family 21. Not all models in the same
> family, only model 2. So I am thinking although patch
On Sat, 13 Jul 2019 18:18:35 +0100, Mick wrote:
> Anyway, if you want to look at the initramfs contents manually, I
> suppose you will need to decompress your initramfs in a temporary
> directory to see its contents. First find what archive format has been
> used.
>
> file /boot/EFI/...
On Sun, Jul 14, 2019 at 4:06 AM Mick wrote:
> On Saturday, 13 July 2019 18:42:27 BST Jack wrote:
> >
> > If linux-firmware is emerged with the savedconfig use flag, then only
> > the firmware not deleted from the config file is left.
>
> Yes. I used to do this, but gave up after a while.
> Then I came across this old message regarding Piledriver CPUs:
>
> https://lists.debian.org/debian-security/2016/03/msg00084.html
>
> The post refers to model 2 of cpu family 21. Not all models in the same
> family, only model 2. So I am thinking although patch files are named per
> CPU
>
On Saturday, 13 July 2019 23:03:11 BST Mick wrote:
> Unlike my old Intel which lights up like a christmas tree with "Vulnerable,
> no microcode found" because Intel has thrown its users to the kerb, both
> AMDs show "Not Vulnerable" and for some of the vulnerabilities it reports:
>
> (your CPU
On Saturday, 13 July 2019 22:01:02 BST Rich Freeman wrote:
> On Sat, Jul 13, 2019 at 4:16 PM Wols Lists wrote:
> > On 13/07/19 20:23, Mick wrote:
> > > Thanks Corbin, I wonder if despite articles about microcode patch
> > > releases to deal with spectre and what not, there are just no patches
> >
On Sat, Jul 13, 2019 at 4:16 PM Wols Lists wrote:
>
> On 13/07/19 20:23, Mick wrote:
> > Thanks Corbin, I wonder if despite articles about microcode patch releases
> > to
> > deal with spectre and what not, there are just no patches made available for
> > my aging AMD CPUs.
>
> Or Spectre and
On 13/07/19 20:23, Mick wrote:
> Thanks Corbin, I wonder if despite articles about microcode patch releases to
> deal with spectre and what not, there are just no patches made available for
> my aging AMD CPUs.
Or Spectre and what not are Intel specific ...
I know a lot of the reports said
On Saturday, 13 July 2019 19:16:18 BST Corbin wrote:
> For reference, the .config file for the kernel should have something
>
> along the lines of this:
> > #
> > # Firmware loader
> > #
> > CONFIG_FW_LOADER=y
> > CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin
> >
For reference, the .config file for the kernel should have something
along the lines of this:
> #
> # Firmware loader
> #
> CONFIG_FW_LOADER=y
> CONFIG_EXTRA_FIRMWARE="amd-ucode/microcode_amd.bin
> amd-ucode/microcode_amd_fam15h.bin amdgpu/polaris10_ce.bin
> amdgpu/polaris10_ce_2.bin
On Saturday, 13 July 2019 18:42:27 BST Jack wrote:
>
> If linux-firmware is emerged with the savedconfig use flag, then only
> the firmware not deleted from the config file is left.
Yes. I used to do this, but gave up after a while.
> I did find a
> few extras based on the "failed to load..."
On 2019.07.13 13:18, Mick wrote:
On Saturday, 13 July 2019 17:21:40 BST Jack wrote:
> On 2019.07.12 08:18, Mick wrote:
[snip]
And, one question - if I have linux-firmware emerged with
savedconfig use flag set, what's the best/easiest way to hunt
through the actually available firmware,
On Saturday, 13 July 2019 18:18:35 BST Mick wrote:
> or
>
> xv -dc < /boot/EFI/... initramfs-XXX.img | cpio -idmv
Oops! Typo alert! xv should of course be 'xz'. I think you can also use
lzcat.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
On Saturday, 13 July 2019 17:21:40 BST Jack wrote:
> On 2019.07.12 08:18, Mick wrote:
> > https://www.bleepingcomputer.com/news/hardware/amd-releases-spectre-v2-mic
> > rocode-updates-for-cpus-going-back-to-2011/
> I have not yet done any further searching or digging, but that link
> seems to
On 2019.07.12 08:18, Mick wrote:
I'm looking at dmesg output which on my Intel CPUS of various
vintages shows
"microcode updated early ..." but two different AMD APUs of mine do
not show
the same, despite AMD apparently releasing microcode updates going
back to
2011:
I'm looking at dmesg output which on my Intel CPUS of various vintages shows
"microcode updated early ..." but two different AMD APUs of mine do not show
the same, despite AMD apparently releasing microcode updates going back to
2011:
19 matches
Mail list logo
