Question Very long boot time

[Concelma]

Hello,

I have a PC that takes a very long to start:
Easily 1-2 minutes until the monitor turns on and shows the "Press F2 for UEFI" etc. screen.

After that I can access the UEFI or boot the installed OS.
Then everything works just fine... mostly. The mouse hangs and lags a little.

But sometimes the monitor doesn't turn on and I have to force shutdown by holding the power button.

Since the problem sits before the UEFI stage I have no idea where to start debugging.
I hope you can maybe guide me into the right direction.

Here is some information about the affected system. If you need anything else, please tell me.

Hardware

• i7-11700K
• 2x 8GB RAM (XMP enabled @2400MHz)
• ASRock H570M-ITX/ac
• Samsung 970 Evo Plus 500 GB NVMe
• Samsung 850 Evo 250 GB SATA
• Samsung 850 Pro 128 GB SATA
• No dedicated GPU installed

The PC is connected via DisplayPort and USB to this DeLOCK DisplayPort 8K KVM Switch.
Also connected to the switch is a Dell U4021QW 5120x2160 monitor.
Mouse, keyboard and a small DAC headphone amp are connected to the monitor's USB hub and the hub is connected to the KVM switch.
So that I can switch mouse, keyboard, audio and monitor input with a single key.

The other PC connected to the KVM switch is running perfectly fine.

Since I got some weird mouse laggs I suspect it could have something to do with the switch setup.
So I tried disconnecting the USB cable from the PC. (Only DisplayPort connected)
But it didn't help.

 

[punkncat]

I would offer a couple of simple things to try next time you can get in BIOS and/or Windows.

When in BIOS check to be sure what your boot order is. Disable everything else. Just remember you did that before you try to boot from a USB next.
Disable any Fast Boot options. I want to say there is something in BIOS as well as a setting inside OS but might be recalling incorrectly on that.

 

[Concelma]

Thanks for the reply.

• The OS drive is the only entry in the boot order
• Fast boot is already disabled

In the UEFI I noticed the following:
Under "Advanced > USB Configuration" it says "4 keyboards, 3 mice, 9 hubs".
That's definitely not the amount of devices connected.

I also noticed that the RAM shows up as 2133MHz, but with enabled XMP it targets 2400MHz.
I've kept XMP enabled but set it manually to 2133MHz.

Also I've set the option "DRAM gear mode" from gear2 to auto.
(Not sure why it was on gear2, because most other settings are on auto by default)

The installed OS is not Windows but Debian Linux.
I've noticed the following messages in my Xorg.log:

[  2019.235] (EE) event10 - Lioncast LK20 keybord Lioncast LK20 keybord: client bug: event processing lagging behind by 15ms, your system is too slow
[  2100.941] (EE) event10 - Lioncast LK20 keybord Lioncast LK20 keybord: client bug: event processing lagging behind by 33ms, your system is too slow
[  6948.278] (EE) event15 - Logitech MX Master: client bug: event processing lagging behind by 14ms, your system is too slow
[  6948.446] (EE) event15 - Logitech MX Master: client bug: event processing lagging behind by 22ms, your system is too slow
[  6950.250] (EE) event15 - Logitech MX Master: client bug: event processing lagging behind by 14ms, your system is too slow
[  6950.250] (EE) event15 - Logitech MX Master: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
[  8050.316] (EE) client bug: timer event15 debounce:       scheduled expiry is in the past (-11ms), your system is too slow
[  8050.316] (EE) client bug: timer event15 debounce short: scheduled expiry is in the past (-25ms), your system is too slow
[  8064.372] (EE) client bug: timer event15 debounce short: scheduled expiry is in the past (-12ms), your system is too slow
[  8066.272] (EE) client bug: timer event15 debounce:       scheduled expiry is in the past (-3ms),  your system is too slow

Could have something to do with the mouse lag.
I did some research but most answers suggest to just ignore these messages...

Actually after changing the settings above, the PC booted normal twice in a row.
Not sure if its finally solved tho...