[Stable Update] 2024-03-13 - Plasma 5.27.11, Firefox, Thunderbird, AMDVLK, Qemu

I’ve encountered a bug related to the “Do not disturb” mode, and I’m not sure if it’s new with this update. This issue arises specifically after setting “Do not disturb” to automatically disable with a certain condition. Once this condition is met, the system doesn’t still play the sound that usually occurs when adjusting the volume level and when “Do not disturb” is disabled. Fortunately, this issue isn’t major, as manually turning on and turning off “Do Not Disturb” mode restores the volume change sound.

Hi,

Update fine today on stable branch, thanks.

[nls@lap ~]$ date -u
jeu. 04 avril 2024 08:16:15 UTC
[nls@lap ~]$ neofetch
██████████████████  ████████   nls@lap
██████████████████  ████████   -------
██████████████████  ████████   OS: Manjaro Linux x86_64
██████████████████  ████████   Host: NJ50_70CU
████████            ████████   Kernel: 6.6.19-1-MANJARO
████████  ████████  ████████   Uptime: 49 secs
████████  ████████  ████████   Packages: 1637 (pacman)
████████  ████████  ████████   Shell: bash 5.2.26
████████  ████████  ████████   Resolution: 1920x1080
████████  ████████  ████████   DE: Plasma 5.27.11
████████  ████████  ████████   WM: kwin
████████  ████████  ████████   WM Theme: plastik
████████  ████████  ████████   Theme: [Plasma], Breeze [GTK2/3]
████████  ████████  ████████   Icons: oxygen [Plasma], oxygen [GTK2/3]
                               Terminal: konsole
                               CPU: Intel i7-10510U (8) @ 4.900GHz
                               GPU: Intel CometLake-U GT2 [UHD Graphics]
                               Memory: 1278MiB / 15689MiB
