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

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:

That workqueue patch wasn’t backported to any kernel older than 6.6. So if you’re still getting workqueue errors on 6.1 it’s not related to that patch, it’s something else. I have no idea what that could be, sorry.

1 Like

Well in the situation where i’am right now, its equal to BSOD.

Journal doesn’t show anything why the system was freezing and this other new error’s in journal points at the emptiness.

I have a Windows retro feeling right now. :face_exhaling:

6.26 still shows this errors:

$ journalctl -p 3 -xb
Apr 13 10:06:05 koboldx-z170 kernel: x86/cpu: SGX disabled by BIOS.
Apr 13 10:06:06 koboldx-z170 kernel: 
Apr 13 10:06:11 koboldx-z170 systemd[1104]: /run/user/1000/systemd/generator.late/app-nvidia\x2dsettings@autostart.service:18>
Apr 13 10:06:11 koboldx-z170 systemd[1104]: /run/user/1000/systemd/generator.late/app-nvidia@autostart.service:18: WorkingDir>
Apr 13 10:06:14 koboldx-z170 pulseaudio[1321]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner: Could n>
Apr 13 10:16:15 koboldx-z170 kernel: BUG: workqueue leaked lock or atomic: kworker/4:0/0x7fffffff/45
                                          last function: ata_scsi_dev_rescan
Apr 13 10:16:15 koboldx-z170 kernel: BUG: scheduling while atomic: kworker/4:0/45/0x00000000

At least PC is stable :see_no_evil: :hear_no_evil: :speak_no_evil:

Hello,

I am just checking in as I am experiencing the same issue with 6.8 and 6.6. After reading the thread I installed kernel 6.1 and I am not seeing any problem in the logs for now. Let me know if I can help testing something.

I came here from the Arch forum.

System:
  Host: lenovo Kernel: 6.1.85-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 5.27.11 Distro: Manjaro Linux
Machine:
  Type: Laptop System: LENOVO product: 81LK v: IdeaPad L340-15IRH Gaming
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN
    serial: <superuser required> UEFI: LENOVO v: BGCN17WW date: 03/21/2019
Battery:
  ID-1: BAT0 charge: 39.9 Wh (99.0%) condition: 40.3/45.0 Wh (89.6%)
CPU:
  Info: 6-core model: Intel Core i7-9750H bits: 64 type: MT MCP cache:
    L2: 1.5 MiB
  Speed (MHz): avg: 823 min/max: 800/4500 cores: 1: 800 2: 886 3: 900 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 900
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nvidia
    v: 550.67
  Device-3: Lite-On Integrated Camera driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.12 driver: X:
    loaded: modesetting,nvidia unloaded: nouveau dri: iris gpu: i915
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.2-manjaro1.1
    renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  API: Vulkan v: 1.3.279 drivers: nvidia,intel surfaces: xcb,xlib
Audio:
  Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
  API: ALSA v: k6.1.85-1-MANJARO status: kernel-api
  Server-1: PulseAudio v: 17.0 status: active
Network:
  Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
    driver: rtw_8821ce
  IF: wlp7s0 state: up mac: 28:39:26:45:9b:2b
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp8s0 state: down mac: 98:fa:9b:37:d7:f5
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 3 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.14 TiB used: 249.33 GiB (21.3%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GDHTNG-8310A
    size: 238.47 GiB
  ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-24Z10
    size: 931.51 GiB
Partition:
  ID-1: / size: 196.67 GiB used: 125.98 GiB (64.1%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 288 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 42.0 C pch: 40.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.64 GiB used: 3.22 GiB (42.1%)
  Processes: 319 Uptime: 55m Shell: Zsh inxi: 3.3.34
1 Like

Hmm let me try again 6.1 then… did you waited 10min after boot for the errrors to show up?

Are you on Manjaro’s stable release branch?

Did you had actually real bugs related this error logs?

I guess i’m lucky that i only see this error’s that not harm the system stability.

My AMD Laptop which used the same Kernel/Software packages btw. don’t show this error’s.
Maybe this is a Intel problem?

It has been up for over 6 hours now without any of the error messages in the journal.

Yes.

Not sure what you mean but with 6.6 and 6.8 I experienced a kernel panic after a few hours.

Same error’s with Kernel: 6.1.85-1 :zipper_mouth_face:

The last stable release update with Kernel: 6.6.30-2 fixed the error message for me.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.