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?
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.
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…
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?
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.
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?
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
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:
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
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.
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.