36 Second Boot Gap on Asus Laptop (Slow boot time)

simonhuang · 2025-07-28 16:09:00

Hi everyone, I noticed that my laptop took a long time to boot my recently installed Arch Linux and a 36 delay during the process:

$ systemd-analyze
Startup finished in 5.721s (firmware) + 7.782s (loader) + 44.140s (kernel) + 2.460s (userspace) = 1min 105ms 
graphical.target reached after 1.705s in userspace.

# dmesg
...
[    1.946679] usb 1-1: SerialNumber: 200901010001
[    1.969696] usb 3-5: New USB device found, idVendor=0489, idProduct=e122, bcdDevice= 0.00
[    1.969707] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.969709] usb 3-5: Product: Bluetooth Radio
[    1.969711] usb 3-5: Manufacturer: Realtek
[    1.969713] usb 3-5: SerialNumber: 00e04c000001
[   37.995856] clk: Disabling unused clocks
[   37.995866] PM: genpd: Disabling unused power domains
[   37.997077] Freeing unused decrypted memory: 2028K
...

As you can see, after the 'usb' sequence, it took around 36 seconds to move on to the 'clk' sequence. Also, I thought that `systemd-analyze blame` and `systemd-analyze critical-chain` showed messages unrelated to the issue:

$ systemd-analyze blame
1.154s asusd.service
 282ms ufw.service
 180ms user@1000.service
 160ms dev-nvme0n1p4.device
 138ms power-profiles-daemon.service
 125ms nftables.service
 104ms iwd.service
  97ms polkit.service
  88ms systemd-networkd-persistent-storage.service
  55ms systemd-journal-flush.service
  50ms systemd-udev-trigger.service
  44ms systemd-tmpfiles-clean.service
  42ms systemd-hostnamed.service
  41ms systemd-vconsole-setup.service
  38ms systemd-backlight@leds:asus::kbd_backlight.service
  36ms systemd-networkd.service
  36ms dev-disk-by\x2duuid-7ce04691\x2d3a8a\x2d4af2\x2d924f\x2d4062c1ef4d7b.swap
  35ms systemd-logind.service
  34ms systemd-tmpfiles-setup-dev-early.service
  31ms systemd-journald.service
  30ms systemd-backlight@backlight:nvidia_0.service
  28ms systemd-backlight@backlight:amdgpu_bl2.service
  28ms systemd-resolved.service
  27ms systemd-update-utmp.service
  27ms user-runtime-dir@1000.service
  24ms systemd-tmpfiles-setup.service
  22ms systemd-user-sessions.service
  22ms boot.mount
  21ms getty@tty1.service
  19ms systemd-udevd.service
  19ms dev-hugepages.mount
  19ms systemd-remount-fs.service
  19ms dev-mqueue.mount
  19ms sys-kernel-debug.mount
  17ms sys-kernel-tracing.mount
  17ms switcheroo-control.service
  16ms kmod-static-nodes.service
  14ms modprobe@configfs.service
  14ms modprobe@drm.service
  13ms systemd-boot-random-seed.service
  13ms modprobe@fuse.service
  13ms systemd-userdbd.service
  12ms tmp.mount
  12ms dbus-broker.service
  10ms systemd-modules-load.service
  10ms systemd-rfkill.service
   9ms systemd-network-generator.service
   9ms systemd-tmpfiles-setup-dev.service
   9ms supergfxd.service
   8ms systemd-sysctl.service
   8ms systemd-udev-load-credentials.service
   5ms modprobe@loop.service
   5ms systemd-random-seed.service
   5ms modprobe@dm_mod.service
   3ms sys-fs-fuse-connections.mount
   3ms sys-kernel-config.mount
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

$ systemd-analyze critical-chain
graphical.target @1.705s
└─power-profiles-daemon.service @1.566s +138ms
  └─multi-user.target @1.565s
    └─getty.target @1.565s
      └─supergfxd.service @1.318s +9ms
        └─basic.target @1.304s
          └─dbus-broker.service @1.289s +12ms
            └─dbus.socket @1.285s
              └─sysinit.target @1.283s
                └─systemd-update-utmp.service @1.255s +27ms
                  └─systemd-tmpfiles-setup.service @1.228s +24ms
                    └─local-fs.target @1.225s
                      └─boot.mount @1.202s +22ms
                        └─dev-nvme0n1p2.device @330ms

