Hello,
my manjaro xfce hangs for 20 seconds or so (several times a day, sometimes just a single app, sometimes all the apps) maybe you can recommend something. it might be hw related and/or btrfs related (or maybe something else, I don’t know). dmesg doesn’t really help
thank you in advance
Moderator edit: Topic title edited
My crystal ball is broken and my clairvoyant abilities are limited to the time of day, so there should be a little more to come.
It cannot help us either - since we do not have it …
or really anything halfway concrete at all …
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit.
To that end, links are provided (below) - Please use them.
Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Waiting for someone to blindly ask questions is also counter-productive – typically, nobody has a 
at their disposal – Instead, please help others to ask informed questions, based on information you provide.
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; 
Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:
inxi --filter --verbosity=8
or the short form (preferred):
inxi -zv8
inxi output follows:
System:
Kernel: 6.18.4-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: tsc
avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.18-x86_64
root=UUID=16cb97b0-71ba-4729-b64f-cc052751b408 rw rootflags=subvol=@ quiet splash
cryptdevice=UUID=a6456476-edde-4d61-af4a-1accda4d33ba:luks-a6456476-edde-4d61-af4a-1accda4d33ba
root=/dev/mapper/luks-a6456476-edde-4d61-af4a-1accda4d33ba apparmor=1 security=apparmor
udev.log_priority=3
Console: pty pts/2 DM: LightDM v: 1.32.0 Distro: Manjaro base: Arch Linux
Machine:
Type: Convertible System: HP product: HP Spectre x360 Convertible 13-w0XX v: N/A
serial: <filter> Chassis: type: 31 serial: N/A
Mobo: HP model: 827E v: 94.71 serial: <filter> part-nu: Z9E46EA#ABV
uuid: 36444335-3534-4c37-4e50-504c35344435 Firmware: UEFI vendor: American Megatrends v: F.49
date: 05/03/2019
Battery:
ID-1: BAT0 charge: 1.5 Wh (7.3%) condition: 20.3/20.3 Wh (100%) volts: 11.96 min: 11.55
model: Hewlett-Packard Primary type: Li-ion serial: N/A charging: status: not charging
cycles: N/A
Memory:
System RAM: total: 16 GiB available: 15.49 GiB used: 4.7 GiB (30.3%) igpu: 64 MiB
Array-1: capacity: 16 GiB slots: 2 modules: 2 EC: None max-module-size: 8 GiB note: est.
Device-1: Bottom - on board type: LPDDR3 detail: synchronous unbuffered (unregistered)
size: 8 GiB speed: 1867 MT/s volts: curr: 1.2 min: 1.25 max: 1.25 width (bits): data: 64
total: 64 manufacturer: Micron part-no: MT52L1G32D4PG-107 WT:B serial: N/A
Device-2: Bottom - on board type: LPDDR3 detail: synchronous unbuffered (unregistered)
size: 8 GiB speed: 1867 MT/s volts: curr: 1.2 min: 1.25 max: 1.25 width (bits): data: 64
total: 64 manufacturer: Micron part-no: MT52L1G32D4PG-107 WT:B serial: N/A
PCI Slots:
Slot: 0 type: PCIe status: in use info: J6B2 length: long volts: 3.3 bus-ID: 00:01.0
CPU:
Info: model: Intel Core i7-7500U socket: U3E1 bits: 64 type: MT MCP arch: Amber/Kaby Lake
note: check gen: core 7 level: v3 note: check built: 2017 process: Intel 14nm family: 6
model-id: 0x8E (142) stepping: 9 microcode: 0xF6
Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 600 min/max: 400/3500 base/boost: 3500/8300 scaling: driver: intel_pstate
governor: powersave volts: 1.0 V ext-clock: 100 MHz cores: 1: 600 2: 600 3: 600 4: 600
bogomips: 23199
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 epb 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 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: gather_data_sampling mitigation: Microcode
Type: ghostwrite status: Not affected
Type: indirect_target_selection status: Not affected
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: old_microcode status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
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: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2
bus-ID: 00:02.0 chip-ID: 8086:5916 class-ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP Wide Vision FHD camera driver: uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 05c8:0430
class-ID: 0e02
Device-3: Cheng Uei Precision Industry (Foxlink) HP IR Camera driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:5 chip-ID: 05c8:0431 class-ID: 0e02
serial: <filter>
Display: x11 server: X.org v: 1.21.1.21 compositor: xfwm4 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: iris gpu: i915 tty: 190x41
Monitor-1: eDP-1 model: ChiMei InnoLux 0x1367 built: 2015 res: 1920x1080 dpi: 166 gamma: 1.2
chroma: red: x: 0.643 y: 0.341 green: x: 0.314 y: 0.608 blue: x: 0.153 y: 0.051 white: x: 0.314
y: 0.329 size: 293x165mm (11.54x6.5") diag: 336mm (13.2") ratio: 16:9 modes: 1920x1080
EDID-Warnings: 1: parse_edid: unknown flag 2
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris inactive: wayland,x11
API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.3-arch1.1 note: console (EGL sourced)
renderer: Mesa Intel HD Graphics 620 (KBL GT2), llvmpipe (LLVM 21.1.6 256 bits)
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings x11: xprop
Audio:
Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:9d71 class-ID: 0403
Device-2: C-Media CM108 Audio Controller driver: hid-generic,snd-usb-audio,usbhid type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.1.4:9 chip-ID: 0d8c:013c class-ID: 0300
API: ALSA v: k6.18.4-1-MANJARO status: kernel-api with: aoss type: oss-emulator
tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.9 status: n/a (root, process) with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 01:00.0 chip-ID: 8086:24fd class-ID: 0280
IF: wlp1s0 state: down mac: <filter>
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter driver: r8152 type: USB rev: 3.0
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-1.1.1:5 chip-ID: 0bda:8153 class-ID: 0000
serial: <filter>
IF: enp0s20f0u1u1u1 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:7 chip-ID: 8087:0a2b class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: see --recommends
Logical:
Message: No logical block device data found.
Device-1: luks-a6456476-edde-4d61-af4a-1accda4d33ba maj-min: 253:0 type: LUKS dm: dm-0
size: 1.81 TiB
Components:
p-1: sda2 maj-min: 8:2 size: 1.81 TiB
Device-2: luks-87a3c2a8-5168-451e-bcef-4d2a8c5955f4 maj-min: 253:1 type: LUKS dm: dm-1
size: 8.8 GiB
Components:
p-1: sda3 maj-min: 8:3 size: 8.8 GiB
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 2.75 TiB used: 1.33 TiB (48.4%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Toshiba model: N/A size: 953.87 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 5KHA4101 temp: 30.9 C scheme: GPT
SMART: yes health: PASSED on: 4y 65d 9h cycles: 4,149 read-units: 12,215,330 [6.25 TB]
written-units: 10,210,783 [5.22 TB]
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD20SPZX-22UA7T0
family: Blue Mobile (SMR) size: 1.82 TiB block-size: physical: 4096 B logical: 512 B type: USB
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5400
serial: <filter> fw-rev: 01.01A01 temp: 51 C scheme: GPT
SMART: yes state: enabled health: PASSED on: 88d 19h cycles: 140
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 1.33 TiB (73.5%) fs: btrfs
block-size: 4096 B dev: /dev/dm-0 maj-min: 253:0
mapped: luks-a6456476-edde-4d61-af4a-1accda4d33ba label: N/A
uuid: 16cb97b0-71ba-4729-b64f-cc052751b408
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 904 KiB (0.3%) fs: vfat
block-size: 512 B dev: /dev/sda1 maj-min: 8:1 label: N/A uuid: EE16-CDAA
ID-3: /home raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 1.33 TiB (73.5%) fs: btrfs
block-size: 4096 B dev: /dev/dm-0 maj-min: 253:0
mapped: luks-a6456476-edde-4d61-af4a-1accda4d33ba label: N/A
uuid: 16cb97b0-71ba-4729-b64f-cc052751b408
ID-4: /var/cache raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 1.33 TiB (73.5%) fs: btrfs
block-size: 4096 B dev: /dev/dm-0 maj-min: 253:0
mapped: luks-a6456476-edde-4d61-af4a-1accda4d33ba label: N/A
uuid: 16cb97b0-71ba-4729-b64f-cc052751b408
ID-5: /var/log raw-size: 1.81 TiB size: 1.81 TiB (100.00%) used: 1.33 TiB (73.5%) fs: btrfs
block-size: 4096 B dev: /dev/dm-0 maj-min: 253:0
mapped: luks-a6456476-edde-4d61-af4a-1accda4d33ba label: N/A
uuid: 16cb97b0-71ba-4729-b64f-cc052751b408
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes compressor: zstd
max-pool: 20%
ID-1: swap-1 type: partition size: 8.8 GiB used: 614 MiB (6.8%) priority: -2 dev: /dev/dm-1
maj-min: 253:1 mapped: luks-87a3c2a8-5168-451e-bcef-4d2a8c5955f4 label: swap
uuid: 03d4d42b-dd49-4de9-bd71-aadeb217b628
Unmounted:
ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 260 MiB fs: vfat label: N/A uuid: 88E0-AD11
ID-2: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: N/A label: N/A uuid: N/A
ID-3: /dev/nvme0n1p3 maj-min: 259:3 size: 941.77 GiB fs: ntfs label: Windows
uuid: DC669389669362D6
ID-4: /dev/nvme0n1p4 maj-min: 259:4 size: 1.77 GiB fs: ntfs label: N/A uuid: B2D000EAD000B71F
ID-5: /dev/nvme0n1p5 maj-min: 259:5 size: 10.05 GiB fs: ntfs label: RECOVERY
uuid: A82E062D2E05F4DA
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 1-1:2 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
mode: 2.0 chip-ID: 0bda:5411 class-ID: 0900
Hub-3: 1-1.1:4 info: Realtek RTS5411 Hub ports: 4 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 chip-ID: 0bda:5411 class-ID: 0900
Device-1: 1-1.1.2:6 info: Logitech Keyboard K120 type: keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 90mA
chip-ID: 046d:c31c class-ID: 0300
Device-2: 1-1.1.3:8 info: Logitech Mouse type: mouse driver: hid-generic,usbhid interfaces: 1
rev: 2.0 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA chip-ID: 046d:c077
class-ID: 0301
Device-3: 1-1.1.4:9 info: C-Media CM108 Audio Controller type: audio,HID
driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
lanes: 1 mode: 1.1 power: 100mA chip-ID: 0d8c:013c class-ID: 0300
Device-4: 1-5:3 info: Cheng Uei Precision Industry (Foxlink) HP Wide Vision FHD camera
type: video driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
mode: 2.0 power: 500mA chip-ID: 05c8:0430 class-ID: 0e02
Device-5: 1-6:5 info: Cheng Uei Precision Industry (Foxlink) HP IR Camera type: video
driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
power: 500mA chip-ID: 05c8:0431 class-ID: 0e02 serial: <filter>
Device-6: 1-7:7 info: Intel Bluetooth wireless interface type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 8087:0a2b class-ID: e001
Hub-4: 2-0:1 info: super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
mode: 3.2 gen-1x1 chip-ID: 1d6b:0003 class-ID: 0900
Hub-5: 2-1:2 info: Realtek Hub ports: 4 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
mode: 3.2 gen-1x1 chip-ID: 0bda:0411 class-ID: 0900
Hub-6: 2-1.1:3 info: Realtek Hub ports: 4 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
mode: 3.2 gen-1x1 chip-ID: 0bda:0411 class-ID: 0900
Device-1: 2-1.1.1:5 info: Realtek RTL8153 Gigabit Ethernet Adapter type: Network driver: r8152
interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 power: 256mA
chip-ID: 0bda:8153 class-ID: 0000 serial: <filter>
Device-2: 2-1.2:4 info: ASMedia ASM1051E SATA 6Gb/s bridge ASM1053E ASM1153 3Gb/s ASM1153E
bridge type: mass storage driver: uas interfaces: 1 rev: 3.1 speed: 5 Gb/s (596.0 MiB/s)
lanes: 1 mode: 3.2 gen-1x1 chip-ID: 174c:55aa class-ID: 0806 serial: <filter>
Sensors:
System Temperatures: cpu: 48.0 C pch: 45.5 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1610 libs: 402 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
2: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
3: https://mirror.koddos.net/manjaro/stable/$repo/$arch
4: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
5: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
6: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
7: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
8: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 334
1: cpu: 100% command: ps pid: 395567 mem: 4.26 MiB (0.0%)
2: cpu: 13.9% command: thunderbird pid: 394150 mem: 712.7 MiB (4.4%)
3: cpu: 11.7% command: brave pid: 395042 mem: 239.2 MiB (1.5%)
4: cpu: 7.7% command: transmission-gtk pid: 275396 mem: 280.9 MiB (1.7%)
5: cpu: 7.2% command: freetube pid: 394410 mem: 214.7 MiB (1.3%)
Memory top: 5 of 334
1: mem: 712.7 MiB (4.4%) command: thunderbird pid: 394150 cpu: 13.9%
2: mem: 417.1 MiB (2.6%) command: brave pid: 218136 cpu: 1.4%
3: mem: 356.9 MiB (2.2%) command: exe pid: 9370 cpu: 2.1%
4: mem: 335.5 MiB (2.1%) command: qtcreator pid: 276355 cpu: 0.0%
5: mem: 287.2 MiB (1.8%) command: brave pid: 218183 cpu: 1.4%
Info:
Processes: 334 Power: uptime: 1d 1h 36m states: freeze,mem,disk suspend: deep avail: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.18 GiB
services: upowerd,xfce4-power-manager Init: systemd v: 258 default: graphical tool: systemctl
Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Sudo (su) v: 1.9.17p2 default: Bash v: 5.3.9
running-in: pty pts/2 inxi: 3.3.40
rootfs is a raid1 usb enclosure (I used the same enclosure under ubuntu, but with different hdds)
Maybe there is something interesting in the journal
journalctl -b -p3 --no-pager
PipeWire status n/a (root, process) indicates that the PipeWire service is not active
To check the socket and service:
systemctl --user --full status pipewire.socket pipewire.service
So you are running the Manjaro installation on a removable disk, yes?
Could be the bottleneck created by the USB connection.
To further the bottleneck you have encrypted the installation.
Do not run your system from a removable USB connected disk
This seems a bit “off”:
Processes:
CPU top: 5 of 334
1: cpu: 100% command: ps pid: 395567 mem: 4.26 MiB (0.0%)
Check what this PID is in Task Manager, Htop or similar.
Journal file /var/log/journal/8b95da60281e4870996c5fc0482b4341/user-1000@000644811ae9b0bc-536df9f7e73d8904.journal~ is truncated, ignoring file.
jan 28 19:38:12 af1 kernel: x86/cpu: SGX disabled or unsupported by BIOS.
jan 28 19:38:23 af1 kernel: Bluetooth: hci0: Reading supported features failed (-16)
jan 28 19:38:43 af1 bluetoothd[890]: Failed to set mode: Failed (0x03)
jan 28 19:40:12 af1 lightdm[1703]: gkr-pam: unable to locate daemon control file
● pipewire.socket - PipeWire Multimedia System Sockets
Loaded: loaded (/usr/lib/systemd/user/pipewire.socket; enabled; preset: enabled)
Active: active (running) since Wed 2026-01-28 19:40:14 CET; 3h 45min ago
Invocation: 29c8989751e14e73807ba8057615842c
Triggers: ● pipewire.service
Listen: /run/user/1000/pipewire-0 (Stream)
/run/user/1000/pipewire-0-manager (Stream)
jan 28 19:40:14 af1 systemd[1762]: Listening on PipeWire Multimedia System Sockets.
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
Active: active (running) since Wed 2026-01-28 19:40:21 CET; 3h 45min ago
Invocation: 25dbe9afad1c49d484d8976fa8335049
TriggeredBy: ● pipewire.socket
Main PID: 1893 (pipewire)
Tasks: 3 (limit: 18988)
Memory: 9.2M (peak: 12.6M)
CPU: 34.550s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─1893 /usr/bin/pipewire
jan 28 19:40:21 af1 systemd[1762]: Started PipeWire Multimedia Service.
yes
rebooted since then, but now I have this:
1: cpu: 300% command: ps pid: 110578 mem: 4.29 MiB (0.0%)
there’s no process for that pid. can it be something inxi started in order to be able to generate that output?
Yes, that’s how inxi works. In and of itself, it’s only a Perl script — which will of course also have a PID attached to it — and it executes other utilities to gather its data.
today I saw this in the dmesg after hanging, might be related:
[44237.983253] INFO: task khugepaged:53 blocked for more than 122 seconds.
[44237.983274] Tainted: G OE 6.18.4-1-MANJARO #1
[44237.983285] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[44237.983290] task:khugepaged state:D stack:0 pid:53 tgid:53 ppid:2 task_flags:0x240040 flags:0x00080000
[44237.983312] Call Trace:
[44237.983319] <TASK>
[44237.983331] ? __pfx_bit_wait_io+0x10/0x10
[44237.983356] __schedule+0x418/0x1320
[44237.983376] ? blk_mq_flush_plug_list+0x49/0x1b0
[44237.983398] ? __pfx_bit_wait_io+0x10/0x10
[44237.983413] schedule+0x27/0xd0
[44237.983427] io_schedule+0x46/0x70
[44237.983441] bit_wait_io+0x11/0x60
[44237.983455] __wait_on_bit+0x2d/0xa0
[44237.983473] out_of_line_wait_on_bit+0x97/0xc0
[44237.983491] ? __pfx_wake_bit_function+0x10/0x10
[44237.983508] read_extent_buffer_pages+0x3e/0x60
[44237.983529] btrfs_read_extent_buffer+0x77/0x190
[44237.983551] read_block_for_search+0x21e/0x400
[44237.983568] btrfs_search_slot+0x325/0xd10
[44237.983586] ? set_extent_bit+0x1e7/0x7c0
[44237.983601] ? kmem_cache_alloc_noprof+0x14b/0x5a0
[44237.983620] btrfs_lookup_file_extent+0x4d/0x70
[44237.983638] btrfs_get_extent+0x122/0x6b0
[44237.983659] btrfs_do_readpage+0x202/0x6c0
[44237.983688] btrfs_readahead+0xe3/0x180
[44237.983712] ? __lruvec_stat_mod_folio+0x85/0xd0
[44237.983735] ? __pfx_end_bbio_data_read+0x10/0x10
[44237.983760] read_pages+0x75/0x220
[44237.983795] page_cache_ra_unbounded+0x1e0/0x270
[44237.983819] page_cache_sync_readahead+0x4c/0x70
[44237.983833] collapse_file+0x6f5/0x1030
[44237.983846] ? __pfx_khugepaged+0x10/0x10
[44237.983860] ? __pfx_workingset_update_node+0x10/0x10
[44237.983877] hpage_collapse_scan_file+0x248/0x5d0
[44237.983893] ? __pfx_khugepaged+0x10/0x10
[44237.983902] khugepaged+0x76f/0x960
[44237.983922] ? __pfx_khugepaged+0x10/0x10
[44237.983931] kthread+0xfc/0x240
[44237.983943] ? __pfx_kthread+0x10/0x10
[44237.983954] ret_from_fork+0x1c2/0x1f0
[44237.983966] ? __pfx_kthread+0x10/0x10
[44237.983976] ret_from_fork_asm+0x1a/0x30
[44237.983997] </TASK>
Going right back to the source khugepaged is related to transparent huge pages. (I use permanent huge pages.) Is this system a hypervisor?
Still seems unrelated to the problem. Or did other stack traces get spawned the same way?
Regardless, it should not take 2 minutes for what it’s trying to do here.
Are you sure this device 100% works? The quality of the enclosure does matter for doing something like this.
btrfs.It could be that some of btrfs’s features are causing you serious problems.
No, btrfs isn’t a bad file system at all, and it has some fascinating features. But the combination you’ve set up is practically begging for trouble.
Btrfs is a journaling filesystem. This means, among other things, that it has to perform cleanup more often than other filesystems. When it does this, it has to read, analyze, and rewrite entire chunks (1GB). Combined with USB, LUKS, and USB RAID, this means a lot of work for the filesystem.
It wouldn’t be unusual for long pauses to occur in your setup during emergencies.
Please check the current status of your filesystem using btrfs usage (and show it here).
sudo btrfs filesystem usage /
Ensure all btrfs volumes are mounted with noatime as an option.
This makes btrfs faster and avoids generating unnecessary metadata when files are only read. Details are linked at:
make btrfs faster
But not in your case, it’s located on the same device and is also encrypted. What’s intended as a relief therefore becomes an additional burden in this configuration.
I used the same enclosure under ubuntu for several years without issues (using ext4, different disks)
Overall:
Device size: 1.81TiB
Device allocated: 1.47TiB
Device unallocated: 348.88GiB
Device missing: 0.00B
Device slack: 2.50KiB
Used: 1.31TiB
Free (estimated): 504.94GiB (min: 330.50GiB)
Free (statfs, df): 504.94GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:1.46TiB, Used:1.30TiB (89.55%)
/dev/mapper/luks-a6456476-edde-4d61-af4a-1accda4d33ba 1.46TiB
Metadata,DUP: Size:6.00GiB, Used:3.51GiB (58.51%)
/dev/mapper/luks-a6456476-edde-4d61-af4a-1accda4d33ba 12.00GiB
System,DUP: Size:8.00MiB, Used:208.00KiB (2.54%)
/dev/mapper/luks-a6456476-edde-4d61-af4a-1accda4d33ba 16.00MiB
Unallocated:
/dev/mapper/luks-a6456476-edde-4d61-af4a-1accda4d33ba 348.88GiB
several such stack traces right after each other, these were the tasks:
According to this information, the disk is not too full.
Btrfs should not cause problems under these circumstances (unless the USB data rate drops significantly).
This also means that balancing the disk will not provide any significant advantages.
P.S. If possible, I would recommend swapping to an internal NVMe drive.
how would I able to know if there’s a hardware (or driver?) issue?
I’m kind of interested in trying a USB device myself, as it should work.
What are your mount options? (In /etc/fstab?)
With btrfs, there a few basic things you can do to help with this high latency device.
I would use the options:
UUID=XX-X-XX / btrfs subvol=/@,noautodefrag,nodiscard,noatime,compress 0 0
noautodefrag - I changed my mind here, autodefrag is extra I/O attempting to optimise. And you hardly ever need to defrag btrfs in the way it operates in 2G chunks.
space_cache=v2
Edit: space_cache=v2 has been then default since v4.5
noatime - Disable file access times
Massive performance improvement as metadata doesn’t constantly get hammered
compress - compress all newly written data at the default compression level. The default is compress=zstd:3, which is fine and fast. You can experiment with higher, zstd:7 would probably be a good place to aim high, the trade off gets almost exponentially worse with higher values.
I’m not even a fan of compression, but this is a case where you want to offload some of the work to your CPU, and less data needs to be transferred over USB.
To make the whole volume compressed, we would have to run:
btrfs filesystem defrag -r -v -czstd:3 /We don’t have to do it now, but to see the benefits it will need to be done.
@andreas85 knows a lot more about compression than I. I’ve only dabbled here and there.
Is this an NVMe drive in the enclosure? If so..
nodiscard - Disables on the fly TRIM for your driveSince kernel 6.2, btrfs does default to discard=async
Perform a scheduled manual TRIM (weekly usually suffices), this will make everything faster day to day.
If you don’t want to remember, you can enable this service (it will TRIM all mounted file systems that support it):
$ systemctl status fstrim
○ fstrim.service - Discard unused blocks on filesystems from /etc/fstab
Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static)
Active: inactive (dead) since Mon 2026-02-02 00:03:46 MST; 12h ago
Invocation: d91592da5e6949ea839029b12a18169c
TriggeredBy: ● fstrim.timer
Docs: man:fstrim(8)
Process: 59663 ExecStart=/usr/bin/fstrim --listed-in /etc/fstab:/proc/self/mountinfo --verbose --quiet-unsupported (code=exited, status=0/SUCCESS)
Main PID: 59663 (code=exited, status=0/SUCCESS)
Mem peak: 2.5M
CPU: 1.656s
But the point is to run this,when you don’t put load on the system.
This might be obvious, but have you checked the fans for dust buildup? I’ve seen random hangs turn out to be just overheating from clogged vents. Easy to overlook, easy to fix — worth ruling out!