Fedora 30 vmlinuz crashing on every boot

I’ve installed Fedora 30 alongside Windows 10

and vmlinuz is crashing on every boot.

I’ve read the previous posts concerning the nouveau drivers.

But in my case, I do not have a dedicated gpu on my laptop.

dmsg is

    [    0.000000] Linux version 5.1.17-300.fc30.x86_64 (mockbuild@bkernel03.phx2.fedoraproject.org) (gcc version 9.1.1 20190503 (Red Hat 9.1.1-1) (GCC)) #1 SMP Wed Jul 10 15:20:27 UTC 2019
    [    0.000000] Command line: BOOT_IMAGE=(hd0,gpt5)/vmlinuz-5.1.17-300.fc30.x86_64 root=/dev/mapper/fedora-root ro resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet

    [    0.000000] NX (Execute Disable) protection: active
    [    0.000000] efi: EFI v2.60 by Lenovo
    [    0.000000] secureboot: Secure boot disabled
    [    0.000000] SMBIOS 3.1.1 present.
    [    0.000000] DMI: LENOVO 20QDA005KR/20QDA005KR, BIOS N2HET21W (1.04 ) 06/03/2019

    [    0.606147] ACPI: Added _OSI(Module Device)
    [    0.606148] ACPI: Added _OSI(Processor Device)
    [    0.606149] ACPI: Added _OSI(3.0 _SCP Extensions)
    [    0.606151] ACPI: Added _OSI(Processor Aggregator Device)
    [    0.606153] ACPI: Added _OSI(Linux-Dell-Video)
    [    0.606154] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
    [    0.606156] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
    [    0.695098] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.RP14.PXSX.WIST], AE_NOT_FOUND (20190215/psargs-330)
    [    0.695105] ACPI: Ignoring error and continuing table load
    [    0.695106] ACPI Error: Skipping While/If block (20190215/psloop-427)
    [    0.698639] ACPI: 12 ACPI AML tables successfully acquired and loaded
    [    0.700371] ACPI: EC: EC started
    [    0.700372] ACPI: EC: interrupt blocked
    [    0.702895] ACPI: \: Used as first EC
    [    0.702896] ACPI: \: GPE=0x16, EC_CMD/EC_SC=0x66, EC_DATA=0x62
    [    0.702897] ACPI: EC: Boot ECDT EC used to handle transactions
    [    0.706367] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
    [    0.774231] ACPI: Dynamic OEM Table Load:

I’ve tried to snip areas on the log that seems pertinent.

I am totally lost and what to do

Generally, ACPI errors are not system halting since they relate (usually) to the format of the table not being 100% as expected according to industry standard defined (not sure which standard specifically). So this is an extract from ‘journalctl boot’ command I assume, can you provide more? Possibly use pastebin and provide a link to it, it would help to see more info. Do you make it into the emergency shell (dracut)?
[EDIT]: Sorry the command is ‘journalctl -b’

1 Like

Aside the error notification, everything else seems to be working fine.

The error output of journalctl -b is here.

So, do I understand correctly that you are able to run your system, and it all seems to work okay? If that is the case, and yes the ACPI errors can and do happen, then you are likely fine to continue. There is a table that is stored in BIOS’s that it is referring to, which helps OS’s map IO of the hardware. Not all hardware MFG’s treat this table standard as a must follow, more like a nice to have. The caveats are that you may not have reliable metric’s from the BIOS to exploit the full potential of your CPU if you wanted to overclock as one example. The output of the boot log you pasted would seem to support the premise your system is OK and your kernel is not “crashing” (if it crashes there is usually quite a number of errors reported in the log).