I tried to update the BIOS and my Arch, but none has solved the issue. This is driving me crazy. I appreciate any possible solutions!

The system information of my device:

#inxi -Fxpmrz
Linux arda 6.15.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 24 Jul 2025 18:18:11 +0000 x86_64 GNU/Linux
System:
  Kernel: 6.15.8-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
  Console: tty 1 Distro: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK product: ASUS TUF Gaming A14 FA401KM_FA401KM v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: FA401KM v: 1.0 serial: <superuser required> UEFI: American Megatrends
    LLC. v: FA401KM.303 date: 06/16/2025
Battery:
  ID-1: BAT0 charge: 28.4 Wh (39.0%) condition: 72.8/73.0 Wh (99.8%) volts: 14.9 min: 15.9
    model: AS3GYRE3KC GA40347 status: discharging
Memory:
  System RAM: total: 32 GiB available: 30.47 GiB used: 1.07 GiB (3.5%)
  Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: None max-module-size: 16 GiB note: est.
  Device-1: Channel-A DIMM 0 type: LPDDR5 size: 8 GiB speed: 7500 MT/s
  Device-2: Channel-B DIMM 0 type: LPDDR5 size: 8 GiB speed: 7500 MT/s
  Device-3: Channel-C DIMM 0 type: LPDDR5 size: 8 GiB speed: 7500 MT/s
  Device-4: Channel-D DIMM 0 type: LPDDR5 size: 8 GiB speed: 7500 MT/s
CPU:
  Info: 8-core model: AMD Ryzen AI 7 350 w/ Radeon 860M bits: 64 type: MT MCP arch: N/A rev: 0
    cache: L1: 640 KiB L2: 8 MiB L3: 16 MiB
  Speed (MHz): avg: 623 min/max: 623/5091:3506 boost: enabled cores: 1: 623 2: 623 3: 623 4: 623
    5: 623 6: 623 7: 623 8: 623 9: 623 10: 623 11: 623 12: 623 13: 623 14: 623 15: 623 16: 623
    bogomips: 63879
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GB206M [GeForce RTX 5060 Max-Q / Mobile] vendor: ASUSTeK driver: nvidia
    v: 575.64.05 bus-ID: 64:00.0
  Device-2: Advanced Micro Devices [AMD/ATI] Krackan [Radeon 840M / 860M Graphics]
    vendor: ASUSTeK driver: amdgpu v: kernel bus-ID: 66:00.0 temp: 31.0 C
  Device-3: Shinetech ASUS FHD webcam driver: uvcvideo type: USB bus-ID: 1-1:2
  Display: unspecified server: N/A driver: gpu: amdgpu tty: 160x50 resolution: 2560x1600
  API: N/A Message: No API data available in console. Headless machine?
  Info: Tools: gpu: nvidia-smi,radeontop
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel bus-ID: 64:00.1
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio [Rembrandt/Strix]
    vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 66:00.1
  Device-3: Advanced Micro Devices [AMD] Audio Coprocessor vendor: ASUSTeK driver: snd_acp_pci
    v: kernel bus-ID: 66:00.5
  Device-4: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel bus-ID: 66:00.6
  API: ALSA v: k6.15.8-arch1-1 status: kernel-api
Network:
  Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network vendor: Foxconn driver: rtw89_8852ce
    v: kernel port: f000 bus-ID: 63:00.0
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB bus-ID: 3-5:2
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: not found rfk-block: hardware: no
    software: no address: see --recommends
