I run this script
https://github.com/speed47/spectre-meltdown-checker
Code: Select all
CVE-2018-3640 [rogue system register read] aka 'Variant 3a'
* CPU microcode mitigates the vulnerability: NO
> STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)
> How to fix: The microcode of your CPU needs to be upgraded to mitigate this vulnerability. This is usually done at boot time by your kernel (the upgrade is not persistent across reboots which is why it's done at each boot). If you're using a distro, make sure you are up to date, as microcode updates are usually shipped alongside with the distro kernel. Availability of a microcode update for you CPU model depends on your CPU vendor. You can usually find out online if a microcode update is available for your CPU by searching for your CPUID (indicated in the Hardware Check section). The microcode update is enough, there is no additional OS, kernel or software change needed.
Code: Select all
CVE-2018-3639 [speculative store bypass] aka 'Variant 4'
* Mitigated according to the /sys interface: NO (Vulnerable)
* Kernel supports speculation store bypass: YES (found in /proc/self/status)
> STATUS: VULNERABLE (Your CPU doesn't support SSBD)
> How to fix: Your kernel is recent enough to use the CPU microcode features for mitigation, but your CPU microcode doesn't actually provide the necessary features for the kernel to use. The microcode of your CPU hence needs to be upgraded. This is usually done at boot time by your kernel (the upgrade is not persistent across reboots which is why it's done at each boot). If you're using a distro, make sure you are up to date, as microcode updates are usually shipped alongside with the distro kernel. Availability of a microcode update for you CPU model depends on your CPU vendor. You can usually find out online if a microcode update is available for your CPU by searching for your CPUID (indicated in the Hardware Check section).
I have errors with
neko kernel 4.16.18
Code: Select all
ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
ACPI BIOS Error (bug): Failure looking up [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20180105/psargs-364)
ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.SPT1._GTF, AE_NOT_FOUND (20180105/psparse-550)
On my MSI Z170A GAMING PRO CARBON I have this BIOS version - 7A12v1A (Release Date 2018-07-13)
Any suggestions are welcome.
Update. With kernel 4.16.8 by
brokenman I have the same errors
I found this solution here
https://www.linuxquestions.org/question ... ost5707423
I have 2 different Asus(Intel) motherboards that do the same thing with newer kernels. It's nothing to worry about and there is nothing you can
do about it at this point.
Just to give you some background, as you probably know, ACPI is the power regulation code in your motherboard's BIOS/UEFI:
https://en.wikipedia.org/wiki/Advanc...ower_Interface
It's suppose to be a standard that any operating system can properly
implement. However, in typical Microsoft fashion, MS operating systems
do not follow or properly implement the ACPI standard. Instead, MS gives
motherboard manufacturers their own improperly implemented ACPI code
for inclusion in the motherboard BIOS/UEFI. The code runs fine with MS
windows but all for other operating systems like linux there can be
problems. Because of MS's market dominance, the faulty ACPI
implementation from MS has become the de facto industry standard. As a
result, linux and other non-MS operating systems have to reverse
engineer the faulty ACPI implementation from MS. That's why you can see
problems in linux with ACPI related functionality like suspend to ram,
hibernate, etc.
Apparently, the ACPI related code in certain newer linux kernels has a
problem with the typical BIOS/UEFI ACPI implementation on certain
motherboards which is why we're getting those error messages. Even
though I get those error messages at the beginning of the boot process,
I've had no problems with suspend/resume or any other ACPI related
issues. Here's another guy with the same problem so you are not alone:
https://www.reddit.com/r/linux/comme..._installation/
The advice there was to not run in BIOS legacy mode by disabling UEFI
but to run in UEFI mode instead with secure boot disabled. I haven't
bothered with it myself since I have several operating systems already
installed with BIOS legacy mode and I would have to reinstall everything
if I wanted to switch to UEFI mode.
BTW, I use MBR and BIOS legacy mode.
Update. I have done a small test. I switched on UEFI mode in BIOS.
I took USB-Flash drive with one single FAT32 partition and run the Porteus-installer-for-Linux.com
And booted from this USB Flash drive (in UEFI mode) and it's not resolve this issue. I have the same errors.
I am stuck
Отправлено спустя 16 часов 3 минуты 56 секунд:
After updating BIOS to 7A12v1A I have this output:
In GRUB2
Code: Select all
root@porteus:~# grep microcode /proc/cpuinfo
microcode : 0xc6
microcode : 0xc6
microcode : 0xc6
microcode : 0xc6
root@porteus:~# dmesg | grep -i microcode
[ 0.280199] microcode: sig=0x506e3, pf=0x2, revision=0xc6
[ 0.280218] microcode: Microcode Update Driver: v2.2.
[ 3.365087] [drm] Loading bonaire Microcode
root@porteus:~# cat /proc/cmdline
quiet BOOT_IMAGE=/boot/syslinux/vmlinuz changes=/porteus kmap=us,ru
root@porteus:~#
Kernel is Linux 4.16.8-porteus
Code: Select all
./spectre-meltdown-checker.sh
CVE-2018-3639 [speculative store bypass] aka 'Variant 4'
* Kernel supports speculation store bypass: NO
> STATUS: VULNERABLE (your kernel needs to be updated)
CVE-2018-3639 speculative store bypass (Variant 4)
Impact: software using JIT (no known exploitation against kernel)
Mitigation: microcode update + kernel update making possible for affected software to protect itself
Performance impact of the mitigation: low to medium
Now only this vulnerability is open.
Update. I tried kernel 4.18-rc3 by
neko from Porteus-XFCE-v4.0-x86_64-18.07.02.iso
viewtopic.php?p=65413#p65413
and now
Code: Select all
CVE-2018-3639 [speculative store bypass] aka 'Variant 4'
* Mitigated according to the /sys interface: YES (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
* Kernel supports speculation store bypass: YES (found in /proc/self/status)
> STATUS: NOT VULNERABLE (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
but in dmesg (dmesg | grep -i ACPI) with kernel 4.18-rc3 I have this:
Code: Select all
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.534500] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.535086] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.535564] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.536584] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.537228] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT2._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.542265] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT1._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.545523] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20180531/psparse-516)
3ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20180531/psargs-330)
[ 0.547206] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20180531/psparse-516)