Since Stable update 2022-07-18 & 2022-07-12, my system has high IO lag for first operations

Support
1

Since the stable update from 2022-07-18, my system somehow has high lag for IO operations, which were not there before the update and i cannot seem to figure out where the problem is.

System:
Linux Manjaro (21.3.4)
KDE Plasma Wayland 5.24.5 → 5.24.6
Pipewire 0.3.54 → 0.3.55
Kernel 5.18.10 5.18.7 → 5.18.12
Running on a SATA SSD

and i know it is not my hardware failing, because this io latency / lag was not be fore the update.

most noticeable is the IO lag when opening Firefox, Terminal (Konsole with zsh) and general KDE operations (like opening the start-menu).

this io latency / lag sometimes just makes the application load longer (case for Konsole), but for some others it completely freezes the display output until the IO happens (KDE operations and sometimes when starting / doing something in firefox)

2

Hi @hasezoey,

In order for us, or anyone for that matter, to be able to provide assistance, more information is necessary. To that end, please see:

Hope you manage!

Tip:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```

pasted text

```

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Thereby improving legibility and making it much easier for those trying to be of assistance.

Please edit your post accordingly.

P.S.:

I’m no expert and this might be completely wrong, but I see in your profile you use wayland, and that’s not ready AFAIK. Especially not with KDE (which I also saw you use.) So that might be the reason, I don’t know.

3

thanks, forgot to include inxi:

System:
  Kernel: 5.18.12-3-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-5.18-x86_64
    root=UUID=f91dda9e-f6f6-4c52-a22a-a3140000f9ce rw rootflags=subvol=@ quiet
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.24.6 tk: Qt v: 5.15.5 wm: kwin_wayland vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: MSI product: MS-7972 v: 2.0
    serial: <superuser required>
  Mobo: MSI model: B150M MORTAR (MS-7972) v: 2.0
    serial: <superuser required> UEFI: American Megatrends v: C.D0
    date: 06/27/2018
Battery:
  ID-1: hidpp_battery_0 charge: 88% condition: N/A volts: 4.1 min: N/A
    model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
    serial: <filter> status: discharging
