System freezes randomly, likely due to CTRL-EVENT-BEACON-LOSS

LinuxLover471 · 2026-07-25 15:17:45

Hello!

I have been experiencing this issue for quite a while. When using the system normally, it would freeze at any random time, be it while editing a file in neovim, or playing a video in firefox. Means it doesn't depend upon system load as far as I can tell.

When it freezes, it locks up completely, the mouse doesn't work, neither does the keyboard. Anything I type during that time is lost as far as I can remember.

This issue seemed to be somewhat less frequent (might be placebo) by following this ArchWiki article.
I tried it because rtkit was demoting some threads in logs, and pipewire etc was a part of it, and this all too, happened without any significant system load, even while editing a file.

What I think is relevant in logs, it occurs at 20:02 as of the last polybar reading:

Jul 25 20:01:36 cosmos NetworkManager[469]: <info>  [1784989896.0845] dhcp4 (wlp0s29f7u5): state changed new lease, address=10.127.221.170
Jul 25 20:01:36 cosmos systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 25 20:01:36 cosmos systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 25 20:01:46 cosmos systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 25 20:02:29 cosmos wpa_supplicant[482]: wlp0s29f7u5: CTRL-EVENT-BEACON-LOSS
Jul 25 20:03:17 cosmos rtkit-daemon[527]: Successfully made thread 14727 of process 12410 owned by '1000' RT at priority 10.

Full log where this occurred: https://pastebin.com/W7aemPkP

Concise System info:

CPU: Intel Core 2 Quad Q9550 @ 3.33GHz
GPU: GT 740 GDDR3 (470xx proprietary driver)
RAM: 4GB DDR2 800MT/s Dual Channel
Storage: ADATA SU800 SATA 2 SSD

Detailed System info:

❯ inxi -Fxxz
System:
  Kernel: 7.1.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 16.1.1
  Desktop: i3 v: 4.25.1 dm: N/A Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required>
    Firmware: BIOS vendor: Award v: FI date: 08/09/2010
CPU:
  Info: quad core model: Intel Core2 Quad Q9550 bits: 64 type: MCP
    arch: Penryn rev: A cache: L1: 256 KiB L2: 12 MiB
  Speed (MHz): avg: 2352 min/max: 2000/2834 cores: 1: 2352 2: 2352 3: 2352
    4: 2352 bogomips: 26654
  Flags-basic: ht lm nx pae sse sse2 sse3 sse4_1 ssse3
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02
    arch: Kepler-2 pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0fc8
  Display: x11 server: X.org v: 1.21.1.24 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: LG (GoldStar) FHD
    res: 1920x1080 hz: 100 dpi: 102 diag: 546mm (21.5")
  API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: swrast x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: nvidia mesa v: 470.256.02
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GT 740/PCIe/SSE2
  API: Vulkan v: 1.4.350 surfaces: N/A device: 0 type: discrete-gpu
    driver: nvidia device-ID: 10de:0fc8
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    gpu: nvidia-settings,nvidia-smi x11: xprop,xrandr
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio
    vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:27d8
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b
  API: ALSA v: k7.1.4-arch1-1 status: kernel-api
  Server-1: sndiod v: N/A status: off
  Server-2: JACK v: 1.9.22 status: off
  Server-3: PipeWire v: 1.6.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet
    vendor: Gigabyte GA-G31M-ES2L driver: atl1c v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: bf00 bus-ID: 03:00.0 chip-ID: 1969:1063
  IF: enp3s0 state: down mac: <filter>
  Device-2: Ralink 802.11 n WLAN driver: rt2800usb type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-5:2 chip-ID: 148f:5370
  IF: wlp0s29f7u5 state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 90.09 GiB (6.4%)
  ID-1: /dev/sda vendor: A-Data model: SU800 size: 476.94 GiB
    speed: <unknown> serial: <filter>
  ID-2: /dev/sdb vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
    speed: <unknown> serial: <filter>
Partition:
  ID-1: / size: 39.08 GiB used: 18.27 GiB (46.7%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 332.55 GiB used: 71.83 GiB (21.6%) fs: ext4
    dev: /dev/sda6
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 632 KiB (0.0%) priority: -1
    dev: /dev/sda7
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A gpu: nvidia temp: 45 C
  Fan Speeds (rpm): cpu: 1834 fan-2: 2045 gpu: nvidia fan: 30%
  Power: 12v: N/A 5v: 2.91 3.3v: N/A vbat: 3.14
Info:
  Memory: total: 4 GiB available: 3.81 GiB used: 2.03 GiB (53.3%)
  Processes: 196 Power: uptime: 1h 4m wakeups: 0 Init: systemd v: 261
    default: graphical
  Packages: pm: pacman pkgs: 962 Compilers: clang: 22.1.8 gcc: 16.1.1
    Shell: Bash v: 5.3.15 running-in: alacritty inxi: 3.3.41

Please ask for any relevant information.
Thanks!

Last edited by LinuxLover471 (2026-07-25 15:38:57)

seth · 2026-07-25 19:11:24

it occurs at 20:02 as of the last polybar reading:

A clock widget? Does it show seconds?

When it freezes, it locks up completely, the mouse doesn't work, neither does the keyboard. Anything I type during that time is lost as far as I can remember.

https://wiki.archlinux.org/title/Keyboa … el_(SysRq) ?

Jul 25 19:31:21 archlinux kernel: usb 1-5: Product: 802.11 n WLAN
Jul 25 19:31:21 archlinux kernel: usb 1-6: Product: USB 2.0 Hub
Jul 25 19:31:21 archlinux kernel: usb 5-1: Product: G512 RGB MECHANICAL GAMING KEYBOARD
Jul 25 19:31:22 archlinux kernel: usb 5-2: Product: USB Optical Mouse

Ftr, mouse + keyboard are not on the same hub as the dongle.

Jul 25 19:31:31 cosmos kernel: rt2800usb 1-5:1.0 wlp0s29f7u5: renamed from wlan0
…
Jul 25 19:31:35 cosmos wpa_supplicant[482]: wlp0s29f7u5: Trying to associate with b6:ef:61:24:c2:35 (SSID='Redmi 13 5G' freq=2437 MHz)
…
Jul 25 19:31:36 cosmos NetworkManager[469]: <info>  [1784988096.2822] dhcp4 (wlp0s29f7u5): state changed new lease, address=10.127.221.170
…
Jul 25 19:31:57 cosmos kernel: INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.541 msecs
Jul 25 19:32:01 cosmos systemd-timesyncd[267]: Contacted time server [2401:c080:3000:2945:5400:4ff:fe69:f923]:123 (2.arch.pool.ntp.org).
…
Jul 25 19:42:35 cosmos kernel: perf: interrupt took too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Jul 25 19:42:52 cosmos sudo[5347]:       ak : TTY=pts/0 ; PWD=/var/tmp/aurutils-1000/build.z5VMiRvf ; USER=root ; COMMAND=/usr/bin/pacsync aurutils
Jul 25 19:42:52 cosmos sudo[5347]: pam_unix(sudo:session): session opened for user root(uid=0) by ak(uid=1000)
…
Jul 25 19:52:16 cosmos kernel: perf: interrupt took too long (3156 > 3138), lowering kernel.perf_event_max_sample_rate to 63000
…
Jul 25 19:57:06 cosmos pinentry-gtk[12627]: AT-SPI: Could not obtain desktop path or name
…
Jul 25 20:01:36 cosmos NetworkManager[469]: <info>  [1784989896.0845] dhcp4 (wlp0s29f7u5): state changed new lease, address=10.127.221.170
…
Jul 25 20:02:29 cosmos wpa_supplicant[482]: wlp0s29f7u5: CTRL-EVENT-BEACON-LOSS
…
Jul 25 20:09:19 cosmos kernel: perf: interrupt took too long (3956 > 3945), lowering kernel.perf_event_max_sample_rate to 50000
Jul 25 20:13:53 cosmos sudo[15334]:       ak : TTY=pts/1 ; PWD=/home/ak/repos/aur/ndstrim-rs-git ; USER=root ; COMMAND=/usr/bin/journalctl -b

So a usb dongle connecting to your phone's hotspot.
After ~30m you obtain a new lease and 53s later the beacon is gone - I suspect that's your phone going through some powersaving and the re-lease somehow gets fumbled on either end?

Not sure whether that's *really* the cause of the random freezes, you draw the journal ~11 minutes later, ~5 minutes after the last interrupt timeout.
Ftr

Jul 25 19:31:57 cosmos kernel: INFO: NMI handler (perf_event_nmi_handler) took too long to run: 1.541 msecs
Jul 25 19:42:35 cosmos kernel: perf: interrupt took too long (2511 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Jul 25 19:52:16 cosmos kernel: perf: interrupt took too long (3156 > 3138), lowering kernel.perf_event_max_sample_rate to 63000
Jul 25 20:09:19 cosmos kernel: perf: interrupt took too long (3956 > 3945), lowering kernel.perf_event_max_sample_rate to 50000

Can you avoid this when stabilizing the network connection eg. by https://wiki.archlinux.org/title/Tethering the phone or not using it at all?

Jul 25 19:31:21 archlinux kernel: Command line: … tsc=reliable clocksource=tsc …

Is this a mitigational effort? Why is that there?

LinuxLover471 · Yesterday 15:06:34

It doesn't show seconds since I don't need second-level accuracy, but I will enable it now.

Yes, I will try SysRQ and then report back.

Both mouse and keyboard are on the back panel, in different ports.

This seems to happen in all of my phones, one from Xiaomi, one from Poco and one from Samsung.

As far as I can recall, it seems to happen much less, if at all, with Tethering or Ethernet.

I have tsc there because it's supposedly faster than HPET, means for latency and performance reasons.

I will report back with what I can after testing!
Thanks!

seth · Yesterday 15:18:49

As far as I can recall, it seems to happen much less, if at all, with Tethering or Ethernet.

Point was whether the "interrupt took too long" messages go away on ethernet.
Do you have (access to) a wifi AP that's not a phone (but some static wifi router)?

I have tsc there because it's supposedly

Okey, try to remove that for the moment…

Arch Linux

#1 2026-07-25 15:17:45

System freezes randomly, likely due to CTRL-EVENT-BEACON-LOSS

#2 2026-07-25 19:11:24

Re: System freezes randomly, likely due to CTRL-EVENT-BEACON-LOSS

#3 Yesterday 15:06:34

Re: System freezes randomly, likely due to CTRL-EVENT-BEACON-LOSS

#4 Yesterday 15:18:49

Re: System freezes randomly, likely due to CTRL-EVENT-BEACON-LOSS

Board footer