Kernel 6.6.25: BUG: workqueue leaked lock or atomic: kworker ... last function: ata_scsi_dev_rescan

Hello,
i had a stable Manjaro/KDE install for some year’s now. Today i was doing Video Encoding in background and i played X-Com2, then out of nowhere my sound stuck, the picture freeze and i saw my Keyboard led’s blinking (reverse shift and Scroll but Num wasn’t blinking).

I pressed by mistake crtl+alt+print+f several times, but nothing happend (i saw later in my documents that it should be alt+print+f) after a (hardreset) restart there was a journal restored message showing up.

Didn’t Reisub working because of my blinking keyboard led’s or maybe the freeze was to heavy and even Reisub couldn’t restore it or was it maybe related to my wrong shortcut combo?

How can i check the restored journal?

$ inxi --admin --verbosity=5 --filter --no-host --width:

System:
  Kernel: 6.6.25-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/vmlinuz-6.6-x86_64
    root=UUID=eb235aa7-d461-413d-800e-ea57385703fb rw quiet
    sysrq_always_enabled=1 nvidia_drm.modeset=1 retbleed=off
    resume=UUID=717b267e-7322-4bf9-a840-f1210d422d1a udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 info: frameworks
    v: 5.115.0 wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: Z170X-UD3 v: N/A
    serial: <superuser required>
  Mobo: Gigabyte model: Z170X-UD3-CF v: x.x serial: <superuser required>
    uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F23d
    date: 12/01/2017
