Odd Warning Messages In dmesg

As I was tracking down a webcam issue, I noticed quite a few of the messages below when viewing the output from dmesg.

[ 8996.385572] WARNING: CPU: 2 PID: 2288 at ../include/linux/dma-fence.h:478 amdgpu_sync_keep_later+0xab/0xc0 [amdgpu]
[ 8996.385840] Modules linked in: bnep bluetooth ecdh_generic vmnet(OEX) ppdev parport_pc parport vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OEX) af_packet iscsi_ibft iscsi_boot_sysfs rfkill dmi_sysfs joydev uvcvideo snd_usb_audio videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_usbmidi_lib videobuf2_common snd_rawmidi snd_seq_device videodev mc edac_mce_amd kvm_amd ccp kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi irqbypass snd_hda_intel wmi_bmof snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec r8169 pcspkr k10temp fam15h_power realtek i2c_piix4 mdio_devres snd_hda_core libphy snd_hwdep snd_pcm snd_timer snd soundcore gpio_amdpt gpio_generic button acpi_cpufreq fuse configfs ip_tables x_tables ext4 crc16 mbcache jbd2 hid_microsoft ff_memless hid_generic crc32_pclmul sr_mod crc32c_intel cdrom usbhid sd_mod t10_pi ghash_clmulni_intel amdgpu aesni_intel crypto_simd drm_ttm_helper ttm mfd_core cryptd iommu_v2 gpu_sched i2c_algo_bit
[ 8996.385891]  drm_kms_helper xhci_pci xhci_pci_renesas ahci syscopyarea sysfillrect sysimgblt fb_sys_fops sp5100_tco(N) ehci_pci ehci_hcd cec libahci xhci_hcd rc_core drm libata usbcore wmi video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr
[ 8996.385911] Supported: No, Unsupported modules are loaded

I don’t ever remember seeing these messages in the past. Are they normal?

Thanks in advance

@dekernel2 You have updated to the retracted kernel I suspect…

See Lots of kernel warnings after kernel update

Thanks! Apparently the search I did before posting wasn’t quit effective.
As a side note, I went years and years with no issues, but in the last 6 months, I have had two (2) different kernels cause me issues. Wondering what has changed, but there is no distro I would rather use so not complaining.

@dekernel2 Yes, there have been a couple, I suspect the change with the base system and moving to SUSE ownership has created some issues, it happens, but does get resolved in a timely fashion…