[nls@lap ~]$ uname -a
Linux lap 6.6.19-1-MANJARO #1 SMP PREEMPT_DYNAMIC Fri Mar  1 18:16:16 UTC 2024 x86_64 GNU/Linux
[nls@lap ~]$ sudo pacman -Syu
[sudo] password for nls:
:: Synchronising package databases...
 core                                                                          150,4 KiB  1052 KiB/s 00:00 [###############################################################] 100%
 extra                                                                           8,7 MiB  59,3 MiB/s 00:00 [###############################################################] 100%
 community                                                                      29,0   B  1705   B/s 00:00 [###############################################################] 100%
 multilib                                                                      143,9 KiB  7,03 MiB/s 00:00 [###############################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (3) linux66-6.6.24-1  linux66-virtualbox-host-modules-7.0.14-13  mhwd-nvidia-550.67-1

Total Download Size:   130,00 MiB
Total Installed Size:  135,54 MiB
Net Upgrade Size:       -0,12 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux66-6.6.24-1-x86_64                                                       129,7 MiB  83,8 MiB/s 00:02 [###############################################################] 100%
 linux66-virtualbox-host-modules-7.0.14-13-x86_64                              311,4 KiB  15,2 MiB/s 00:00 [###############################################################] 100%
 Total (2/2)                                                                   130,0 MiB  81,1 MiB/s 00:02 [###############################################################] 100%
(3/3) checking keys in keyring                                                                             [###############################################################] 100%
(3/3) checking package integrity                                                                           [###############################################################] 100%
(3/3) loading package files                                                                                [###############################################################] 100%
(3/3) checking for file conflicts                                                                          [###############################################################] 100%
(3/3) checking available disk space                                                                        [###############################################################] 100%
:: Running pre-transaction hooks...
(1/2) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
(2/2) Removing linux initcpios...
:: Processing package changes...
(1/3) upgrading linux66                                                                                    [###############################################################] 100%
(2/3) upgrading linux66-virtualbox-host-modules                                                            [###############################################################] 100%
(3/3) upgrading mhwd-nvidia                                                                                [###############################################################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img --microcode /boot/intel-ucode.img
==> Starting build: '6.6.24-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect --microcode /boot/intel-ucode.img
==> Starting build: '6.6.24-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
==> Image generation successful
(4/5) Refreshing PackageKit...
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p2@/efi/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (23.1.4) on /dev/sdb2
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
[nls@lap ~]$ reboot

after the update

[nls@lap ~]$ uname -a
Linux lap 6.6.24-1-MANJARO #1 SMP PREEMPT_DYNAMIC Thu Apr  4 04:33:21 UTC 2024 x86_64 GNU/Linux
[nls@lap ~]$ 

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

There were kernel updates pushed earlier. It seems quite a few people updated before all the updated packages were pushed. Make sure your mirrors are up to date and check for updates.

2 Likes

Latest Review ISOs are now online. Please test: Release 202404050324 · manjaro/release-review · GitHub

1 Like

Hi,
With all 6.7 kernel versions I get intermittent failure of sound. Some boots it works, some boots it doesn’t. Kernel 6.6 always fine. It’s a Dell Precision 5510 laptop from 2016. When it fails I get this in dmesg:

[   13.259557] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[   13.324320] snd_soc_avs 0000:00:1f.3: cldma_irq_handler sd_status: 0x00000004
[   13.324396] snd_soc_avs 0000:00:1f.3: cldma_irq_handler sd_status: 0x00000004
[   13.327770] snd_soc_avs 0000:00:1f.3: cldma_irq_handler sd_status: 0x00000004
[   13.331424] snd_soc_avs 0000:00:1f.3: NHLT table not found
[   13.331441] snd_soc_avs 0000:00:1f.3: platform has no NHLT
[   13.342014] snd_hda_codec_realtek hdaudioB0D0: autoconfig for ALC3266: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   13.342020] snd_hda_codec_realtek hdaudioB0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   13.342022] snd_hda_codec_realtek hdaudioB0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[   13.342025] snd_hda_codec_realtek hdaudioB0D0:    mono: mono_out=0x0
[   13.342026] snd_hda_codec_realtek hdaudioB0D0:    inputs:
[   13.342028] snd_hda_codec_realtek hdaudioB0D0:      Headset Mic=0x18
[   13.342030] snd_hda_codec_realtek hdaudioB0D0:      Headphone Mic=0x1a
[   13.342031] snd_hda_codec_realtek hdaudioB0D0:      Internal Mic=0x12
[   13.352617] snd_hda_codec_realtek hdaudioB0D0: creating for ALC3266 Analog 0
[   13.392525] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-10ec0298-tplg.bin failed with error -2
[   13.392530] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-10ec0298-tplg.bin" failed: -2
[   13.392590] avs_hdaudio avs_hdaudio.0: trying to load fallback topology hda-generic-tplg.bin
[   13.392616] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-generic-tplg.bin failed with error -2
[   13.392618] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-generic-tplg.bin" failed: -2
[   13.392670] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_component_probe on hdaudioB0D0-platform: -2
[   13.392735] avs_hdaudio avs_hdaudio.0: ASoC: failed to instantiate card -2
[   13.392871] avs_hdaudio: probe of avs_hdaudio.0 failed with error -2
[   13.400532] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 0 0
[   13.400536] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 0
[   13.400538] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 1 1
[   13.400540] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 1
[   13.400541] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 2 2
[   13.400543] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 2
[   13.400591] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-80862809-tplg.bin failed with error -2
[   13.400594] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-80862809-tplg.bin" failed: -2
[   13.400661] avs_hdaudio avs_hdaudio.2: trying to load fallback topology hda-8086-generic-tplg.bin
[   13.400688] snd_soc_avs 0000:00:1f.3: Direct firmware load for intel/avs/hda-8086-generic-tplg.bin failed with error -2
[   13.400690] snd_soc_avs 0000:00:1f.3: request topology "intel/avs/hda-8086-generic-tplg.bin" failed: -2
[   13.400759] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_component_probe on hdaudioB0D2-platform: -2
[   13.400814] avs_hdaudio avs_hdaudio.2: ASoC: failed to instantiate card -2
[   13.400938] avs_hdaudio: probe of avs_hdaudio.2 failed with error -2

The intermittent nature meant it took me a while to be sure it was 6.7.
Using 6.6 for now.


Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

The Nvidia und kernel updates went fine. Also decided to Timeshift back to mid of Februray which was my latest snapshot before I had updgraded to the faulty Xz package. And did all updates after that date again - which went fine too :slight_smile:

I however do not remember and can’t find it on the forum what to do with this (at least I can’t comprehend):

[ALPM] warning: directory permissions differ on /usr/share/polkit-1/rules.d/
filesystem: 750  package: 755

Can someone please tell me if I should change those.

1 Like

According to @Yochanan you should change it.

Continuing the discussion from [Unstable Update] January 2024 Edition:

2 Likes

Had a flickering issue on my 2nd monitor with kernel 6.8.4−1

Swapping back to the latest LTS fixed it.

2 Likes

i think one of these updates broke jDownloader for me. when i start it, i get logged out. i logged in again, started jD again and my PC froze. press reset button. after boot i started jD and it logged me out again.

[2024-04-07T09:52:38+0200] [ALPM] upgraded xorg-xwayland (23.2.4-2 → 23.2.5-0)
[2024-04-07T09:52:38+0200] [ALPM] upgraded xorg-server (21.1.11-1 → 21.1.12-0)
[2024-04-07T09:52:38+0200] [ALPM] upgraded xorg-server-common (21.1.11-1 → 21.1.12-0)
[2024-04-07T09:52:38+0200] [ALPM] upgraded mhwd-nvidia (550.54.14-2 → 550.67-1)
[2024-04-07T09:52:38+0200] [ALPM] upgraded manjaro-release (23.1.3-1 → 23.1.4-1)
[2024-04-07T09:52:38+0200] [ALPM] upgraded linux68 (6.8.0rc6-1 → 6.8.4-1)

1 Like

Regarding ntfs3 mounting issues on kernel 6.8.
The solution posted in Known Issues, still doesn’t let me mount ntfs partitions.

Kernel 6.6 / 6.7 fstab using Fuse/ntfs-3g:

UUID=B0A0696BA069394C /mnt/storage ntfs-3g noatime,nofail,uid=1000,gid=1000,umask=022,utf8 0 0

Kernel 6.8 fstab tested 2 entries:

1) UUID=B0A0696BA069394C /mnt/storage ntfs3 noatime,nofail,user_id=1000,group_id=1000,allow_other,utf8 0 0
2) UUID=B0A0696BA069394C /mnt/storage ntfs3 noatime,nofail,uid=1000,gid=1000,umask=022,utf8 0 0

Logs:

$ Dmesg | grep ntfs3
[   46.561385] request_module fs-ntfs3 succeeded, but still no fs?
$ Journalctl
apr 08 13:03:48 Infinity kernel: /dev/sdc1: Can't open blockdev

Manually mounting, disabled ntfs mount entry in fstab, result:

$ sudo mount -t ntfs3 /dev/sdc1 /mnt/storage/
mount: /mnt/storage: unknown filesystem type 'ntfs3'.
       dmesg(1) may have more information after failed mount system call.

After this tried to blacklist ntfs3 via modprobe.d
Ntfs3 module was now not loaded on boot, yet Fuse (ntfs-3g) still failed to mount the ntfs partition:

$ sudo mount -t ntfs-3g /dev/sdc1 /mnt/storage/
fuse: mount failed: Device or resource busy

Booting into Kernel 6.6/6.7 the ntfs partition just mounts again using Fuse/ntfs-3g.

Hope this feedback is somewhat useful.

Thats true. But the bug is in the free nouveau driver i want to use. @pheiduck That is what i dont understand, that there should be no bug. Its obvisually that there is a bug in nouveau in combination with sddm-greeter and Nvidia Geforce210. But if they dont want to know it, its ok for me too. And you are right, @soundofthunder, upgrading is the only real way.

At this point in time it would be the best advice. The latest official driver for the GeForce 210 was 340.108 which was released in 2019. So, even the equivilent maintained drivers of that vintage are now too old, I’m guessing. I think the oldest Nvida driver still (barely) supported is 470.

I’m not certain exactly how supportive Nouveau is for that model, but it’s likely the only game in town for that model today. Cheers.

2 Likes

Recent security fixes in Xorg broke Java programs: Bug #2060354 “Segfaults and assertion failures in Xorg's render/...” : Bugs : xorg-server package : Ubuntu

ahhh ok. thx

Are you gonna jump from Gnome 45.4 to Gnome 46? Won’t there be Gnome 45.5? Thank you!

Testing has gnome 46. Since unstable → testing → stable. Expect gnome 46 in stable when there are no issues in testing.

2 Likes

After the Kernel Update i got exactly every 10 min this:

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

Can’t find a solution yet :melting_face:

:man_shrugging: Don’t shoot the messenger. :stuck_out_tongue_closed_eyes:

I won’t, don’t worries i just wanted to post it here. Because i think its fits to the info about the new Kernel update, that’s all :wink:

1 Like

4 posts were split to a new topic: After stable update 2024-03-13 system fails to shutdown