Bugzilla – Bug 1212139
[amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
Last modified: 2024-01-18 20:30:04 UTC
Created attachment 867453 [details] dmesg-mohamed-mehany-steps-reproduce Linux steamdeck.lan 6.4.0-rc5-1.g2cab33e-default #1 SMP PREEMPT_DYNAMIC Sun Jun 4 20:15:10 UTC 2023 (2cab33e) x86_64 x86_64 x86_64 GNU/Linux Step to reproduce. ``` sudo -i echo "low" > /sys/class/drm/card1/device/power_dpm_force_performance_level exit sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover ``` LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230605 Codename: n/a Information for package plasma5-mobile: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : plasma5-mobile Version : 5.27.5-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 2.3 MiB Installed : Yes Status : out-of-date (version 5.27.4-1.1 installed) Source package : plasma5-mobile-5.27.5-1.1.src Upstream URL : http://www.kde.org/ Summary : Plasma Mobile Description : Plasma shell and components targeted for phones. https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_1948249
Created attachment 867454 [details] dmesg-freezing-while-watching-videos Firefox and anglefish was opened.
I wonder if my bug is similar to this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1209294
(In reply to ted chang from comment #2) > I wonder if my bug is similar to this bug > > https://bugzilla.opensuse.org/show_bug.cgi?id=1209294 Yes, very likely. Let's wait for the upstream resolution.
(In reply to Takashi Iwai from comment #3) > > Yes, very likely. Let's wait for the upstream resolution. All power bugs are nasty to debug and fix. The fix might take years. I hope Valve becomes rope into it. They might have more leverage to ask for AMD to spend more engineering hours into it.
Apparently, my ina2xx controller is dead https://steamcommunity.com/app/1675200/discussions/1/3186864655209404156/?ctp=29 [ 7.430212] ina2xx i2c-PRP0001:02: supply vs not found, using dummy regulator [ 7.441099] ina2xx i2c-PRP0001:02: error configuring the device: -121 [ 7.458895] ina2xx i2c-PRP0001:03: supply vs not found, using dummy regulator [ 7.461193] ina2xx i2c-PRP0001:03: error configuring the device: -121 [ 7.471518] ina2xx i2c-PRP0001:04: supply vs not found, using dummy regulator [ 7.473991] ina2xx i2c-PRP0001:04: error configuring the device: -121 [ 7.484221] thermal LNXTHERM:00: registered as thermal_zone0
The controller issue is probably unrelated. I have to wait for upstream.
AMD employee reproduced the bug https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_2146527
I have the very same bug, but cannot reproduce easily. Note that you have VanGogh GPU (0x163f), but the freedesktop issue (and mine too) is about Rembrandt (0x1681). It might be the same bug. Or it might not. How easy is it for you to reproduce? When a fix is available, can you test on demand?
(In reply to Jiri Slaby from comment #8) > I have the very same bug, but cannot reproduce easily. > > Note that you have VanGogh GPU (0x163f), but the freedesktop issue (and mine > too) is about Rembrandt (0x1681). It might be the same bug. Or it might not. > > How easy is it for you to reproduce? When a fix is available, can you test > on demand? I might be look at my dmesg logs wrong. It seems like I didn't reproduce it. I believe I did hit this bug before without mohamed directions but I only hit it like 3 times the 2 years I had this device. Super hard bug to reproduce.
(In reply to Jiri Slaby from comment #8) > I have the very same bug, but cannot reproduce easily. > > Note that you have VanGogh GPU (0x163f), but the freedesktop issue (and mine > too) is about Rembrandt (0x1681). It might be the same bug. Or it might not. > > How easy is it for you to reproduce? When a fix is available, can you test > on demand? Nevermind, I did hit this sdma0 bug. I didn't reproduce mehany's steps. It seems like this bug requires video decode to trigger. Super hard bug to reproduce.
Steam deck has Rembrandt GPU. https://en.wikipedia.org/wiki/RDNA_2
Movement on the bug https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=3aae4ef4d799fb3d0381157640fdb251008cf0ae drm/amdgpu/sdma5.2: add begin/end_use ring callbacks commit ab4750332dbe535243def5dcebc24ca00c1f98ac upstream. Add begin/end_use ring callbacks to disallow GFXOFF when SDMA work is submitted and allow it again afterward. This should avoid corner cases where GFXOFF is erroneously entered when SDMA is still active. For now just allow/disallow GFXOFF in the begin and end helpers until we root cause the issue. This should not impact power as SDMA usage is pretty minimal and GFXOSS should not be active when SDMA is active anyway, this just makes it explicit. v2: move everything into sdma5.2 code. No reason for this to be generic at this point. v3: Add comments in new code Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2220 Reviewed-by: Mario Limonciello <mario.limonciello@amd.com> (v1) Tested-by: Mario Limonciello <mario.limonciello@amd.com> (v1) Reviewed-by: Christian König <christian.koenig@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org # 5.15+ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> I might close this bug since I cannot reproduce this bug myself.
The commit is a workaround. Not a fix.
Created attachment 871543 [details] dmesg-sdma0 6.6.6-1-default sdma0 recovery timeout worked. ypper info kernel-default Loading repository data... Reading installed packages... Information for package kernel-default: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : kernel-default Version : 6.6.6-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 238.1 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.6.6-1.1.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2023-12-11 09:46:39 +0000 GIT Revision: a946a9f9d865a849717a570675413f097b229184 GIT Branch: stable 13921.428572] br-489b770a8295: port 5(vethd49d2d6) entered disabled state [13921.430516] vethd49d2d6 (unregistering): left allmulticast mode [13921.430530] vethd49d2d6 (unregistering): left promiscuous mode [13921.430555] br-489b770a8295: port 5(vethd49d2d6) entered disabled state [13971.699892] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=118486, emitted seq=118489 [13971.700466] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [13971.700981] amdgpu 0000:04:00.0: amdgpu: GPU reset begin! [13971.873638] amdgpu 0000:04:00.0: amdgpu: MODE2 reset [13971.883852] amdgpu 0000:04:00.0: amdgpu: GPU reset succeeded, trying to resume [13971.884507] [drm] PCIE GART of 1024M enabled (table at 0x000000F47FC00000). [13971.884678] [drm] PSP is resuming... [13971.907096] [drm] reserve 0xa00000 from 0xf47e000000 for PSP TMR [13972.572603] amdgpu 0000:04:00.0: amdgpu: SMU is resuming... [13972.573350] amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully! [13972.583240] [drm] DMUB hardware initialized: version=0x0300000A [13972.662705] [drm] Failed to add display topology, DTM TA is not initialized. [13972.810113] [drm] Failed to add display topology, DTM TA is not initialized. [13972.830527] [drm] kiq ring mec 2 pipe 1 q 0 [13972.832594] [drm] VCN decode and encode initialized successfully(under DPG Mode). [13972.833161] [drm] JPEG decode initialized successfully. [13972.833168] amdgpu 0000:04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [13972.833192] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [13972.833197] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [13972.833200] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [13972.833204] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [13972.833208] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [13972.833211] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [13972.833215] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [13972.833219] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [13972.833223] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0 [13972.833227] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [13972.833231] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8 [13972.833235] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8 [13972.833238] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8 [13972.833241] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8 [13972.836573] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow start [13972.836579] amdgpu 0000:04:00.0: amdgpu: recover vram bo from shadow done [13972.836616] amdgpu 0000:04:00.0: amdgpu: GPU reset(1) succeeded! [13972.836941] [drm] Skip scheduling IBs! [13972.837328] [drm] Skip scheduling IBs! [13972.837479] [drm] Skip scheduling IBs! [13972.844896] [drm] Skip scheduling IBs!
The timeout blinked both the internal and external screen. This timeout happened while watching youtube videos.
I do not think the 6.6 kernel is patched.
Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Valve Version: F7A0120 Release Date: 12/01/2023
Created attachment 871544 [details] journalctl-sdma0-timeout-recovery Information for package kernel-firmware-amdgpu: ----------------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : kernel-firmware-amdgpu Version : 20231214-1.1 Arch : noarch Vendor : openSUSE Installed Size : 22.4 MiB Installed : Yes (automatically) Status : up-to-date Source package : kernel-firmware-20231214-1.1.src Upstream URL : https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for AMDGPU graphics driver Description : This package contains compressed kernel firmware files for AMDGPU graphics driver.
Created attachment 871680 [details] jounrnalctl -b -1 - 2024-01-24 Jan 07 08:00:58 steamdeck.lan avahi-daemon[1079]: Registering new address record for 2603:8001:6e02:11dc:29de:aa3c:f44c:c193 on wlo1.*. Jan 07 08:00:59 steamdeck.lan kernel: [drm] Failed to add display topology, DTM TA is not initialized. Jan 07 08:00:59 steamdeck.lan kernel: amdgpu 0000:04:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x0000001E SMN_C2PMSG_82:0x00000000 Jan 07 08:00:59 steamdeck.lan kernel: amdgpu 0000:04:00.0: amdgpu: Failed to disable gfxoff! Jan 07 08:01:00 steamdeck.lan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=9158, emitted seq=9158 Jan 07 08:01:00 steamdeck.lan kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 Jan 07 08:01:00 steamdeck.lan kernel: ------------[ cut here ]------------ Jan 07 08:01:00 steamdeck.lan kernel: WARNING: CPU: 6 PID: 22561 at include/linux/dma-fence.h:580 amdgpu_job_timedout+0x226/0x240 [amdgpu] Jan 07 08:01:00 steamdeck.lan kernel: Modules linked in: binfmt_misc uinput rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device ccm xt_nat xt_tcpudp veth uas usb_storag> Jan 07 08:01:00 steamdeck.lan kernel: snd_pci_acp6x snd_hda_intel mac80211 snd_soc_wm_adsp snd_pci_acp5x snd_intel_dspcfg kvm libarc4 cs_dsp snd_intel_sdw_acpi snd_soc_nau> Jan 07 08:01:00 steamdeck.lan kernel: video crypto_simd cryptd usbcore wdat_wdt ccp mmc_core rc_core t10_pi sp5100_tco i2c_hid_acpi wmi battery i2c_hid serio_raw btrfs bla> Jan 07 08:01:00 steamdeck.lan kernel: CPU: 6 PID: 22561 Comm: kworker/u32:64 Tainted: G W 6.6.9-1-default #1 openSUSE Tumbleweed d1362128d661d49af1fa81074e6> Jan 07 08:01:00 steamdeck.lan kernel: Hardware name: Valve Jupiter/Jupiter, BIOS F7A0120 12/01/2023 Jan 07 08:01:00 steamdeck.lan kernel: Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched] Jan 07 08:01:00 steamdeck.lan kernel: RIP: 0010:amdgpu_job_timedout+0x226/0x240 [amdgpu] Jan 07 08:01:00 steamdeck.lan kernel: Code: 08 19 3b c1 48 8b 50 18 e8 47 90 34 e7 b8 02 00 00 00 e9 5c ff ff ff 89 c6 48 c7 c7 a1 a4 40 c1 e8 4f ef ad e7 e9 33 ff ff ff <0> Jan 07 08:01:00 steamdeck.lan kernel: RSP: 0018:ffffc900023f7da0 EFLAGS: 00010202 Jan 07 08:01:00 steamdeck.lan kernel: RAX: ffff8883d986ecc0 RBX: ffff88829aefc800 RCX: 0000000000000027 Jan 07 08:01:00 steamdeck.lan kernel: RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff8883fed274c0 Jan 07 08:01:00 steamdeck.lan kernel: RBP: ffffc900023f7e28 R08: 0000000000000000 R09: ffffc900023f7be8 Jan 07 08:01:00 steamdeck.lan kernel: R10: 0000000000000003 R11: ffff8883fe9fffe8 R12: ffff888109128608 Jan 07 08:01:00 steamdeck.lan kernel: R13: ffff888109100000 R14: ffff8881394efc05 R15: ffff88829aefc800 Jan 07 08:01:00 steamdeck.lan kernel: FS: 0000000000000000(0000) GS:ffff8883fed00000(0000) knlGS:0000000000000000 Jan 07 08:01:00 steamdeck.lan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 07 08:01:00 steamdeck.lan kernel: CR2: 000055dcf9364838 CR3: 00000003f6c36000 CR4: 0000000000350ee0 Jan 07 08:01:00 steamdeck.lan kernel: Call Trace: Jan 07 08:01:00 steamdeck.lan kernel: <TASK> Jan 07 08:01:00 steamdeck.lan kernel: ? amdgpu_job_timedout+0x226/0x240 [amdgpu 75900756fd35384fd369346969bd6f9295095a1f] Jan 07 08:01:00 steamdeck.lan kernel: ? __warn+0x81/0x130 Jan 07 08:01:00 steamdeck.lan kernel: ? amdgpu_job_timedout+0x226/0x240 [amdgpu 75900756fd35384fd369346969bd6f9295095a1f] Jan 07 08:01:00 steamdeck.lan kernel: ? report_bug+0x171/0x1a0 Jan 07 08:01:00 steamdeck.lan kernel: ? handle_bug+0x3c/0x80 Jan 07 08:01:00 steamdeck.lan kernel: ? exc_invalid_op+0x17/0x70 lines 4862-4899 Jan 07 08:01:00 steamdeck.lan kernel: ? asm_exc_invalid_op+0x1a/0x20 Jan 07 08:01:00 steamdeck.lan kernel: ? amdgpu_job_timedout+0x226/0x240 [amdgpu 75900756fd35384fd369346969bd6f9295095a1f] Jan 07 08:01:00 steamdeck.lan kernel: ? srso_return_thunk+0x5/0x10 Jan 07 08:01:00 steamdeck.lan kernel: ? ttwu_queue_wakelist+0xef/0x110 Jan 07 08:01:00 steamdeck.lan kernel: drm_sched_job_timedout+0x6a/0x100 [gpu_sched 9b74bcf7223bc3f77eb4fbe315bcbf25bf150620] Jan 07 08:01:00 steamdeck.lan kernel: process_one_work+0x168/0x330 Jan 07 08:01:00 steamdeck.lan kernel: worker_thread+0x2f5/0x410 Jan 07 08:01:00 steamdeck.lan kernel: ? __pfx_worker_thread+0x10/0x10 Jan 07 08:01:00 steamdeck.lan kernel: kthread+0xe8/0x120 Jan 07 08:01:00 steamdeck.lan kernel: ? __pfx_kthread+0x10/0x10 Jan 07 08:01:00 steamdeck.lan kernel: ret_from_fork+0x34/0x50 Jan 07 08:01:00 steamdeck.lan kernel: ? __pfx_kthread+0x10/0x10 Jan 07 08:01:00 steamdeck.lan kernel: ret_from_fork_asm+0x1b/0x30 Jan 07 08:01:00 steamdeck.lan kernel: </TASK> Jan 07 08:01:00 steamdeck.lan kernel: ---[ end trace 0000000000000000 ]--- Jan 07 08:01:00 steamdeck.lan kernel: amdgpu 0000:04:00.0: amdgpu: GPU reset begin! Jan 07 08:01:00 steamdeck.lan systemd[1]: run-docker-runtime\x2drunc-moby-96c775eaf70ad3cefde4f92ce1c9df68b817e811dcb169a8f7b19740e64be7da-runc.MAp0vZ.mount: Deactivated su> Jan 07 08:01:00 steamdeck.lan systemd[3364]: org.gnome.Shell@wayland.service: State 'stop-sigterm' timed out. Killing. Jan 07 08:01:00 steamdeck.lan systemd[3364]: org.gnome.Shell@wayland.service: Killing process 4468 (Xwayland) with signal SIGKILL. Jan 07 08:01:00 steamdeck.lan systemd[3364]: org.gnome.Shell@wayland.service: Killing process 4778 (mutter-x11-fram) with signal SIGKILL. Jan 07 08:01:00 steamdeck.lan systemd[3364]: org.gnome.Shell@wayland.service: Killing process 4810 (mutter-x11:cs0) with signal SIGKILL. zypper info kernel-default Loading repository data... Reading installed packages... Information for package kernel-default: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : kernel-default Version : 6.6.9-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 238.1 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.6.9-1.1.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2024-01-02 07:19:30 +0000 GIT Revision: 61d1d446f15b070e1465e03edfec1088ebe48485 GIT Branch: stable Repository : openSUSE-Tumbleweed-Oss Name : kernel-firmware-amdgpu Version : 20240102-1.1 Arch : noarch Vendor : openSUSE Installed Size : 22.4 MiB Installed : Yes (automatically) Status : up-to-date Source package : kernel-firmware-20240102-1.1.src Upstream URL : https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for AMDGPU graphics driver Description : This package contains compressed kernel firmware files for AMDGPU graphics driver. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: Valve Version: F7A0120 Release Date: 12/01/2023 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 16 MB Characteristics: The bug is probably isn't fixed
SUSE-SU-2024:0115-1: An update that solves 10 vulnerabilities, contains three features and has 40 security fixes can now be installed. Category: security (important) Bug References: 1179610, 1183045, 1211162, 1211226, 1212139, 1212584, 1214117, 1214747, 1214823, 1215237, 1215696, 1215885, 1215952, 1216032, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217822, 1217927, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218092, 1218139, 1218184, 1218229, 1218234, 1218253, 1218258, 1218335, 1218357, 1218397, 1218447, 1218461, 1218515, 1218559, 1218569, 1218643 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7167 Sources used: openSUSE Leap 15.5 (src): kernel-source-rt-5.14.21-150500.13.30.1, kernel-livepatch-SLE15-SP5-RT_Update_9-1-150500.11.3.1, kernel-syms-rt-5.14.21-150500.13.30.1 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5-RT_Update_9-1-150500.11.3.1 SUSE Real Time Module 15-SP5 (src): kernel-source-rt-5.14.21-150500.13.30.1, kernel-syms-rt-5.14.21-150500.13.30.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:0141-1: An update that solves 10 vulnerabilities, contains three features and has 41 security fixes can now be installed. Category: security (important) Bug References: 1108281, 1179610, 1183045, 1211162, 1211226, 1212139, 1212584, 1214117, 1214747, 1214823, 1215237, 1215696, 1215885, 1215952, 1216032, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217822, 1217927, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218092, 1218139, 1218184, 1218229, 1218234, 1218253, 1218258, 1218335, 1218357, 1218397, 1218447, 1218461, 1218515, 1218559, 1218569, 1218643 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7167 Sources used: openSUSE Leap 15.5 (src): kernel-syms-azure-5.14.21-150500.33.29.1, kernel-source-azure-5.14.21-150500.33.29.1 Public Cloud Module 15-SP5 (src): kernel-syms-azure-5.14.21-150500.33.29.1, kernel-source-azure-5.14.21-150500.33.29.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.
SUSE-SU-2024:0160-1: An update that solves 10 vulnerabilities, contains three features and has 42 security fixes can now be installed. Category: security (important) Bug References: 1179610, 1183045, 1211162, 1211226, 1212139, 1212584, 1214117, 1214158, 1214747, 1214823, 1215237, 1215696, 1215885, 1215952, 1216032, 1216057, 1216559, 1216776, 1217036, 1217217, 1217250, 1217602, 1217692, 1217790, 1217801, 1217822, 1217927, 1217933, 1217938, 1217946, 1217947, 1217980, 1217981, 1217982, 1218056, 1218092, 1218139, 1218184, 1218229, 1218234, 1218253, 1218258, 1218335, 1218357, 1218397, 1218447, 1218461, 1218515, 1218559, 1218569, 1218643, 1218738 CVE References: CVE-2020-26555, CVE-2023-51779, CVE-2023-6121, CVE-2023-6531, CVE-2023-6546, CVE-2023-6606, CVE-2023-6610, CVE-2023-6622, CVE-2023-6931, CVE-2023-6932 Jira References: PED-3459, PED-5021, PED-7167 Sources used: openSUSE Leap 15.5 (src): kernel-obs-build-5.14.21-150500.55.44.1, kernel-livepatch-SLE15-SP5_Update_9-1-150500.11.5.1, kernel-syms-5.14.21-150500.55.44.1, kernel-source-5.14.21-150500.55.44.1, kernel-default-base-5.14.21-150500.55.44.1.150500.6.19.2, kernel-obs-qa-5.14.21-150500.55.44.1 SUSE Linux Enterprise Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.44.1.150500.6.19.2 Basesystem Module 15-SP5 (src): kernel-default-base-5.14.21-150500.55.44.1.150500.6.19.2, kernel-source-5.14.21-150500.55.44.1 Development Tools Module 15-SP5 (src): kernel-source-5.14.21-150500.55.44.1, kernel-obs-build-5.14.21-150500.55.44.1, kernel-syms-5.14.21-150500.55.44.1 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5_Update_9-1-150500.11.5.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.