[SOLVED] MS Windows programs not responding vs Linux total freeze

mahdi · 2021-12-23 04:51:46

I see in Linux (tested different distros) when a program consume to much CPU whole system freeze, mouse slow down or freeze, ... but as I remember in MS windows only such program window were become not responding, mouse and taskbar still smoothly was working and you could close such program using them without hassle

Same experience or only me? Is there a reason or my incorrect experience

Last edited by mahdi (2022-03-03 18:10:21)

seth · 2021-12-23 09:02:48

It's unlikely that this is a CPU issue but in any event "linux" is not a thing here, it very much depends on the scheduler and also in what process the cursor operates (a compositor might act as a limiting filter here)
https://wiki.archlinux.org/title/Improv … onsiveness
Next to the "niceness" of an offending process, there's https://wiki.archlinux.org/title/Cgroups

Finally, you need to produce some data rather than innuendo - eg. sth. as basic as the cpu load in "top" is going to be much more informative than "i think linux is worse than windows but I also didn't actually test windows"
That's borderline flamebait and prone to get dustbinned - or at the very least TGN

Morn · 2021-12-23 10:06:11

mahdi wrote:

Same experience or only me? Is there a reason or my incorrect experience

You can use ulimit or cpulimit to limit CPU or memory use of a process. But by default, there are no limits, so if a process goes haywire and tries to allocate all available memory, the system grinds to a halt. My personal choice is also not to use swap at all on Linux, which helps somewhat with malfunctioning processes because they soon run out of memory. Having xkill accessible in your WM menu is also helpful, if you can still manage to launch it under heavy resource contention.

I think Windows is indeed a bit more clever than Linux when it comes to automatically detecting a runaway process and dealing with it. If the mouse does not respond anymore on Linux, it's usually time for the hardware off switch because recovering is so difficult.

mahdi · 2022-01-31 06:09:41

My guess was correct it is a bug of Linux and is called priority inversion. Turnning off swap doesn't solve it. NetBSD (or Windows) doesn't have this problem. In NetBSD for example offending process became incredible slow while the OS itself is very responsive.

Last edited by mahdi (2022-01-31 06:59:38)

seth · 2022-01-31 08:19:28

