This issue has not been present in 1.0.16.
I've seen it previously in 1.0.18 but wanted to wait for the next kernel and scx version before I report it. Now, here we are.
This usually happens easily with Chrome while playing Youtube videos. The scheduler crashes and will eventually be restarted by systemd until the restart counter expires:
# uname -a
Linux jupiter 6.18.3-gentoo #2 SMP PREEMPT Sun Jan 4 15:13:30 CET 2026 x86_64 12th Gen Intel(R) Core(TM) i7-12700K GenuineIntel GNU/Linux
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 20
On-line CPU(s) list: 0-19
Vendor ID: GenuineIntel
Model name: 12th Gen Intel(R) Core(TM) i7-12700K
CPU family: 6
Model: 151
Thread(s) per core: 2
Core(s) per socket: 12
Socket(s): 1
Stepping: 2
CPU(s) scaling MHz: 19%
CPU max MHz: 5000.0000
CPU min MHz: 800.0000
BogoMIPS: 7222.00
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4
_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves avx_vnni dtherm ida arat pln pts hwp
hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize pconfig arch_lbr ibt flush_l1d arch_capabilities
Virtualization features:
Virtualization: VT-x
Caches (sum of all):
L1d: 512 KiB (12 instances)
L1i: 512 KiB (12 instances)
L2: 12 MiB (9 instances)
L3: 25 MiB (1 instance)
Vulnerabilities:
Gather data sampling: Not affected
Ghostwrite: Not affected
Indirect target selection: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Old microcode: Not affected
Reg file data sampling: Vulnerable
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Vulnerable
Spectre v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
Spectre v2: Vulnerable; IBPB: disabled; STIBP: disabled; PBRSB-eIBRS: Vulnerable; BHI: Vulnerable
Srbds: Not affected
Tsa: Not affected
Tsx async abort: Not affected
Vmscape: Vulnerable
I often see NOHZ tick-stop error: local softirq work is pending when stopping scx but this one also captures the crash itself:
# dmesg upgrading from 1.0.16 to 1.0.19
[209999.331435] NOHZ tick-stop error: local softirq work is pending, handler #200!!!
[209999.333611] NOHZ tick-stop error: local softirq work is pending, handler #280!!!
[209999.336930] NOHZ tick-stop error: local softirq work is pending, handler #280!!!
[209999.336933] NOHZ tick-stop error: local softirq work is pending, handler #280!!!
[209999.340268] NOHZ tick-stop error: local softirq work is pending, handler #280!!!
[209999.340270] NOHZ tick-stop error: local softirq work is pending, handler #280!!!
[209999.340489] NOHZ tick-stop error: local softirq work is pending, handler #200!!!
[209999.351920] NOHZ tick-stop error: local softirq work is pending, handler #80!!!
[209999.353610] NOHZ tick-stop error: local softirq work is pending, handler #80!!!
[209999.353769] NOHZ tick-stop error: local softirq work is pending, handler #80!!!
[209999.483712] sched_ext: BPF scheduler "lavd_1.0.16_x86_64_unknown_linux_gnu" disabled (unregistered from user space)
[210002.820652] sched_ext: BPF scheduler "lavd_1.0.20_x86_64_unknown_linux_gnu" enabled
[210002.820695] sched_ext: scx_bpf_cpu_rq() is deprecated; use scx_bpf_locked_rq() when holding rq lock or scx_bpf_cpu_curr() to read remote curr safely.
[210051.375101] sched_ext: BPF scheduler "lavd_1.0.20_x86_64_unknown_linux_gnu" disabled (runtime error)
[210051.375111] sched_ext: lavd_1.0.20_x86_64_unknown_linux_gnu: SCX_DSQ_LOCAL[_ON] cannot move migration disabled chrome[561481] from CPU 18 to 10
[210051.375115] task_can_run_on_remote_rq+0xd0/0x130
[210051.375126] dispatch_to_local_dsq+0x61/0x200
[210051.375128] process_ddsp_deferred_locals+0x49/0xc0
[210051.375129] deferred_irq_workfn+0x23/0x30
[210051.375130] irq_work_run_list+0x49/0x80
[210051.375132] irq_work_run+0x18/0x40
[210051.375133] __sysvec_irq_work+0x1c/0xb0
[210051.375135] sysvec_irq_work+0x6c/0x90
[210051.375137] asm_sysvec_irq_work+0x1a/0x20
[210051.375138] finish_task_switch.isra.0+0x90/0x260
[210051.375140] __schedule+0x3d5/0x1020
[210051.375141] schedule+0x27/0xd0
[210051.375143] schedule_hrtimeout_range_clock+0xdc/0xe0
[210051.375144] do_epoll_wait+0x443/0x480
[210051.375146] __x64_sys_epoll_wait+0x51/0xe0
[210051.375148] do_syscall_64+0x52/0xfd0
[210051.375149] entry_SYSCALL_64_after_hwframe+0x4b/0x53
[210055.008059] sched_ext: scx_bpf_cpu_rq() is deprecated; use scx_bpf_locked_rq() when holding rq lock or scx_bpf_cpu_curr() to read remote curr safely.
[210055.008379] sched_ext: BPF scheduler "lavd_1.0.20_x86_64_unknown_linux_gnu" enabled
Take note that the scheduler identifies as 1.0.20 although I've installed 1.0.19:
# equery l scx
* Searching for scx ...
[IP-] [ ] sys-kernel/scx-1.0.19:0
This already happened with the previous version which showed 1.0.19 despite 1.0.18 being installed.
I'm using the new scx_loader.service for both 1.0.16 and 1.0.19:
# systemctl status scx_loader.service
● scx_loader.service - DBUS on-demand loader of sched-ext schedulers
Loaded: loaded (/usr/lib/systemd/system/scx_loader.service; enabled; preset: disabled)
Active: active (running) since Wed 2026-01-07 01:40:24 CET; 1min 36s ago
Invocation: bb06dd9a12aa494a90b1fc6bb999aeb6
Main PID: 2183383 (scx_loader)
Tasks: 26 (limit: 38072)
CPU: 2.077s
CGroup: /system.slice/scx_loader.service
├─2183383 /usr/bin/scx_loader
└─2188865 scx_lavd
Jan 07 01:41:16 jupiter scx_loader[2188865]: }
Jan 07 01:41:16 jupiter scx_loader[2188865]: 2026-01-07T00:41:16.985319Z INFO ThreadId(01) scx_lavd: scheds/rust/scx_lavd/src/main.rs:541: capacity bound: 778 (4.0428185%)
Jan 07 01:41:16 jupiter scx_loader[2188865]: primary CPUs: [16]
Jan 07 01:41:16 jupiter scx_loader[2188865]: overflow CPUs: [17, 18, 19, 0, 1, 2, 3, 4, 5, 6, 7, 12, 13, 14, 15, 8, 9, 10, 11]
Jan 07 01:41:16 jupiter scx_loader[2188865]: 2026-01-07T00:41:16.985329Z INFO ThreadId(01) scx_lavd: scheds/rust/scx_lavd/src/main.rs:541: capacity bound: 19244 (100%)
Jan 07 01:41:16 jupiter scx_loader[2188865]: primary CPUs: [8]
Jan 07 01:41:16 jupiter scx_loader[2188865]: overflow CPUs: [10, 0, 2, 4, 6, 12, 14, 16, 17, 18, 19, 9, 11, 1, 3, 5, 7, 13, 15]
Jan 07 01:41:18 jupiter scx_loader[2188865]: 2026-01-07T00:41:18.035071Z WARN ThreadId(01) scx_utils::libbpf_logger: rust/scx_utils/src/libbpf_logger.rs:12: libbpf: map 'lavd_ops': BPF map skeleton link is uninitialized
Jan 07 01:41:18 jupiter scx_loader[2188865]: 2026-01-07T00:41:18.121319Z INFO ThreadId(01) scx_lavd: scheds/rust/scx_lavd/src/main.rs:1010: scx_lavd scheduler is initialized (build ID: 1.0.20 x86_64-unknown-linux-gnu)
Jan 07 01:41:18 jupiter scx_loader[2188865]: 2026-01-07T00:41:18.121337Z INFO ThreadId(01) scx_lavd: scheds/rust/scx_lavd/src/main.rs:1014: scx_lavd scheduler starts running.
This issue has not been present in 1.0.16.
I've seen it previously in 1.0.18 but wanted to wait for the next kernel and scx version before I report it. Now, here we are.
This usually happens easily with Chrome while playing Youtube videos. The scheduler crashes and will eventually be restarted by systemd until the restart counter expires:
I often see
NOHZ tick-stop error: local softirq work is pendingwhen stopping scx but this one also captures the crash itself:Take note that the scheduler identifies as 1.0.20 although I've installed 1.0.19:
This already happened with the previous version which showed 1.0.19 despite 1.0.18 being installed.
I'm using the new scx_loader.service for both 1.0.16 and 1.0.19: