Os Freezing Issue with RT Bore and RT Bore LTO Kernels 🚨

Feedback Bugreports
1

:memo: Problem Description

RT Bore and RT Bore LTO were freezing under actual workload, even on different hosts. The symptoms progressed as follows:

  1. :computer_mouse: Cursor Stops Moving: Initially, the cursor would freeze.
  2. :movie_camera: Video Pauses: Next, video playback would halt.
  3. :speaker_high_volume: Audio Freezes: Then, audio output would stop.
  4. :snowflake: Complete System Freeze: Finally, the entire system would lock up, requiring a forced shutdown and reboot using the system’s built-in capability.

Had to switch to the default kernel : cachy-v3/linux-cachyos.

2

What is “actual workload”? Is it just watching YouTube videos? Note that PREEMPT_RT isn’t meant to be run for “actual workloads”.

3

and also which version kernel ? 6.14 or before ?

4

v3 (RT Bore and RT Bore LTO) freezes, even just bore optimized on v3.
Gotta do a better job so that those optimizations lasts under actual duty / four monitor set up and not freezes …
Screenshot_20250404_101955

actual workloads means actual workloads
100 tabs across 5 browsers, one with three profiles {3 separate window / process}

❯ hyfetch
                                                          prince@cachyos-x8664
           .-------------------------:                    --------------------
          .+=========================.                    OS: CachyOS x86_64
         :++===++==================-       :++-           Host: Blade 18 - RZ09-0509 (10.04)
        :*++====+++++=============-        .==:           Kernel: Linux 6.14.0-1-cachyos-server
       -*+++=====+***++==========:                        Uptime: 1 day, 2 hours, 20 mins
      =*++++========------------:                         Packages: 1212 (pacman), 16 (flatpak)
     =*+++++=====-                     ...                Shell: zsh 5.9
   .+*+++++=-===:                    .=+++=:              Display (BOE0C87): 2560x1600 @ 300 Hz in 18" [Built-in]
  :++++=====-==:                     -*****+              DE: KDE Plasma 6.3.4
 :++========-=.                      .=+**+.              WM: KWin (Wayland)
.+==========-.                          .                 WM Theme: Breeze
 :+++++++====-                                .--==-.     Theme: Breeze (CachyOSNordLightly) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
  :++==========.                             :+++++++:    Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
   .-===========.                            =*****+*+    Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
    .-===========:                           .+*****+:    Cursor: breeze (24px)
      -=======++++:::::::::::::::::::::::::-:  .---:      Terminal: tilix 1.9.6
       :======++++====+++******************=.             Terminal Font: CaskaydiaCove Nerd Font Mono (10pt)
        :=====+++==========++++++++++++++*-               CPU: Intel(R) Core(TM) i9-14900HX (32) @ 5.80 GHz
         .====++==============++++++++++*-                GPU 1: NVIDIA GeForce RTX 4090 Laptop GPU [Discrete]
          .===+==================+++++++:                 GPU 2: Intel Raptor Lake-S UHD Graphics @ 1.65 GHz [Integrated]
           .-=======================+++:                  Memory: 12.48 GiB / 30.97 GiB (40%)
             ..........................                   Swap: 0 B / 62.97 GiB (0%)
                                                          Disk (/): 122.02 GiB / 1.82 TiB (7%) - xfs
                                                          Local IP (enp46s0): 1x.1x.1x4.159/22
                                                          Battery (Blade): 100% [AC Connected]
                                                          Locale: en_US.UTF-8
5

I have been here when nobody was.
make full proof kernels naim.
hk does not has sufficient space to send rockets to mars.
I m a mainlander.

Screenshot_20250328_201903
Screenshot_20250328_2019031095Ă—109 6.78 KB

6

Those workloads doesn’t fit the usecase of PREEMPT_RT, instability is to be expected. Weird that you’re seeing freezes in BORE kernel too, since that is pretty much identical to default.

Without any logs, there’s nothing I can do. There’s also not much that I can do as a downstream maintainer. Test the Arch kernel, if it freezes there then it’s upstream’s problem.

sudo pacman -U https://archive.archlinux.org/packages/l/linux/linux-6.14.arch1-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/l/linux-headers/linux-headers-6.14.arch1-1-x86_64.pkg.tar.zst