Memory:
  System RAM: total: 16 GiB available: 15.58 GiB used: 3.67 GiB (23.6%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: no module installed
  Device-2: ChannelA-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
  Device-3: ChannelB-DIMM0 type: no module installed
  Device-4: ChannelB-DIMM1 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2800 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: G.Skill part-no: F4-2800C16-8GRR
    serial: N/A
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 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: 4500 high: 4502 min/max: 800/4700 scaling:
    driver: intel_pstate governor: performance cores: 1: 4502 2: 4500 3: 4500
    4: 4500 5: 4500 6: 4500 7: 4500 8: 4500 bogomips: 64026
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  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: reg_file_data_sampling status: Not affected
  Type: retbleed status: Vulnerable
  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: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti Rev. A] vendor: Micro-Star MSI
    driver: nvidia v: 550.67 alternate: nouveau,nvidia_drm non-free: 545.xx+
    status: current (as of 2024-02; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: DP-3 empty: DP-1, DP-2, HDMI-A-1, Unknown-1
    bus-ID: 01:00.0 chip-ID: 10de:1e07 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.12 compositor: kwin_x11 driver: X:
    loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 122 s-size: 532x302mm (20.94x11.89")
    s-diag: 612mm (24.08")
  Monitor-1: DP-3 mapped: DP-4 note: disabled model: Dell S2417DG
    serial: <filter> built: 2018 res: 2560x1440 dpi: 123 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.67 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
    memory: 10.74 GiB
  API: Vulkan v: 1.3.279 layers: 5 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 2080 Ti driver: nvidia v: 550.67 device-ID: 10de:1e07
    surfaces: xcb,xlib
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA TU102 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f7 class-ID: 0403
  Device-3: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
    Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 0b:00.0 chip-ID: 1102:0012 class-ID: 0403
  API: ALSA v: k6.6.25-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.3 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:2
    chip-ID: 0a12:0001 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
Drives:
  Local Storage: total: 5.93 TiB used: 415.27 GiB (6.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: MP600 PRO LPX
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EIFM31.6 temp: 33.9 C
    scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HDN724030ALE640
    size: 2.73 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: A5E0 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: Portable SSD T5
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: USB
    rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter>
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 88.61 GiB size: 86.66 GiB (97.80%) used: 19.21 GiB (22.2%)
    fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: N/A
    uuid: eb235aa7-d461-413d-800e-ea57385703fb
  ID-2: /boot raw-size: 2.93 GiB size: 2.82 GiB (96.15%)
    used: 439.8 MiB (15.2%) fs: ext3 dev: /dev/sdc3 maj-min: 8:35 label: N/A
    uuid: cbfeca98-b99d-4383-9ded-fe66cd598006
  ID-3: /home raw-size: 332.03 GiB size: 325.75 GiB (98.11%)
    used: 16.64 GiB (5.1%) fs: ext4 dev: /dev/sdc4 maj-min: 8:36 label: N/A
    uuid: ada4a6a2-bd0a-4652-b386-7c637bba7ee9
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 7.81 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdc2 maj-min: 8:34 label: N/A
    uuid: 717b267e-7322-4bf9-a840-f1210d422d1a
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: nvidia temp: 36 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 25%
Info:
  Processes: 264 Power: uptime: 56m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.22 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: 1548 pm: pacman pkgs: 1542 libs: 450 tools: pamac pm: flatpak
    pkgs: 6 Compilers: clang: 16.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.26
    running-in: konsole inxi: 3.3.33

Edit from April/09: After investigation, i found out this was just a RARE Freeze, my system is still stable and i still can play my games… but the Topic is around this new Journal BUG logs now, that probably introduced with the new Kernel Patch from April/05

1 Like
  1. Can you confirm whether the REISUB option kernel.sysrq=1 is activated?

  2. Check journalctl -p err -b -1 after hardreset.

1 Like

Yes 100%, i used it in the past…

My freeze accured at 20:55 (35min ago) when i look at the unfinished Shotcut Video Encoding Job.

journalctl -p err -b -1:

Apr 07 15:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:0/0x7fffffff/2960914
                                          last function: ata_scsi_dev_rescan
Apr 07 15:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:0/2960914/0x00000000
Apr 07 15:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/2:2/0x7fffffff/2555628
                                          last function: ata_scsi_dev_rescan
Apr 07 15:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/2:2/2555628/0x00000000
Apr 07 16:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/0:2/0x7fffffff/2510416
                                          last function: ata_scsi_dev_rescan
Apr 07 16:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/0:2/2510416/0x00000000
Apr 07 16:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/0:2/0x7fffffff/2510416
                                          last function: ata_scsi_dev_rescan
Apr 07 16:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/0:2/2510416/0x00000000
Apr 07 16:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/0:2/0x7fffffff/2510416
                                          last function: ata_scsi_dev_rescan
Apr 07 16:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/0:2/2510416/0x00000000
Apr 07 16:25:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/5:2/0x7fffffff/162985
                                          last function: ata_scsi_dev_rescan
Apr 07 16:25:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/5:2/162985/0x00000000
Apr 07 16:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 16:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 16:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/4:2/0x7fffffff/2928682
                                          last function: ata_scsi_dev_rescan
Apr 07 16:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/4:2/2928682/0x00000000
Apr 07 16:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:1/0x7fffffff/1869471
                                          last function: ata_scsi_dev_rescan
Apr 07 16:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:1/1869471/0x00000000
Apr 07 17:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 17:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 17:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 17:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 17:25:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 17:25:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 17:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/5:2/0x7fffffff/162985
                                          last function: ata_scsi_dev_rescan
Apr 07 17:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/5:2/162985/0x00000000
Apr 07 17:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/5:2/0x7fffffff/162985
                                          last function: ata_scsi_dev_rescan
Apr 07 17:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/5:2/162985/0x00000000
Apr 07 17:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:0/0x7fffffff/3081355
                                          last function: ata_scsi_dev_rescan
Apr 07 17:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:0/3081355/0x00000000
Apr 07 17:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:1/0x7fffffff/1869471
                                          last function: ata_scsi_dev_rescan
Apr 07 17:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:1/1869471/0x00000000
Apr 07 18:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:1/0x7fffffff/1869471
                                          last function: ata_scsi_dev_rescan
Apr 07 18:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:1/1869471/0x00000000
Apr 07 18:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 18:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 18:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 18:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 18:25:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/5:2/0x7fffffff/162985
                                          last function: ata_scsi_dev_rescan
Apr 07 18:25:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/5:2/162985/0x00000000
Apr 07 18:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/5:2/0x7fffffff/162985
                                          last function: ata_scsi_dev_rescan
Apr 07 18:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/5:2/162985/0x00000000
Apr 07 18:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 18:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 18:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/2:2/0x7fffffff/2555628
                                          last function: ata_scsi_dev_rescan
Apr 07 18:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/2:2/2555628/0x00000000
Apr 07 19:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:1/0x7fffffff/1869471
                                          last function: ata_scsi_dev_rescan
Apr 07 19:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:1/1869471/0x00000000
Apr 07 19:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:0/0x7fffffff/3081669
                                          last function: ata_scsi_dev_rescan
Apr 07 19:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:0/3081669/0x00000000
Apr 07 19:25:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:1/0x7fffffff/1727621
                                          last function: ata_scsi_dev_rescan
Apr 07 19:25:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:1/1727621/0x00000000
Apr 07 19:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 19:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 19:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/0:2/0x7fffffff/2510416
                                          last function: ata_scsi_dev_rescan
Apr 07 19:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/0:2/2510416/0x00000000
Apr 07 19:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:1/0x7fffffff/1727621
                                          last function: ata_scsi_dev_rescan
Apr 07 19:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:1/1727621/0x00000000
Apr 07 19:55:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:1/0x7fffffff/1727621
                                          last function: ata_scsi_dev_rescan
Apr 07 19:55:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:1/1727621/0x00000000
Apr 07 20:05:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:1/0x7fffffff/2930093
                                          last function: ata_scsi_dev_rescan
Apr 07 20:05:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:1/2930093/0x00000000
Apr 07 20:15:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:2/0x7fffffff/3110959
                                          last function: ata_scsi_dev_rescan
Apr 07 20:15:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:2/3110959/0x00000000
Apr 07 20:25:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/1:2/0x7fffffff/3141499
                                          last function: ata_scsi_dev_rescan
Apr 07 20:25:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/1:2/3141499/0x00000000
Apr 07 20:35:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/1:2/0x7fffffff/3141499
                                          last function: ata_scsi_dev_rescan
Apr 07 20:35:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/1:2/3141499/0x00000000
Apr 07 20:45:11 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/3:1/0x7fffffff/1869471
                                          last function: ata_scsi_dev_rescan
Apr 07 20:45:11 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/3:1/1869471/0x00000000

So 10min before the freeze happen, stopped the journal :frowning:
Should i worried about this bug reports? My system was running for 2 days and no problem’s.

Edit:
i just tested it with the wrong combo crlt+alt+print+f (while the system was not freezing) and it was working 3 times as the log shows:

Apr 07 21:35:25 koboldx-z170 kernel: Out of memory: Killed process 2048 (Web Content) total-vm:2451920kB, anon-rss:14708kB, f>
Apr 07 21:35:35 koboldx-z170 kernel: Out of memory: Killed process 2199 (shotcut) total-vm:3686604kB, anon-rss:394208kB, file>
Apr 07 21:35:39 koboldx-z170 kernel: Out of memory: Killed process 1261 (plasmashell) total-vm:2159896kB, anon-rss:202456kB, >

I have to add, i never played x-com2 and used video-encoding in the same time. But i played other games while i used video-encoding.

If the keyboard LEDs are blinking, then there’s a kernel panic, which in turn means that the kernel is dead. Therefore, the Magic SysRq keys won’t have any effect.

It would be like trying to start a car with an internal combustion engine that doesn’t have a fuel tank attached to it. :wink:

1 Like

Hmmm good info, didn’t know this yet about the blinking LED’s.

So i think the combo between video encoding + x-com2 was to much for my hardware then.
And i need to look for a Hardware Problem? Like CPU Overclock reducing even more?

I had Stability problem’s as i joind this community 4 year’s ago, and i had to reduce my OC from 4,7Ghz that i still use in Windows for VR (5k) Simracing, to 4,5Ghz in Linux for a 3 year’s stable Manjaro experience. CPU cooling alert is set on 70° on my Skylake… so i have a pretty good cooled CPU and 300Mhz isn’t so much OC… strange.

One of the more likely culprits — especially when gaming — is temperature, and overclocking could definitely be increasing the risk of such an occurrence.

1 Like

My main question is now, should i only look for HW issue or what lead to the Dead Kernel situation?

Or maybe it was the nvidia-update from yesterday?

First and foremost, set your CPU/GPU clocks to their recommended values. There’s no point in trying to find other potential causes when your hardware is not functioning at factory specifications.

Continuing with the automotive metaphor, there’s no point in complaining about your headlights being defective after you’ve just rammed your car into a wall head-on.

GPU was never overclocked… I just interested to understand the difference about OS stability.

Why my CPU clock in Windows run stable with 4,7Ghz where i used CPU heavy Simracing Pcars2/AMS2 while running Prime95 on all cores/treads at the same time STABLE. But under Linux my CPU run’s into stability problems and can’t even hold 4,5 Ghz when im playing x-com2+video encoding, while my Mainboard always used 1,3Vcore for both settings because of a BIOS OC.

Is it possible that Linux relys more on stability as Windows?

Yes. Windows doesn’t even properly check the hardware.

Sure it does…

Windows: Is the machine powered on?
System: Yes.
Windows: Hardware receiving power?
System: Yes. Do you want to do something with it?
Windows: Yes. Here's the request.
System: Here the response.
Windows: BSOD.

What’s wrong with that? :cowboy_hat_face:

5 Likes

I normally used always the command:

journalctl -p 3 -xb

To look for bugs… and out of nowhere my logs are filled with messages like this since yesterday,
but before that crash even happen, so i don’t think this single crash lead to file corruption that shows errors like this:

Apr 08 14:47:56 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/6:0/0x7fffffff/57
                                          last function: ata_scsi_dev_rescan
Apr 08 14:47:56 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/6:0/57/0x00000000
Apr 08 14:57:56 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/4:2/0x7fffffff/254
                                          last function: ata_scsi_dev_rescan
Apr 08 14:57:56 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/4:2/254/0x00000000
Apr 08 15:07:56 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:0/0x7fffffff/63
                                          last function: ata_scsi_dev_rescan
Apr 08 15:07:56 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:0/63/0x00000000

I just had a fresh PC start today, i openend firefox and watched a youtube video and there are this errors now… i never saw errors like this before… what is going on there?

Did journalctl -p err -b -1 somehow changed my journalctl -p 3 -xb… i don’t understand whats happen to my system now… was this bugs reports filtered out before and now just on the display because of the other journal error command?

Has my system now a problem? How serious are this log reports? Besides the single crash yesterday my system is stable, at least that what i thought…

There is no right answer to you.

But I guess that no one reported the same issue of Kernel 6.6 LTS today, except just you.

I think your hardware is probably a problem because:

Some part of your hardware would likely have reached a limit of its lifespan.

How old are the CPU, motherboard and RAM?

1 Like

I bought everything as my Skylake was released, that was 09/2015 i think.

I wouldn’t to much focus on my one time freezing system, maybe its related but i don’t think the freeze will happen again when i playing x-com2 again (without video encoding at the same time). At least i started video-encoding yesterday again for 3 hours and everything was finished without any problems, just while browsing instead gaming.

I just want to find out, what this error’s pointing too. When i google around i find nothing related,
no real connection to my system.

Should i stay away from doing a Systembackup now? Will probably my CPU/RAM miscalculate something when i refresh my Backup Drive?

Kernel 6.6.25 reverted a backported workqueue patch which was causing regressions, it was the only change from 6.6.24. Are those journal messages from before or after you updated to 6.6.25?

1 Like

Holy crap i think this could be related to my error’s.

I regulary update my system… so i’m updating my system with a max 3-4 days delay, since stable update was released 03/13 i had it updated since 03/15 i would bet… so yeah this journal messages are created with Kernel 6.6.25

@MrLavender
Is there something i can do about it? Writing a E-Mail to the developer or something?

Or maybe just switching to Kernel 6.1 and hoping its not there backported too?

6.6.25 wasn’t part of last stable update, it was only released a few days ago. I got it on Friday. So check /var/log/pacman.log to see exactly when you installed it compared to those log messages, because those messages are what 6.6.25 was supposed to fix.

1 Like

Okay confusing… because this is what written in the last stable update:

I think i got it, it was released together with the new nvidia drivers, i also posted the success in this Forum… because other forum member’s reported blackscreen’s after the update:

[2024-04-05T13:03:10+0200] [PAMAC] synchronizing package lists
[2024-04-05T13:06:17+0200] [ALPM] running '60-mkinitcpio-remove.hook'...
[2024-04-05T13:06:17+0200] [ALPM] running 'kernel-alive-pre.hook'...
[2024-04-05T13:06:18+0200] [ALPM] transaction started
[2024-04-05T13:06:19+0200] [ALPM] upgraded nvidia-utils (550.54.14-3 -> 550.67-1)
[2024-04-05T13:06:19+0200] [ALPM-SCRIPTLET] xorg configuration symlink valid...
[2024-04-05T13:06:19+0200] [ALPM-SCRIPTLET] If you run into trouble with CUDA not being available, run nvidia-modprobe first.
[2024-04-05T13:06:19+0200] [ALPM-SCRIPTLET] If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
[2024-04-05T13:06:19+0200] [ALPM] upgraded lib32-nvidia-utils (550.54.14-1 -> 550.67-1)
[2024-04-05T13:06:19+0200] [ALPM-SCRIPTLET] xorg configuration symlink valid...
[2024-04-05T13:06:19+0200] [ALPM] upgraded libxnvctrl (550.54.14-1 -> 550.67-1)
[2024-04-05T13:06:20+0200] [ALPM] upgraded linux66 (6.6.19-1 -> 6.6.25-1)
[2024-04-05T13:06:20+0200] [ALPM] upgraded linux66-nvidia (550.54.14-2 -> 550.67-4)
[2024-04-05T13:06:20+0200] [ALPM] upgraded mhwd-nvidia (550.54.14-2 -> 550.67-1)
[2024-04-05T13:06:20+0200] [ALPM] upgraded nvidia-settings (550.54.14-1 -> 550.67-1)
[2024-04-05T13:06:20+0200] [ALPM] upgraded xorg-server-common (21.1.11-1 -> 21.1.12-0)
[2024-04-05T13:06:20+0200] [ALPM] upgraded xorg-server (21.1.11-1 -> 21.1.12-0)
[2024-04-05T13:06:20+0200] [ALPM] transaction completed
[2024-04-05T13:06:21+0200] [ALPM] running '20-systemd-sysusers.hook'...
[2024-04-05T13:06:21+0200] [ALPM] running '30-systemd-daemon-reload-system.hook'...
[2024-04-05T13:06:21+0200] [ALPM] running '30-systemd-udev-reload.hook'...
[2024-04-05T13:06:21+0200] [ALPM] running '30-systemd-update.hook'...
[2024-04-05T13:06:21+0200] [ALPM] running '60-depmod.hook'...
[2024-04-05T13:06:24+0200] [ALPM] running '90-mkinitcpio-install.hook'...
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/intel-ucode.img
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.6.25-1-MANJARO'
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-04-05T13:06:24+0200] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-04-05T13:06:26+0200] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET] ==> Image generation successful
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET] ==> Using default configuration file: '/etc/mkinitcpio.conf'
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET] ==> Starting build: '6.6.25-1-MANJARO'
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET]   -> Running build hook: [kms]
[2024-04-05T13:06:28+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'ast'
[2024-04-05T13:06:33+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2024-04-05T13:06:33+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'xhci_pci'
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET]   -> Running build hook: [keymap]
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qed'
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla2xxx'
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'qla1280'
[2024-04-05T13:06:34+0200] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: 'bfa'
[2024-04-05T13:06:35+0200] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2024-04-05T13:06:36+0200] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2024-04-05T13:06:37+0200] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2024-04-05T13:06:37+0200] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
[2024-04-05T13:06:46+0200] [ALPM-SCRIPTLET] ==> Image generation successful
[2024-04-05T13:06:46+0200] [ALPM] running '90-nvidia-utils.hook'...
[2024-04-05T13:06:46+0200] [ALPM] running '99-update-grub.hook'...
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Generating grub configuration file ...
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Found theme: /usr/share/grub/themes/manjaro/theme.txt
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Found linux image: /boot/vmlinuz-6.6-x86_64
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Warning: os-prober will not be executed to detect other bootable partitions.
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Systems on them will not be added to the GRUB boot configuration.
[2024-04-05T13:07:00+0200] [ALPM-SCRIPTLET] Check GRUB_DISABLE_OS_PROBER documentation entry.
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] Found memtest86+ image: /boot/memtest86+/memtest.bin
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] done
[2024-04-05T13:07:01+0200] [ALPM] running 'dbus-reload.hook'...
[2024-04-05T13:07:01+0200] [ALPM] running 'kernel-alive-post.hook'...
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] e[1;1me[1;32m==>e[1;0me[1;1m Warning:
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	 -> Kernel has been updated. Modules of the current kernel
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	 -> have been backed up so you can continue to use your
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	 -> computer. However, the new kernel will only work
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	 -> at next boot.
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	e[1;0m
[2024-04-05T13:07:01+0200] [ALPM-SCRIPTLET] 	e[1;0m
[2024-04-05T13:07:01+0200] [ALPM] running 'update-desktop-database.hook'...

This all make sense now, why this error’s surprising me now… so yeah my journals was from today and yesterday and the Kernel Update 6.6.25 was 3 days ago from 05.april.

Maybe the Kernel update is just to new, that’s why nobody else complained about it yet?

I created a snapshot before i updated the kernel+nvidia drivers When this error’s vanished after the rollback to 6.6.19 it proofes that my system is okay… but i have to update anyways otherwise i run into a regression sooner or later.

So the best way for me is now to switch to LTS Kernel 6.1?

That post gets updated until the next Stable update arrives. Was last edited 6th April, presumably to update the current supported kernel versions.

If it’s causing you problems that’s one possible solution. Or could try 6.8. I don’t have those workqueue errors myself either before or after 6.6.25.

1 Like

Is it possible that this workqueue patch is backported to 6.1 Kernel also?

Because i getting the same workqueue errors under 6.1 now :frowning:

I don’t see a seriously link to this statement… anyways, i found some strange stuff around the internet where some people reported this bug in some other forum’s, someone hinted a connected i-Pad or something like that and i remember that i bought a new Sharkoon Mouse for my PC, 2 weeks ago.

When i look closer at the error logs, i see precisely every 10minutes this journal message… strange huh?
Hmm i disconnected my mouse 2min before the 10min interval should showed up, but the error was listen in journal.

Edit:
Uninstalled 6.1 LTS and rebooted, exactly 10min after the Boot was finished the error showed in journal, system was just idle:

$ journalctl -p 3 -xb
Apr 09 14:08:29 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Apr 09 14:08:30 koboldx-z170 kernel: 
Apr 09 14:08:35 koboldx-z170 systemd[1210]: /run/user/1000/systemd/generator.late/app-nvidia\x2dsettings@autostart.service:18>
Apr 09 14:08:35 koboldx-z170 systemd[1210]: /run/user/1000/systemd/generator.late/app-nvidia@autostart.service:18: WorkingDir>
Apr 09 14:08:38 koboldx-z170 pulseaudio[1427]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Apr 09 14:18:39 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/7:3/0x7fffffff/1312
                                          last function: ata_scsi_dev_rescan
Apr 09 14:18:39 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/7:3/1312/0x00000000

I booted in Manjaro Live Environment with Kernel 6.6.10 i was waiting 25min and no error like this shown up. Should be a sign that its not serious and that’s something related to the new kernels?

So maybe the problem Backported to 6.1 too, i try older LTS next :face_with_diagonal_mouth: