[SOLVED] Problems with ACPI/APST during boot make boot times slow

DarkReaper231 · 2023-07-30 15:21:22

My Arch installation takes different times to boot because at the boot, I get these errors:

ata2 revalidation failed (errno=-5)
ata2 revalidation failed (errno=-5) 
nvme failed to set APST feature
ata2 EH pending after 5 tries, giving up
ata2 revalidation failed (errno=-5)
ata2 revalidation failed (errno=-5)
ata2 failed to IDENTIFY after ACPI commands
ata2 revalidation failed (errno=-5)
ata2 revalidation failed (errno=-5)
ata2 failed to IDENTIFY after ACPI commands

This goes for different times with each boot. Sometimes it's longer, sometimes it's shorter. Eventually it continues to boot as normal.
Sometimes I get only single revalidation failed (errno=-5) message with no APST or ACPI errors and it boots fast.
Other times it takes from seconds to whole minute.
The system always boots eventually, never have I ever had issue where it just didn't boot at all but it is annoying.

I was trying to find solutions on the internet but I never quite found any post that would describe this exact issue.

How can I solve this?

EDIT 1: ata2 is CD/DVD, I didn't realize it's written there until now. So this is problem with CD/DVD drive.
EDIT 2: It's my nvme drive that fails to set APST feature, not the optical drive. This is the drive I have Windows on, it is accessible from Nautilus tho and this error occurs only once so not sure how much of an issue is it
EDIT 3: ata2 issues were caused by wrongly seated power cable

Last edited by DarkReaper231 (2023-07-31 21:09:55)

seth · 2023-07-30 15:53:32

Please don't post random lines out of context, that's completely meaningless.
Post your complete system journal for the boot:

sudo journalctl -b | curl -F 'f:1=<-' ix.io

DarkReaper231 · 2023-07-30 16:11:32

seth wrote:

Please don't post random lines out of context, that's completely meaningless.
Post your complete system journal for the boot:
sudo journalctl -b | curl -F 'f:1=<-' ix.io

I did that because I can't locate a single log that would contain it so I just took a photo a wrote it down.
The command you provided returned no output.

seth · 2023-07-30 16:14:51

You get a URL from that, just tested, works here (though another thread indicates the same)

The journal will most likely still reveal stalls, so try

sudo journalctl -b | curl -F 'file=@-' 0x0.st

DarkReaper231 · 2023-07-30 16:17:38

seth wrote:

You get a URL from that, just tested, works here (though another thread indicates the same)
The journal will most likely still reveal stalls, so try
sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/H2Bh.txt
I can see it is doing SATA link up hell a lot of times and sometimes it's followed by revalidation failed

Last edited by DarkReaper231 (2023-07-30 16:20:16)

DarkReaper231 · 2023-07-31 14:04:10

Okay yesterday was fun. Someone in some forum had somewhat similar issue and recommended BIOS update. That didn't go well. None of the versions worked except the original one. It just wouldn't get past the BIOS splash screen, even the bios boot menu just showed the menu itself when selecting an entry and would get stuck. Thankfully BIOS was still functional so I tested earlier versions and came to the conclusion eventually that no version worked so I reverted back to the original version.

When I did come back I quickly realized that the BIOS update nicely NUKED my EFI partition. Whole grub was done. So I entered archiso and tried salvaging the partition and just reinstalled grub. That worked for two boots but then during boot I got error in the verbose log saying that it cannot recognize the file system on that partition as vfat. So I had to reformat the partition and try again. But this time grub wasn't recognized by BIOS so eventually I tried --removable which worked. Very nice experience, took me about 5 hours to get back into working state. I still have some oddities now.

Oddity 1: The Xubuntu partition type is now called Microsoft basic data instead of Linux file system, this is also caused by the BIOS update somehow and I am not entirely sure how to fix this. It doesn't cause any issues tho so it's fine I guess.

Oddity 2: grub's mkconfig now somehow detects Windows and Xubuntu without having os-prober enabled. This didn't work before this whole mess up. I had to enable os-prober to detect Xubuntu and do the trick with mounting Windows's efi and file system partition to /mnt in order to have that entry. I no longer have to do this for whatever reason.

Oddity 3: Also every single entry in grub has like 5 duplicates. Not sure why, nor where is it getting those entries from.

So if someone recommends BIOS updates, they are out of questions. BIOS updates are broken on my machine. Not sure why but best guess is hardware compatibility with newer versions.

PS: If someone can help me fix those oddities, it would be nice.

Last edited by DarkReaper231 (2023-07-31 14:05:34)

seth · 2023-07-31 14:22:24

Sorry, didn't see your yesterdays update.
There're obvious issues w/ the optical drive (ata2.00/sr0)

Did you run the BIOS update from windows?
Btw, 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

DarkReaper231 · 2023-07-31 15:20:52

seth wrote:

Sorry, didn't see your yesterdays update.
There're obvious issues w/ the optical drive (ata2.00/sr0)
Did you run the BIOS update from windows?
Btw, 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I ran the BIOS update using M-FLASH on the USB. No version other than the factory one works properly so I am not doing BIOS updates again on this machine.
Btw I fixed the partition type by unchecking msftdata flag in gparted. Grub duplicates were caused by grub-customizer. Had to uninstall it and delete /etc/grub.d and reinstall grub to create it again.
Now it doesn't detect other operating systems without os-prober and there are no duplicates.