That's not "a bug of Linux" but a general phenomenon and there's ab·so·fuck·ing·lu·te·ly no indication made by you that you're facing anything like this.
If the CPU load is (data pending) the determining factor and you were (data pending) facing a priority inversion then it would be a bug in the scheduler (which you've so far failed to name)

You still need to provide *any* data on the claimed situation but myblind guess is that what's actually stalling is your WM/DE/Compositor of choice.

mahdi · 2022-02-03 14:13:21

below is journalctl after slow down => freeze after opening two relatively heavy programs. I had to hard reboot. I hope journalctl -n 2000 include that time

$ journalctl -n 2000 --no-pager
Feb 03 17:30:54 m-pc systemd[1]: Detected architecture x86-64.
Feb 03 17:30:54 m-pc systemd[1]: Hostname set to <m-pc>.
Feb 03 17:30:54 m-pc kernel: random: lvmconfig: uninitialized urandom read (4 bytes read)
Feb 03 17:30:54 m-pc systemd[1]: Configuration file /etc/systemd/system/piavpn.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Feb 03 17:30:54 m-pc systemd[1]: Queued start job for default target Graphical Interface.
Feb 03 17:30:54 m-pc kernel: random: systemd: uninitialized urandom read (16 bytes read)
Feb 03 17:30:54 m-pc systemd[1]: Created slice Slice /system/getty.
Feb 03 17:30:54 m-pc kernel: random: systemd: uninitialized urandom read (16 bytes read)
Feb 03 17:30:54 m-pc systemd[1]: Created slice Slice /system/modprobe.
Feb 03 17:30:54 m-pc systemd[1]: Created slice User and Session Slice.
Feb 03 17:30:54 m-pc systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Feb 03 17:30:54 m-pc systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Feb 03 17:30:54 m-pc systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Local Encrypted Volumes.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Login Prompts.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Local Integrity Protected Volumes.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Path Units.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Slice Units.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Swaps.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Local Verity Protected Volumes.
Feb 03 17:30:54 m-pc systemd[1]: Listening on Device-mapper event daemon FIFOs.
Feb 03 17:30:54 m-pc systemd[1]: Listening on LVM2 poll daemon socket.
Feb 03 17:30:54 m-pc systemd[1]: Listening on Process Core Dump Socket.
Feb 03 17:30:54 m-pc systemd[1]: Listening on Journal Audit Socket.
Feb 03 17:30:54 m-pc systemd[1]: Listening on Journal Socket (/dev/log).
Feb 03 17:30:54 m-pc systemd[1]: Listening on Journal Socket.
Feb 03 17:30:54 m-pc systemd[1]: Listening on udev Control Socket.
Feb 03 17:30:54 m-pc systemd[1]: Listening on udev Kernel Socket.
Feb 03 17:30:54 m-pc systemd[1]: Mounting Huge Pages File System...
Feb 03 17:30:54 m-pc systemd[1]: Mounting POSIX Message Queue File System...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Kernel Debug File System...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Kernel Trace File System...
Feb 03 17:30:54 m-pc systemd[1]: Starting Create List of Static Device Nodes...
Feb 03 17:30:54 m-pc systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Feb 03 17:30:54 m-pc systemd[1]: Starting Load Kernel Module configfs...
Feb 03 17:30:54 m-pc systemd[1]: Starting Load Kernel Module drm...
Feb 03 17:30:54 m-pc systemd[1]: Starting Load Kernel Module fuse...
Feb 03 17:30:54 m-pc systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
Feb 03 17:30:54 m-pc systemd[1]: Starting Journal Service...
Feb 03 17:30:54 m-pc systemd[1]: Starting Load Kernel Modules...
Feb 03 17:30:54 m-pc systemd[1]: Starting Remount Root and Kernel File Systems...
Feb 03 17:30:54 m-pc systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
Feb 03 17:30:54 m-pc systemd[1]: Starting Coldplug All udev Devices...
Feb 03 17:30:54 m-pc systemd[1]: Mounted Huge Pages File System.
Feb 03 17:30:54 m-pc kernel: EXT4-fs (sda1): re-mounted. Opts: (null). Quota mode: none.
Feb 03 17:30:54 m-pc kernel: Asymmetric key parser 'pkcs8' registered
Feb 03 17:30:54 m-pc systemd[1]: Mounted POSIX Message Queue File System.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Kernel Debug File System.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Kernel Trace File System.
Feb 03 17:30:54 m-pc systemd[1]: Finished Create List of Static Device Nodes.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.206:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.206:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: modprobe@configfs.service: Deactivated successfully.
Feb 03 17:30:54 m-pc systemd[1]: Finished Load Kernel Module configfs.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.209:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc kernel: audit: type=1131 audit(1643896854.209:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: modprobe@drm.service: Deactivated successfully.
Feb 03 17:30:54 m-pc systemd[1]: Finished Load Kernel Module drm.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.209:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc kernel: audit: type=1131 audit(1643896854.209:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Load Kernel Modules.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.213:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Remount Root and Kernel File Systems.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.216:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc kernel: fuse: init (API version 7.35)
Feb 03 17:30:54 m-pc systemd[1]: Mounting Kernel Configuration File System...
Feb 03 17:30:54 m-pc systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
Feb 03 17:30:54 m-pc systemd[1]: Rebuild Hardware Database was skipped because all trigger condition checks failed.
Feb 03 17:30:54 m-pc systemd[1]: Starting Load/Save Random Seed...
Feb 03 17:30:54 m-pc systemd[1]: Starting Apply Kernel Variables...
Feb 03 17:30:54 m-pc systemd[1]: Starting Create System Users...
Feb 03 17:30:54 m-pc systemd[1]: modprobe@fuse.service: Deactivated successfully.
Feb 03 17:30:54 m-pc systemd[1]: Finished Load Kernel Module fuse.
Feb 03 17:30:54 m-pc kernel: audit: type=1130 audit(1643896854.239:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc kernel: audit: type=1131 audit(1643896854.239:11): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Mounting FUSE Control File System...
Feb 03 17:30:54 m-pc kernel: random: crng init done
Feb 03 17:30:54 m-pc kernel: random: 7 urandom warning(s) missed due to ratelimiting
Feb 03 17:30:54 m-pc systemd[1]: Finished Load/Save Random Seed.
Feb 03 17:30:54 m-pc systemd[1]: Finished Apply Kernel Variables.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Kernel Configuration File System.
Feb 03 17:30:54 m-pc systemd[1]: Mounted FUSE Control File System.
Feb 03 17:30:54 m-pc systemd[1]: First Boot Complete was skipped because of a failed condition check (ConditionFirstBoot=yes).
Feb 03 17:30:54 m-pc systemd[1]: Finished Create System Users.
Feb 03 17:30:54 m-pc systemd[1]: Starting Create Static Device Nodes in /dev...
Feb 03 17:30:54 m-pc systemd-journald[216]: Journal started
Feb 03 17:30:54 m-pc systemd-journald[216]: Runtime Journal (/run/log/journal/b568f9c14b124602a542f4fe1d9b3c7f) is 8.0M, max 161.6M, 153.6M free.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Started Journal Service.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd-modules-load[217]: Inserted module 'pkcs8_key_parser'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Starting Flush Journal to Persistent Storage...
Feb 03 17:30:54 m-pc systemd-journald[216]: Time spent on flushing to /var/log/journal/b568f9c14b124602a542f4fe1d9b3c7f is 125.263ms for 786 entries.
Feb 03 17:30:54 m-pc systemd-journald[216]: System Journal (/var/log/journal/b568f9c14b124602a542f4fe1d9b3c7f) is 344.1M, max 4.0G, 3.6G free.
Feb 03 17:30:54 m-pc systemd-journald[216]: Received client request to flush runtime journal.
Feb 03 17:30:54 m-pc kernel: loop: module loaded
Feb 03 17:30:54 m-pc kernel: loop0: detected capacity change from 0 to 8
Feb 03 17:30:54 m-pc kernel: loop3: detected capacity change from 0 to 196800
Feb 03 17:30:54 m-pc kernel: loop1: detected capacity change from 0 to 448512
Feb 03 17:30:54 m-pc kernel: loop2: detected capacity change from 0 to 337424
Feb 03 17:30:54 m-pc kernel: loop4: detected capacity change from 0 to 113680
Feb 03 17:30:54 m-pc kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Feb 03 17:30:54 m-pc kernel: loop5: detected capacity change from 0 to 133552
Feb 03 17:30:54 m-pc kernel: loop6: detected capacity change from 0 to 188704
Feb 03 17:30:54 m-pc kernel: loop7: detected capacity change from 0 to 88952
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit: BPF prog-id=13 op=LOAD
Feb 03 17:30:54 m-pc audit: BPF prog-id=14 op=LOAD
Feb 03 17:30:54 m-pc audit: BPF prog-id=15 op=LOAD
Feb 03 17:30:54 m-pc systemd[1]: Finished Coldplug All udev Devices.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Create Static Device Nodes in /dev.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Preparation for Local File Systems.
Feb 03 17:30:54 m-pc systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
Feb 03 17:30:54 m-pc systemd[1]: Mounting /tmp...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for bare, revision 5...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for beaker-browser, revision 2...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for core18, revision 2284...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for gnome-3-28-1804, revision 161...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for gnome-3-34-1804, revision 77...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1519...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for session-desktop, revision 192...
Feb 03 17:30:54 m-pc systemd[1]: Mounting Mount unit for snapd, revision 14549...
Feb 03 17:30:54 m-pc systemd[1]: Starting Rule-based Manager for Device Events and Files...
Feb 03 17:30:54 m-pc systemd[1]: Mounted /tmp.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for bare, revision 5.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for beaker-browser, revision 2.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for core18, revision 2284.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for gnome-3-28-1804, revision 161.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for gnome-3-34-1804, revision 77.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1519.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for session-desktop, revision 192.
Feb 03 17:30:54 m-pc systemd[1]: Mounted Mount unit for snapd, revision 14549.
Feb 03 17:30:54 m-pc systemd[1]: Reached target Local File Systems.
Feb 03 17:30:54 m-pc systemd[1]: Starting Rebuild Dynamic Linker Cache...
Feb 03 17:30:54 m-pc systemd[1]: Starting Set Up Additional Binary Formats...
Feb 03 17:30:54 m-pc systemd[1]: Store a System Token in an EFI Variable was skipped because of a failed condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Feb 03 17:30:54 m-pc systemd[1]: Commit a transient machine-id on disk was skipped because of a failed condition check (ConditionPathIsMountPoint=/etc/machine-id).
Feb 03 17:30:54 m-pc systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 254 (systemd-binfmt)
Feb 03 17:30:54 m-pc systemd[1]: Finished Flush Journal to Persistent Storage.
Feb 03 17:30:54 m-pc systemd[1]: Starting Create Volatile Files and Directories...
Feb 03 17:30:54 m-pc systemd[1]: Started Rule-based Manager for Device Events and Files.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Rebuild Dynamic Linker Cache.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ldconfig comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Create Volatile Files and Directories.
Feb 03 17:30:54 m-pc systemd[1]: Starting Rebuild Journal Catalog...
Feb 03 17:30:54 m-pc audit: BPF prog-id=16 op=LOAD
Feb 03 17:30:54 m-pc systemd[1]: Starting Network Time Synchronization...
Feb 03 17:30:54 m-pc systemd[1]: Starting Record System Boot/Shutdown in UTMP...
Feb 03 17:30:54 m-pc audit[278]: SYSTEM_BOOT pid=278 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Record System Boot/Shutdown in UTMP.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Rebuild Journal Catalog.
Feb 03 17:30:54 m-pc systemd[1]: Starting Update is Completed...
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-catalog-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 03 17:30:54 m-pc systemd[1]: Finished Update is Completed.
Feb 03 17:30:54 m-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-done comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Last edited by mahdi (2022-02-03 14:16:28)

mahdi · 2022-02-03 14:20:30

Also note `set-cfs-tweaks.service` auto closes.

# systemctl status set-cfs-tweaks.service
○ set-cfs-tweaks.service - Set CFS tweaks
     Loaded: loaded (/usr/lib/systemd/system/set-cfs-tweaks.service; enabled; vendor preset: disabled)
     Active: inactive (dead) since Thu 2022-02-03 17:47:09 +0330; 1min 35s ago
    Process: 4562 ExecStart=/usr/lib/cfs-zen-tweaks/set-cfs-zen-tweaks.bash (code=exited, status=0/SUCCESS)
   Main PID: 4562 (code=exited, status=0/SUCCESS)
        CPU: 51ms

Feb 03 17:47:09 m-pc systemd[1]: Starting Set CFS tweaks...
Feb 03 17:47:09 m-pc set-cfs-zen-tweaks.bash[4562]: Targeted preemption latency for CPU-bound tasks: 4ms
Feb 03 17:47:09 m-pc set-cfs-zen-tweaks.bash[4562]: Minimal preemption granularity for CPU-bound tasks: 0.4ms
Feb 03 17:47:09 m-pc set-cfs-zen-tweaks.bash[4562]: Wake-up granularity: 0.5ms
Feb 03 17:47:09 m-pc set-cfs-zen-tweaks.bash[4562]: Task migration cost: 0.25ms
Feb 03 17:47:09 m-pc set-cfs-zen-tweaks.bash[4562]: Amount of runtime to allocate from global to local pool: 3ms
Feb 03 17:47:09 m-pc systemd[1]: set-cfs-tweaks.service: Deactivated successfully.
Feb 03 17:47:09 m-pc systemd[1]: Finished Set CFS tweaks.

Using Cgroups is too much even for an advanced user

Last edited by mahdi (2022-02-03 21:10:35)

mahdi · 2022-02-24 19:36:30

1- The problem is caused by memory usage not CPU. (I was wrong)
2- I haven't really tested netBSD (too professional) I just copied someone else comment from somewhere.

seth wrote:

myblind guess is that what's actually stalling is your WM/DE/Compositor of choice.

When it happen everything become slow even in Terminal mode (by pressing alt+ctrl+F3) , so I doubt it is WM/DE fault.
What I found out is that only time OOM kilker trigger is by running

$ stress --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2;}' < /proc/meminfo)k --vm-keep -m 1

which cuase complete freeze. In other times regardless how much system become laggy (via openning programs simultaneously), OOM killer would not trigger

Last edited by mahdi (2022-02-24 19:39:24)

seth · 2022-02-28 09:06:58

https://wiki.archlinux.org/title/Improv … conditions
But if you're not actually running OOM but just juggling between swap and RAM, OOM killing isn't necessarily ideal either (because you're killing a used process)
Ad there's no way windows acts better in this case - if you run OOM you run OOM.

Arch Linux

#1 2021-12-23 04:51:46

[SOLVED] MS Windows programs not responding vs Linux total freeze

#2 2021-12-23 09:02:48

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#3 2021-12-23 10:06:11

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#4 2022-01-31 06:09:41

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#5 2022-01-31 08:19:28

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#6 2022-02-03 14:13:21

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#7 2022-02-03 14:20:30

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#8 2022-02-24 19:36:30

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

#9 2022-02-28 09:06:58

Re: [SOLVED] MS Windows programs not responding vs Linux total freeze

Board footer