System issues with the non-LTS kernels

When booting 6.1.10-arch1:

graphical.target @ 27.879s
└─lightdm.service @ 27.500s +336ms
└─systemd-user-sessions.service @ 27.346s +79ms
└─network.target @ 27.280s
└─NetworkManager.service @ 26.768s +487ms
└─network-pre.target @ 26.681s
└─firewalld.service @ 25.104s +1.576s
└─dbus.service @ 20.856s +3.642s
└─basic.target @ 20.641s
└─sockets.target @ 20.633s
└─dbus.socket @ 20.627s
└─sysinit.target @ 20.571s
└─systemd-update-done.service @ 20.150s +413ms
└─systemd-journal-catalog-update.service @ 18.256s +1.796s
└─systemd-tmpfiles-setup.service @ 14.682s +3.441s
└─local-fs.target @ 14.350s
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @ 14.850s
└─local-fs-pre.target @ 5.913s
└─systemd-tmpfiles-setup-dev.service @ 5.249s +663ms
└─systemd-sysusers.service @ 4.158s +1.051s
└─systemd-remount-fs.service @ 2.533s +1.310s
└─systemd-journald.socket @ 2.206s
└─-.mount @ 2.134s
└─-.slice @ 2.131s

Interestingly, now the system is responsive and the Xorg usage is down, but boot times are still long.

Weird. I can understand it somewhat because the zen kernel is optimised for certain things. But i still don’t know why mine only shows a couple entries on this commands and its fast!.

I think you might have the causality backwards here. This is critical chain output, not the entire output.

In other words, the OPs list is probably longer than yours because of the slow boot issue.

I guess i just don’t understand why all the output compared to mine and what is causing it?

Well, yeah, figuring out what is causing it is the hard part.

I’m just thinking in my mind because i don’t understand enough about what could be causing it. So it makes me think even though i don’t know. :rofl:

@theseventhsu

You have the 5700U processor. Are you using grub? Are you using the kernel parameter amd_pstate=passivein command line on boot? Just wondering?

Edit: The 5700U is no slouch so it confuses me why?
Edit2: I guess this wouldn’t matter anyway because this is on virtualbox.

I am using GRUB, but the amd_pstate parameter wasn’t in any of my GRUB configs; I just added it to the linux invocation and attempted to boot with the zen and lts kernels, and it didn’t change the aforementioned performance in any way.

Did you add it in /etc/default/grub to the command line? Then update grub with sudo grub-mkconfig -o /boot/grub/grub.cfg

Then check with

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver

I just updated grub with the method given, but boot performance was even worse on the Zen kernel and the folder cpu0 doesn’t actually contain a folder cpufreq.

Even on a different system that is Intel with Nvidia graphics i get the same output. This is also with zen kernel.

graphical.target @2.499s
└─lightdm.service @2.482s +14ms
  └─systemd-user-sessions.service @2.462s +17ms
    └─nss-user-lookup.target @2.500s

is virtualbox-host-dkms installed or any other in use?

In the host or in virtualbox?

It isn’t on mine on the host. Is this required as i don’t ever use it?

Edit: Okay i always use this one virtualbox-host-modules-arch

the one or the other…but if you have dkms it could fail building modules p.e. and if non of both is installed it will may cause issue too…

virtualbox logs could show some issue also:

Here’re are some VBox logs from when the systme decides to become unresponsive while loading initial ramdisk.

00:00:20.371629 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:21.548261 GIM: KVM: Enabled wall-clock struct. at 0x00000000a8a00000 - u32Sec=1676072490 u32Nano=892110438 uVersion=2
00:00:21.549623 PIT: mode=2 count=0x4a9 (1193) - 1000.15 Hz (ch=0)
00:00:21.702636 PIT: mode=0 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:21.713948 GIM: KVM: VCPU  1: Enabled system-time struct. at 0x00000000a8a01040 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x56d5926ac uVirtNanoTS=0x30555df49 TscKHz=1796566
00:00:21.713980 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:21.725686 GIM: KVM: VCPU  2: Enabled system-time struct. at 0x00000000a8a01080 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x56e9b4600 uVirtNanoTS=0x306092bcf TscKHz=1796566
00:00:21.725717 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:21.733953 GIM: KVM: VCPU  3: Enabled system-time struct. at 0x00000000a8a010c0 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x56f7e088f uVirtNanoTS=0x3068763c3 TscKHz=1796566
00:00:21.733994 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:21.742519 GIM: KVM: VCPU  4: Enabled system-time struct. at 0x00000000a8a01100 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x57068fef0 uVirtNanoTS=0x3070a2c83 TscKHz=1796566
00:00:21.742559 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:21.758946 GIM: KVM: VCPU  5: Enabled system-time struct. at 0x00000000a8a01140 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x5722bab21 uVirtNanoTS=0x3080506ae TscKHz=1796566
00:00:21.758990 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:30.284721 GIM: KVM: VCPU  6: Enabled system-time struct. at 0x00000000a8a01180 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x90324710e uVirtNanoTS=0x504321487 TscKHz=1796566
00:00:30.284758 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:00:30.293856 GIM: KVM: VCPU  7: Enabled system-time struct. at 0x00000000a8a011c0 - u32TscScale=0x8e7e7ab5 i8TscShift=0 uVersion=2 fFlags=0x1 uTsc=0x90419d957 uVirtNanoTS=0x504baad9e TscKHz=1796566
00:00:30.293897 TM: Host/VM is not suitable for using TSC mode 'RealTSCOffset', request to change TSC mode ignored
00:01:47.544138 TM: Giving up catch-up attempt at a 60 002 366 079 ns lag; new total: 60 002 366 079 ns
00:03:01.492064 TM: Giving up catch-up attempt at a 60 001 210 175 ns lag; new total: 120 003 576 254 ns
00:04:19.455320 TM: Giving up catch-up attempt at a 60 001 814 797 ns lag; new total: 180 005 391 051 ns
00:05:38.600800 TM: Giving up catch-up attempt at a 60 000 339 081 ns lag; new total: 240 005 730 132 ns

It seems like the whole system seizes for some reason, and only with this kernel.

Does your extension pack version match?

I don’t have the extension pack installed.

Welcome to the forum! :smile:

Can you show the output of

pacman -Qs virtualbox
id

in both host and guest?

The host is Windows 11, but the guest returned

local/linux 6.1.10.arch1-1
    The Linux kernel and modules
local/linux-lts 5.15.91-4
    The LTS Linux kernel and modules
local/linux-zen 6.1.10.zen1-1
    The Linux ZEN kernel and modules
local/virtualbox-guest-utils 7.0.6-1
    VirtualBox Guest userspace utilities

for the first command and

uid=1000(myusername) gid=1000(myusername) groups=1000(myusername),3(sys),109(vboxsf),982(rfkill),998(wheel)

for the id command.