What do you mean by issues with ata2? That is CD/DVD drive. What is wrong with it?

DarkReaper231 · 2023-07-31 15:25:47

Oooooh sorry for me being stupid. I never read what is in front of the revalidation errors. It shows ata2, I didn't know what ata2 means until now. It's CD/DVD drive.
I updated the original post for more clarity.

Last edited by DarkReaper231 (2023-07-31 15:26:10)

seth · 2023-07-31 15:39:23

Can you disable the dvd drive in the UEFI?
Is there a disc inside?
Otherwise what if you put a disc into it?

DarkReaper231 · 2023-07-31 16:20:21

I'll answer those questions in a minute but there is one more edit

It's my nvme drive that fails to set APST feature, not the optical drive. This is the drive I have Windows on, it is accessible from Nautilus tho and this error occurs only once so not sure how much of an issue is it
I tried this but it did not work so I'll just leave it as is for now:

nvme_core.default_ps_max_latency_us=1000

DarkReaper231 · 2023-07-31 16:41:21

seth wrote:

Can you disable the dvd drive in the UEFI?
Is there a disc inside?
Otherwise what if you put a disc into it?

Okay umm. On Windows the drive always worked. On Linux when I tried to open it, it closed right after plus all the errors during boot.
I unplugged the power cable and the SATA cable and the errors were gone. I plugged it back in and the errors are still gone. The drive now opens and stays open.
I guess it was just power cable not being seated correctly. Before making this post I only pushed the SATA cable to make sure it's seated, not the power cable leading into the optical drive.

The nvme still fails to set APST feature.

nvme nvme0: failed to set APST feature (2)

but it is accessible from Nautilus and Windows boots correctly on it

Also there are other errros that I kinda blamed on the optical drive but they persist. All of them are APST related.

x86/cpu: SGX disabled by BIOS.
ACPI Error: Aborting method \_SB.PCI0.SPI1.FPNT._CBS due to previous errors (AE_AML_INVALID_RESOURCE_TYPE) (20230331/psparse-529)
ACPI Error: Method execution failed \_SB.PCI0.SPI1.FPNT._CBS due to previous errors (AE_AML_INVALID_RESOURCE_TYPE) (20230331/uteval-68)
ACPI Error: Aborting method \_SB.PCI0.SPI2.FPNT._CBS due to previous errors (AE_AML_INVALID_RESOURCE_TYPE) (20230331/psparse-529)
ACPI Error: Method execution failed \_SB.PCI0.SPI2.FPNT._CBS due to previous errors (AE_AML_INVALID_RESOURCE_TYPE) (20230331/uteval-68)
:: running early hook [udev]
Starting systemd-udevd version 253.7-1-arch
:: running hook [udev]
:: Triggering uevents...
nvme nvme0: failed to set APST feature (2)

http://0x0.st/H2en.txt

The ACPI errors are apparently caused by MSI being bad and prefering Windows, says friend of mine so the only issue remaining is the nvme if that's the case
Optical drive issue is resolved, it was caused by wrongly seated power cable, all grub issues after broken BIOS update are also resolved

Last edited by DarkReaper231 (2023-07-31 16:55:43)

seth · 2023-07-31 19:21:20

"nvme_core.default_ps_max_latency_us=0", but that's unlikely caused any further issues?

There's also no real stall in the boot - just a lot going on.
I'd disable containerd for a test (and w/ it likely dnsmasq/-dhcpcd)

ACPI errors are common across board vendors because they implement ACPI by poking around until windows stop crashing. Reading specs is boring

DarkReaper231 · 2023-07-31 20:06:35

seth wrote:

"nvme_core.default_ps_max_latency_us=0", but that's unlikely caused any further issues?
There's also no real stall in the boot - just a lot going on.
I'd disable containerd for a test (and w/ it likely dnsmasq/-dhcpcd)
ACPI errors are common across board vendors because they implement ACPI by poking around until windows stop crashing. Reading specs is boring

The stall was caused by the optical drive errors, it sometimes took just few seconds, but sometimes it was constantly revalidating for a minute

seth · 2023-07-31 20:11:54

So… is there a remaining issue?

DarkReaper231 · 2023-07-31 21:09:30

seth wrote:

So… is there a remaining issue?

Everything is is alright now, thanks a lot for the help

Btw if anyone ever finds themself with nuked EFI partition, just reformat it, reinstall grub and you're good to go
If grub-customizer causes duplicates, delete /etc/grub.d and then reinstall grub

Arch Linux

#1 2023-07-30 15:21:22

[SOLVED] Problems with ACPI/APST during boot make boot times slow

#2 2023-07-30 15:53:32

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#3 2023-07-30 16:11:32

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#4 2023-07-30 16:14:51

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#5 2023-07-30 16:17:38

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#6 2023-07-31 14:04:10

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#7 2023-07-31 14:22:24

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#8 2023-07-31 15:20:52

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#9 2023-07-31 15:25:47

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#10 2023-07-31 15:39:23

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#11 2023-07-31 16:20:21

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#12 2023-07-31 16:41:21

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#13 2023-07-31 19:21:20

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#14 2023-07-31 20:06:35

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#15 2023-07-31 20:11:54

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

#16 2023-07-31 21:09:30

Re: [SOLVED] Problems with ACPI/APST during boot make boot times slow

Board footer