Arch Linux

xigua

Member

Registered: 2023-07-07

Posts: 3

[SOLVED] increased boot time from "boot.mount" IdeaPad 5 Pro (14ACN6)

I have been running arch on a Lenovo IdeaPad 5 Pro (14ACN6) as my daily driver for over 6 months with no problems. My SSD is setup as LVM on LUKS. In the past the time between me unlocking the LUKS partition and KDE being fully booted up and ready to use has been almost negligible (< 5 seconds). Yet starting this morning it consistently takes upwards of 30 seconds. Running systemd-analyze yields:

Startup finished in 3.658s (firmware) + 4.257s (loader) + 16.362s (kernel) + 26.303s (userspace)
= 50.581s  
graphical.target reached after 26.279s in userspace.

Neither yay or pacman are configured to update automatically and I installed/updated no new packages (or made any substantial changes) before the issue appeared. I have restored to a previous Timeshift snapshot from over a month ago and the issue still persists on the previously working backup.

Looking at the plot from system-analyze, everything in userspace takes negligible time to boot, except "boot.mount" which consistently takes ~ 24 seconds. I am not familiar with what "boot.mount" is and was not able to find much online. My best guess is simply the mounting of /boot. However in this regard I included /boot in my Timeshift snapshot, so I am not sure why the problem would persist with the old snapshot.

Last (hopefully unrelated) information:

The trackpad on the computer also stopped working earlier today without any prior symptoms. It now does not react to touching/scrolling/clicking/anything at all. In KDE settings it simply says "No Touchpad Found". Additionally when booting into BIOS menu or from live USB it still does not function at all or show any signs of being physically there.

For the past week I have been using a different charger than the normal stock one, however this charger has the exact same Amp, Voltage, and Max Wattage output as the stock one. No signs of it rejecting the charger or overheating. Further the battery health was previously and still is at 92%.

Besides these two issues the performance and speed of the computer are exactly the same as before. I see no way the boot time could be a purely hardware issue, but I thought I should mention it regardless.

Any help is appreciated. Thank you.

Last edited by xigua (2023-07-08 18:36:01)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,845

Re: [SOLVED] increased boot time from "boot.mount" IdeaPad 5 Pro (14ACN6)

according to [1] systemd boot.mount is created by systemd-fstab-generator[2] .

However before systemd-fstab-generator runs several other generators have already run.

Are you using a GPT partioned disk ?
If yes, there might be a conflict between the systemd-gpt-auto-generator[3] and your fstab entry .

On the other hand the touchpad issue suggests hardware trouble .

Check your journal / dmesg output for disk errors and other suspicious messages thoroughly (don't grep them , study the whole output) .
Please also post them and your /etc/fstab .

Welcome to archlinux forums

[1] https://unix.stackexchange.com/question … tor#332797
[2] https://man.archlinux.org/man/systemd-f … rator.8.en
[3] https://man.archlinux.org/man/systemd-g … rator.8.en

Last edited by Lone_Wolf (2023-07-08 10:23:49)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,601

Re: [SOLVED] increased boot time from "boot.mount" IdeaPad 5 Pro (14ACN6)

What is the output of systemd-analyze critical-chain --no-pager   ?

Do you dual boot with Microsoft Windows?

Last edited by ewaller (2023-07-08 15:39:26)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

xigua

Member

Registered: 2023-07-07

Posts: 3

Re: [SOLVED] increased boot time from "boot.mount" IdeaPad 5 Pro (14ACN6)

Thank you for the suggestions and info.

After looking through the journal output more thoroughly today, I found the section: 

 
Jul 08 10:30:05 comp systemd[1]: Mounting /boot...
Jul 08 10:30:05 comp systemd[1]: Mounting /home...
Jul 08 10:30:05 comp kernel: EXT4-fs (dm-3): mounted filesystem e8c7a2ad-d7ee-4561-b0e7-0d4538d>
Jul 08 10:30:05 comp systemd[1]: Mounted /home.
Jul 08 10:30:10 comp kernel: i2c_hid_acpi i2c-MSFT0004:00: failed to reset device: -61
Jul 08 10:30:16 comp kernel: i2c_hid_acpi i2c-MSFT0004:00: failed to reset device: -61
Jul 08 10:30:22 comp kernel: i2c_hid_acpi i2c-MSFT0004:00: failed to reset device: -61
Jul 08 10:30:28 comp kernel: i2c_hid_acpi i2c-MSFT0004:00: failed to reset device: -61
Jul 08 10:30:29 comp kernel: i2c_hid_acpi i2c-MSFT0004:00: can't add hid device: -61
Jul 08 10:30:29 comp kernel: i2c_hid_acpi: probe of i2c-MSFT0004:00 failed with error -61
Jul 08 10:30:29 comp kernel: sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
Jul 08 10:30:29 comp kernel: sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
Jul 08 10:30:29 comp kernel: sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
Jul 08 10:30:29 comp kernel: snd_rn_pci_acp3x 0000:04:00.5: enabling device (0000 -> 0002)
Jul 08 10:30:29 comp kernel: videodev: Linux video capture interface: v2.00
Jul 08 10:30:29 comp systemd[1]: Mounted /boot.

the i2c_hid_acpi module seems to be the culprit, attempting to reset/connect to the touchpad a total of four times every six seconds.

blacklisting the i2c_hid_acpi module solved the boot time problem. thus it seems that the touchpad hardware is in fact damaged and that was the root of the problem.