Memory:
  RAM: total: 31.23 GiB used: 5.25 GiB (16.8%)
  RAM Report:
    permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-7700K bits: 64 type: MT MCP arch: Kaby Lake
    gen: core 7 built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158)
    stepping: 9 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 800 min/max: 800/4500 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
    8: 800 bogomips: 67224
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush clflushopt
    cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts
    ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase fxsr ht
    hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida intel_pt invpcid
    invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr mtrr
    nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
    pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep smap
    smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow
    tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave
    xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
    mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Micro-Star MSI driver: i915
    v: kernel arch: Gen9.5 process: Intel 14nm built: 2016-20 ports:
    active: none empty: DP-1, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0
    chip-ID: 8086:5912 class-ID: 0380
  Device-2: AMD Vega 10 XL/XT [Radeon RX 56/64] vendor: ASUSTeK
    driver: amdgpu v: kernel arch: GCN 5 process: GF 14nm built: 2017-20 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 ports: active: DP-2,DP-3,HDMI-A-4
    empty: DVI-D-1,HDMI-A-5 bus-ID: 03:00.0 chip-ID: 1002:687f class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.3
    compositor: kwin_wayland driver: X: loaded: amdgpu,modesetting
    alternate: fbdev,vesa gpu: i915,amdgpu d-rect: 6400x1440 display-ID: 0
  Monitor-1: DP-2 pos: center res: 2560x1440 size: N/A modes: N/A
  Monitor-2: DP-3 pos: right res: 1920x1080 size: N/A modes: N/A
  Monitor-3: HDMI-A-4 pos: primary,left res: 1920x1080 size: N/A modes: N/A
  OpenGL:
    renderer: AMD Radeon RX Vega (vega10 LLVM 14.0.6 DRM 3.46 5.18.12-3-MANJARO)
    v: 4.6 Mesa 22.1.3 direct render: Yes
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio
    vendor: Micro-Star MSI driver: snd_hda_intel bus-ID: 1-3:5 v: kernel
    chip-ID: 0b05:1876 bus-ID: 00:1f.3 class-ID: 0300 chip-ID: 8086:a170
    class-ID: 0403 serial: <filter>
  Device-2: AMD Vega 10 HDMI Audio [Radeon 56/64] driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.1
    chip-ID: 1002:aaf8 class-ID: 0403
  Device-3: ASUSTek USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.18.12-3-MANJARO running: yes
  Sound Server-2: PulseAudio v: 16.1 running: no
  Sound Server-3: PipeWire v: 0.3.55 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: docker0 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  IF-ID-2: veth8ff990b state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.78 TiB used: 488.21 GiB (17.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 240GB
    size: 223.58 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 00RL scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST1000DM010-2EP102
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: CC43 scheme: GPT
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST500LM000-1EJ162
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 5400 serial: <filter> rev: SM30
  ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST1000LM035-1RK172
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 5400 serial: <filter> rev: SBM3
  ID-5: /dev/sde maj-min: 8:64 vendor: Western Digital
    model: WD3200BVVT-63A26Y0 size: 298.09 GiB block-size: physical: 512 B
    logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH16NS55 rev: 1.03
    dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 140.59 GiB size: 140.59 GiB (100.00%)
    used: 75.13 GiB (53.4%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: Manjaro
    uuid: f91dda9e-f6f6-4c52-a22a-a3140000f9ce
  ID-2: /boot/efi raw-size: 33 MiB size: 32.9 MiB (99.55%)
    used: 4.8 MiB (14.7%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: EFI
    uuid: 67F3-740A
  ID-3: /home raw-size: 140.59 GiB size: 140.59 GiB (100.00%)
    used: 75.13 GiB (53.4%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: Manjaro
    uuid: f91dda9e-f6f6-4c52-a22a-a3140000f9ce
  ID-4: /home/<filter>/mnt/<filter> raw-size: N/A size: 14.3 GiB
    used: 7.84 GiB (54.8%) fs: fuse.sshfs
    remote: <filter>
  ID-5: /mnt/projects raw-size: 931.51 GiB size: 1.66 TiB (182.00%)
    used: 413.08 GiB (24.4%) fs: btrfs dev: /dev/sdd maj-min: 8:48 label: N/A
    uuid: 38997abf-7fcb-4eec-9dbb-c115ac647524
  ID-6: /var/cache raw-size: 140.59 GiB size: 140.59 GiB (100.00%)
    used: 75.13 GiB (53.4%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: Manjaro
    uuid: f91dda9e-f6f6-4c52-a22a-a3140000f9ce
  ID-7: /var/log raw-size: 140.59 GiB size: 140.59 GiB (100.00%)
    used: 75.13 GiB (53.4%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: Manjaro
    uuid: f91dda9e-f6f6-4c52-a22a-a3140000f9ce
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 32 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-0 maj-min: 254:0 mapped: swap label: swap
    uuid: 28d70f5b-e14d-4a4d-816b-7a0326785b1f
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 50.96 GiB fs: btrfs label: Linux Mint
    uuid: 6faa2ee2-6f05-4847-b878-431cfd92e3c5
  ID-2: /dev/sda3 maj-min: 8:3 size: 32 GiB fs: swap label: N/A
    uuid: 53d710f6-8ebf-4925-aefc-b0e0a9442e0b
  ID-3: /dev/sdb1 maj-min: 8:17 size: 931.51 GiB fs: btrfs
    label: BTRFS Backup uuid: 61669fdf-4dec-46d8-911d-7e2ddb11e940
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-3:5 info: ASUSTek USB Audio type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 2.0
    speed: 480 Mb/s power: 100mA chip-ID: 0b05:1876 class-ID: 0300
    serial: <filter>
  Hub-2: 1-4:2 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s
    power: 100mA chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-4.3:3 info: Logitech PowerPlay Wireless Charging System
    type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s power: 498mA chip-ID: 046d:c53a class-ID: 0300
  Device-2: 1-4.4:4 info: Trust GXT 860 Keyboard type: Keyboard,Mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s
    power: 100mA chip-ID: 145f:0218 class-ID: 0301
  Hub-3: 2-0:1 info: Super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s
    chip-ID: 1d6b:0003 class-ID: 0900
  Hub-4: 2-4:2 info: Genesys Logic Hub ports: 4 rev: 3.1 speed: 5 Gb/s
    chip-ID: 05e3:0612 class-ID: 0900
Sensors:
  System Temperatures: cpu: 45.0 C pch: 49.0 C mobo: N/A gpu: amdgpu
    temp: 54.0 C mem: 54.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1271
Info:
  Processes: 363 Uptime: 1h 45m wakeups: 9 Init: systemd v: 251
  default: graphical tool: systemctl Compilers: gcc: 12.1.0 Packages: 1486
  pacman: 1478 lib: 421 flatpak: 8 Shell: Zsh v: 5.9 running-in: konsole
  inxi: 3.3.19

I’m no expert and this might be completely wrong, but I see in your profile you use wayland, and that’s not ready AFAIK. Especially not with KDE (which I also saw you use.) So that might be the reason, I don’t know.

personally, i have a better experience with wayland on kde than i had on x11 (especially with pipewire), i had switched at i think around november 2021 and since then i only had some applications crash with “wayland connection lost / wayland compositor connection died”, which were all resolved by around february 2022

4

Ah OK, as long as you remember that it might be the cause. But I admit it doesn’t sound like it.

Have you tried a different kernel?

5

yes, i have tried the following kernels, and can confirm that at least in the tests i did, the problems did not appear:

  • kernel 5.17.15-1
  • kernel 5.18.7-1 (by copying over from a btrfs snapshot before the update)

though these problems may not show in these tests, because it may only happen when the system was off for ~6 hours (though still only after the update)

6

Well, seeing as the problems weren’t present on the earlier kernel versions, is there a specific reason you don’t use one of 'em?

I’d suggest 5.15 as that’s the latest LTS version. To install it:

mhwd-kernel --install linux515

Then reboot into it and test.

7

I’d suggest 5.15 as that’s the latest LTS version

i commonly use the latest available, because it has the most features (i use proton and other things, because commonly the latest gives the best compatibility and performance)

Well, seeing as the problems weren’t present on the earlier kernel versions, is there a specific reason you don’t use one of 'em?

i use the packages, linux517 and linux518, i always have the latest (non-rc) and a backup installed, for testing purposes i had copied the old kernel (from linux518) from snapshots to current and tried that (because the manjaro linux kernel packages only provide the latest version unlike the ubuntu packages)
also as a “last resort” i have the kernel source ready to be compiled if i need something specific, but i rather use the manjaro provided packages

8

No offense meant, but that is a somewhat silly reason. There’s a reason that, originally before the LTS label was even invented, non-LTS kernel versions were known as experimental.

I’d recommend sticking to an LTS version.

Yes, the lagging and IO usage performs well! :stuck_out_tongue_winking_eye:

I still recommend using 5.15` rather than the latest and greatest. Especially since there’s no specific reason you need the latest…

And besides, the latest and greatest is now 5.19. No longer 5.18.

9

And besides, the latest and greatest is now 5.19. No longer 5.18.

not currently, it may be released now, but manjaro still only ships a rc version of 5.19 (and like i said, i self-compile only as a “last resort”)

Especially since there’s no specific reason you need the latest…

there is no specific reason, but like i said, from my experience, Proton performs way better on newer kernels and has more compatibility (with that i also mean less crashes / stuttering)

non-LTS kernel versions were known as experimental.

from what i can tell, “experimental” are only the kernels that are not “released” yet (like development, staging or release-candidates (rc)) and i only really had problems with the manjaro provided kernels in the past, never self compiled (with the same config taken from /proc/config.gz) or ubuntu / debian kernels

but from what i can tell now, it seems like the manjaro provided kernel 5.18.12 is problematic somehow, but the previous 5.18.7 was not, so for now i will stick with the older kernel (or if i want to self-compile stuff)

10

I have now upgraded to 5.18.14-1 and the problems do not seem to happen anymore, so 5.18.12 was probably just a bad build.

1 Like
11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.