Drives:
  Local Storage: total: 1.89 TiB used: 9.04 GiB (0.5%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WD PC SN5000S SDEQNSJ-1T00-1002
    size: 953.87 GiB temp: 32.9 C
  ID-2: /dev/nvme1n1 vendor: Kingston model: SKC3000S1024G size: 953.87 GiB temp: 49.9 C
  ID-3: /dev/sda vendor: SanDisk model: USB 3.2Gen1 size: 28.67 GiB type: USB
Partition:
  ID-1: / size: 901.39 GiB used: 6.51 GiB (0.7%) fs: ext4 dev: /dev/nvme1n1p4
  ID-2: /boot size: 1022 MiB used: 378.3 MiB (37.0%) fs: vfat dev: /dev/nvme1n1p2
  ID-3: /mnt/usb size: 28.66 GiB used: 2.17 GiB (7.6%) fs: vfat dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 36 GiB used: 0 KiB (0.0%) dev: /dev/nvme1n1p3
Sensors:
  System Temperatures: cpu: N/A mobo: N/A
  Fan Speeds (rpm): cpu: 2400 fan-1: 2460
Repos:
...
Info:
  Processes: 303 Uptime: 5m Init: systemd
  Compilers: gcc: 15.1.1 Shell: Zsh v: 5.9 inxi: 3.3.38

The full `dmesg` output can be found here.

seth · 2025-07-28 16:14:03

[    1.969713] usb 3-5: SerialNumber: 00e04c000001
[   37.995856] clk: Disabling unused clocks

doesn't indicate any kind of boot delay.
From what you've shown this is probably some userspace issue, probably w/ the display server starting.
Please post your complete system journal for the boot:

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

simonhuang · 2025-07-29 01:58:43

Thanks for the reply! Here is the full journalctl -b output.

But isn't the output of `systemd-analyze` showing `kernel (44s)` is kinda long for a new device and for a newly installed arch? I saw many people on the internet had way faster time than my device.

simonhuang · 2025-07-29 02:00:57

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

I should have quoted it in the previous reply. Here is the full journalctl -b output. Thanks again!

seth · 2025-07-29 06:09:08

I should have quoted it in the previous reply.

Not sure what you mean by that but please don't bump - edit your previous post if you want to mend it and nobody has yet replied

Jul 29 16:51:21 arda kernel: Linux version 6.15.8-arch1-1 (linux@archlinux) (gcc (GCC) 15.1.1 20250425, GNU ld (GNU Binutils) 2.44.0) #1 SMP PREEMPT_DYNAMIC Thu, 24 Jul 2025 18:18:11 +0000
Jul 29 16:51:21 arda kernel: Command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root=UUID=a594919b-d2d0-4d5f-a765-5d8025c6e775 rw acpi_backlight=native
…
Jul 29 16:51:21 arda kernel: usb 3-5: new full-speed USB device number 2 using xhci_hcd
Jul 29 16:51:21 arda kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
Jul 29 16:51:21 arda kernel: usb 1-1: New USB device found, idVendor=3277, idProduct=0096, bcdDevice= 0.04
Jul 29 16:51:21 arda kernel: usb 1-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Jul 29 16:51:21 arda kernel: usb 1-1: Product: ASUS FHD webcam
Jul 29 16:51:21 arda kernel: usb 1-1: Manufacturer: Shinetech
Jul 29 16:51:21 arda kernel: usb 1-1: SerialNumber: 200901010001
Jul 29 16:51:21 arda kernel: usb 3-5: New USB device found, idVendor=0489, idProduct=e122, bcdDevice= 0.00
Jul 29 16:51:21 arda kernel: usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 16:51:21 arda kernel: usb 3-5: Product: Bluetooth Radio
Jul 29 16:51:21 arda kernel: usb 3-5: Manufacturer: Realtek
Jul 29 16:51:21 arda kernel: usb 3-5: SerialNumber: 00e04c000001
Jul 29 16:51:21 arda kernel: clk: Disabling unused clocks
Jul 29 16:51:21 arda kernel: PM: genpd: Disabling unused power domains
Jul 29 16:51:21 arda kernel: Freeing unused decrypted memory: 2028K
Jul 29 16:51:21 arda kernel: Freeing unused kernel image (initmem) memory: 4644K
…
Jul 29 16:51:22 arda systemd[1]: Reached target Graphical Interface.
…
Jul 29 16:51:23 arda asusd[880]: [INFO  asusd::aura_manager] Found 1 valid devices on startup
Jul 29 16:51:23 arda systemd[1]: Started ASUS Notebook Control.
Jul 29 16:51:23 arda asusd[880]: [INFO  asusd] Startup success, begining dbus server loop
Jul 29 16:51:23 arda systemd[1]: Startup finished in 5.616s (firmware) + 2.185s (loader) + 44.310s (kernel) + 2.475s (userspace) = 54.587s.
Jul 29 16:51:24 arda systemd-networkd[753]: wlan0: Gained IPv6LL
Jul 29 16:51:25 arda systemd-networkd[753]: wlan0: DHCPv4 address 192.168.8.181/24, gateway 192.168.8.1 acquired from 192.168.8.1
…
Jul 29 16:51:33 arda systemd-logind[682]: New session 1 of user supercat.

The gap in your dmesg output isn't reflected in the journal, but the calls indeed all happen during the initramfs phase.

Jul 29 16:51:21 arda kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jul 29 16:51:21 arda kernel:  nvme0n1: p1 p2 p3 p4
Jul 29 16:51:21 arda kernel: nvme nvme1: allocated 64 MiB host memory buffer (1 segment).
Jul 29 16:51:21 arda kernel: nvme nvme1: 16/0/0 default/read/poll queues
Jul 29 16:51:21 arda kernel:  nvme1n1: p1 p2 p3 p4 p5 p6 p7

Parallel windows?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

If that's not it (though the usb device there is bluetooth) and the boot indeed takes almost a minute on a wall clock, can you disable the BT device in the UEFI settings?

simonhuang · 2025-07-29 15:50:02

seth wrote:

Parallel windows?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I now have the fast start disabled and reboot the two OS twice, but the boot time is still the same. After logging back to linux and re-run `journatlctl -b`, these types of messages remain:

Jul 29 16:51:21 arda kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jul 29 16:51:21 arda kernel:  nvme0n1: p1 p2 p3 p4
Jul 29 16:51:21 arda kernel: nvme nvme1: allocated 64 MiB host memory buffer (1 segment).
Jul 29 16:51:21 arda kernel: nvme nvme1: 16/0/0 default/read/poll queues
Jul 29 16:51:21 arda kernel:  nvme1n1: p1 p2 p3 p4 p5 p6 p7

I just want to mention that my Windows and Arch were installed on separate SSDs.

seth wrote:

If that's not it (though the usb device there is bluetooth) and the boot indeed takes almost a minute on a wall clock, can you disable the BT device in the UEFI settings?

Unfortunately, the Asus Bios setting on my device does not come with the functionality.

seth · 2025-07-29 16:39:47

I just want to mention that my Windows and Arch were installed on separate SSDs.

That's not relevant as long as both OS operate on the same ACPI; the journal lines are innocuous - they just suggested there might be a second OS.

Just to be sure (because of the contradicting logs): when you boot the system and look at it, it does stall between

[    1.969713] usb 3-5: SerialNumber: 00e04c000001

and

[   37.995856] clk: Disabling unused clocks

(and this isn't just a clock jump)?

simonhuang · 2025-07-29 17:07:52

seth wrote:

I just want to mention that my Windows and Arch were installed on separate SSDs.
That's not relevant as long as both OS operate on the same ACPI; the journal lines are innocuous - they just suggested there might be a second OS.
Just to be sure (because of the contradicting logs): when you boot the system and look at it, it does stall between
[    1.969713] usb 3-5: SerialNumber: 00e04c000001
and
[   37.995856] clk: Disabling unused clocks
(and this isn't just a clock jump)?

Based on what I saw when turning on my Arch, the screen first shows

ACPI BIOS ERROR (bug): Failure creating named object ...

,followed by "

ACPI Error: AE_ALREADY_EXISTS. During name lookup/catalog ...

.
My laptop basically just stalled for quite a bit before entering the booting sequence, where the bunch of "[OK] ..." appeared.

seth · 2025-07-29 19:58:07

https://wiki.archlinux.org/title/Genera … l_messages - see whether you can get a better hold on where exactly the stall occurs.
Also test the behavior of the LTS kernel.

What's odd about your system is the vga setup,
There's an https://linux-hardware.org/?id=pci:1002-1114-17aa-3815 but it doesn't show up as vga device
And an https://linux-hardware.org/?id=pci:10de-2d59-1028-0d34 but w/o any outputs attached.
And supergfxctl get a bit confused about the setup (after the root switch, but we don't really know where you're stalling)
The AMDGPU ultimately becomes card2, the nvidia one is card1… what happens if you add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters to block the simpledrm device?

Did you recently change anything about the setup? (In the UEFI)

simonhuang · 2025-07-30 12:04:17

seth wrote:

https://wiki.archlinux.org/title/Genera … l_messages - see whether you can get a better hold on where exactly the stall occurs.
Also test the behavior of the LTS kernel.

I added `debug` to my systemd-boot file, arch.config. The stall basically happened after the USB 3-5 was completed. My linux is currently running `linux-lts` now. But the startup time was the same. (Hope the procedure is correct: I installed linux-lts and linux-lts-headers (for the Nvidia driver) through pacman. Edit the config file of systemd-boot, and remove linux and linux-headers.

seth wrote:

What's odd about your system is the vga setup,
There's an https://linux-hardware.org/?id=pci:1002-1114-17aa-3815 but it doesn't show up as vga device
And an https://linux-hardware.org/?id=pci:10de-2d59-1028-0d34 but w/o any outputs attached.
And supergfxctl get a bit confused about the setup (after the root switch, but we don't really know where you're stalling)
The AMDGPU ultimately becomes card2, the nvidia one is card1… what happens if you add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters to block the simpledrm device?

I added `nvidia_drm.modeset=1` to my `arch.config` file. The startup time was still slow.

seth wrote:

Did you recently change anything about the setup? (In the UEFI)

I disabled secure boot and fast boot in the BIOS setting. Previously, I tried to enable secure boot on Arch, and removed the platform key from my BIOS. However, I found it troublesome to implement. So I have restored the platform key to factory setting from the BIOS, and reinstalled my Arch. These are the changes that I have done.

There was one thing that I changed that I did not mention as I believed to be irrelevant. I added `acpi_backlight=native` to my `arch.config`.

seth · 2025-07-30 14:52:41

The stall basically happened after the USB 3-5 was completed.

This is "on-sight"? Not from dmesg?
Otherwise…

I disabled … fast boot in the BIOS setting

What happens if you undo that? (It's not relevant to the windows fast-start condition. If that's the only thing you change, you did wrong)

simonhuang · 2025-07-30 16:43:16

My arch.conf

$ cat /boot/loader/entries/arch.conf
title     Arch Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx rw acpi_backlight=native

where I left out my UUID.

seth wrote:

This is "on-sight"? Not from dmesg?

Yes, when I added `debug` at the end of `options` of my arch.conf, the dmesg messages showed up on screen, and I saw the system actually stalled after showing the USB messages.

seth wrote:

What happens if you undo that? (It's not relevant to the windows fast-start condition. If that's the only thing you change, you did wrong)

Now, I re-enabled it, but it still took 44 sec to boot the kernel alone according to systemd-analyze.

seth · 2025-07-30 22:04:11

"root=UUID=a594919b-d2d0-4d5f-a765-5d8025c6e775" - the UUID isn't sensitive data, it exists to allow deterministic reference to the partition.

https://forums.unraid.net/topic/191749- … ed-clocks/
https://blog.dowhile0.org/2024/06/02/so … er-issues/

What happens if you add

clk_ignore_unused

to the https://wiki.archlinux.org/title/Kernel_parameters ?

tp_printk trace_event=clk:clk_disable

shall debug what's being disabled and might then expose the offender.

simonhuang · 2025-07-31 16:30:55

seth wrote:

"root=UUID=a594919b-d2d0-4d5f-a765-5d8025c6e775" - the UUID isn't sensitive data, it exists to allow deterministic reference to the partition.
https://forums.unraid.net/topic/191749- … ed-clocks/
https://blog.dowhile0.org/2024/06/02/so … er-issues/
What happens if you add
clk_ignore_unused
to the https://wiki.archlinux.org/title/Kernel_parameters ?
tp_printk trace_event=clk:clk_disable
shall debug what's being disabled and might then expose the offender.

Here is the journalctl with these parameters added to my `arch.conf`. What I noticed is that every `clk` is somewhat connected to `AMDI0010:00`.

seth · 2025-07-31 20:33:10

"clk_ignore_unused", NOT "clk_ignore_used"
https://docs.kernel.org/driver-api/clk. … sed-clocks

The idea would be that either "clk_ignore_unused" would prevent the stall or "tp_printk trace_event=clk:clk_disable" would expose the troublesome one - did it stall w/ a specific one?

On a formal note: please avoid bloating the thread with pointless full-quotes of previous posts. Thanks.

simonhuang · 2025-08-01 02:08:25

I have updated the kernel parameter and put the result in the same link.

simonhuang · 2025-08-01 02:49:22

I added `initcall_debug` to the `arch.conf`. The result could be found here.
I suspect the delay could happened at

[   38.311612] initcall acpi_gpio_handle_deferred_request_irqs+0x0/0x70 returned 0 after 36641074 usecs

which matches the time when my kernel stalled.

Last edited by simonhuang (2025-08-01 04:20:07)

seth · 2025-08-01 08:00:03

Yeah, that's 36s… remove "acpi_backlight=native" again…

simonhuang · 2025-08-01 11:36:33

My `arch.conf` is now:

$ cat /boot/loader/entries/arch.conf
title     Arch Linux
linux   /vmlinuz-linux-lts
initrd  /initramfs-linux-lts.img
options root=UUID=a594919b-d2d0-4d5f-a765-5d8025c6e775 rw clk_ignore_unused initcall_debug

After removing `acpi_backlight=native`,

[   38.311612] initcall acpi_gpio_handle_deferred_request_irqs+0x0/0x70 returned 0 after 36641074 usecs

still remains.

seth · 2025-08-02 20:29:54

Edit: sorry - wrong thread.

Does "acpi=noirq" or "acpi=rsdt" have any impact?

Last edited by seth (2025-08-02 20:32:15)

simonhuang · 2025-08-04 02:55:05

After adding `acpi=noirq`, my keyboard is disabled. Adding `acpi=rsdt` didn't solve the problem as well. Perhaps a BIOS bug then?

seth · 2025-08-04 06:43:59

The delay remains despite "acpi=noirq" (keyboard or not)?

acpi_osi=! acpi_osi="Windows 2015"

https://learn.microsoft.com/en-us/windo … inacpi-osi

Also, sanity check: same delay when booting some live distro (grml or the arch install iso) from a USB key (not the same drive you're currently using)?

simonhuang · 2025-08-04 13:31:18

By adding "acpi=noirq", the delay remains and the keyboard was deactivated.
By adding the kernel parameter:

$cat /boot/loader/entries/arch.conf
title     Arch Linux
linux   /vmlinuz-linux-lts
initrd  /initramfs-linux-lts.img
options root=UUID=a594919b-d2d0-4d5f-a765-5d8025c6e775 rw initcall_debug acpi_osi=! acpi_osi="Windows 2015"

the 36 sec is still there. BTW, am I missing any kernel perimeter?

I also checked booting the installation ISO from my USB, the stalling is there as well.

Mengsk8086 · 2025-08-22 12:43:34

I'm on the same boat, I did the full acpi_gpio_handle_deferred_request_irqs tracing : https://gist.github.com/HiFiPhile/324c3 … f2aff7bb6c

If I read the trace correctly, most of the time is spent on acpi_ex_system_do_sleep ? like the sleep is came from ACPI parsing, wouch a ACPI dump help ?

Mengsk8086 · 2025-08-24 14:54:41

So I've decompiled the DSDT and found the delay came from this function:

Method (NOD2, 1, Serialized)
{
If ((IVGA == Zero))
{
If ((Arg0 != RDNT))
{
Local0 = Zero
Local1 = DNOT /* \_SB_.PCI0.SBRG.DNOT */
DNOT = Arg0
RDNT = Zero
While ((Arg0 != RDNT))
{
If ((Local0 >= 0x0f))
{
DNOT = Local1
Break
}

Notify (^^GPP9.PEGP, Arg0)
Local0++
Local2 = (Local0 * 0x64)
Sleep (Local2)
}
}
}
}

I don't know what it does, but once I reduced the loop from 0x0f to 0x08 and enabled ACPI override the boot speed is much quicker.

I'd be appreciated if anyone could check the DSDT (dsdt_org.dat in the gist above) and propose a proper fix

Arch Linux

#1 2025-07-28 16:09:00

36 Second Boot Gap on Asus Laptop (Slow boot time)

#2 2025-07-28 16:14:03

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#3 2025-07-29 01:58:43

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#4 2025-07-29 02:00:57

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#5 2025-07-29 06:09:08

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#6 2025-07-29 15:50:02

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#7 2025-07-29 16:39:47

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#8 2025-07-29 17:07:52

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#9 2025-07-29 19:58:07

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#10 2025-07-30 12:04:17

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#11 2025-07-30 14:52:41

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#12 2025-07-30 16:43:16

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#13 2025-07-30 22:04:11

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#14 2025-07-31 16:30:55

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#15 2025-07-31 20:33:10

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#16 2025-08-01 02:08:25

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#17 2025-08-01 02:49:22

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#18 2025-08-01 08:00:03

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#19 2025-08-01 11:36:33

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#20 2025-08-02 20:29:54

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#21 2025-08-04 02:55:05

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#22 2025-08-04 06:43:59

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#23 2025-08-04 13:31:18

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#24 2025-08-22 12:43:34

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

#25 2025-08-24 14:54:41

Re: 36 Second Boot Gap on Asus Laptop (Slow boot time)

Board footer