January 2025 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1236318] Many many [drm] scheduler comp related errors in dmesg and journal after wakeup
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236318 https://bugzilla.suse.com/show_bug.cgi?id=1236318#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Or a different one: https://gitlab.freedesktop.org/drm/amd/-/issues/3746 The relevant upstream discussion on ML: https://lore.kernel.org/lkml/20250107140240.325899-1-philipp.reisner@linbit… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1236318] Many many [drm] scheduler comp related errors in dmesg and journal after wakeup
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236318 https://bugzilla.suse.com/show_bug.cgi?id=1236318#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- There have been already similar reports found in the upstream tracker and ML. Better to report / join to the upstream, e.g. https://gitlab.freedesktop.org/drm/amd/-/issues/3911 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1236318] New: Many many [drm] scheduler comp related errors in dmesg and journal after wakeup
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236318 Bug ID: 1236318 Summary: Many many [drm] scheduler comp related errors in dmesg and journal after wakeup Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I am using Kernel:stable standard 6.13.0-1.g1513344-default with Tumbleweed. After I suspend and sometime later wakeup the machine I find that the journal and dmesg are full of [drm] scheduler comp notifications. I have added dmesg and current journal output. Firefox is still affected by this as mentioned initially in Bug 1235540 by severely slowing down when saving file (whiting out). Also experienced additional strange behavior in Skype and Tor after wakeup: number 6 repeated like keyboard key is held down i.e. 66666666666666666666666666666 when switching to workspace after wakeup and ticking on application. Or can be v repeated many many times vvvvvvvvvvv , when ticking on application (these characters show in input box fields). Experience is when Skype and or Tor are open in separate desktop workspace number 4 of 4. free -m total used free shared buff/cache available Mem: 15956 8302 1270 395 7111 7654 Swap: 15887 769 15118 -Regards -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c18 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Let's close. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235540] New: Re: dmesg error snippet:< workqueue: Failed to create worker thread:
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235540 Bug ID: 1235540 Summary: Re: dmesg error snippet:< workqueue: Failed to create worker thread: Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879491 --> https://bugzilla.suse.com/attachment.cgi?id=879491&action=edit 1-7-25 journal ENOMEM entry Hi, openSUSE Tumbleweed 20250106, KDE here. I noticed the following 'dmesg' output: [49125.219751] [ T141229] workqueue: Failed to create a worker thread: -ENOMEM [49128.254152] [ T2] SLUB: Unable to allocate memory on CPU 1 (of node 0) on node 0, gfp=0xcc0(GFP_KERNEL) [49128.254157] [ T2] cache: task_struct, object size: 10752, buffer size: 10752, default order: 3, min order: 2 [49128.254159] [ T2] node 0: slabs: 976, objs: 2920, free: 0 I had 3 different Firefox instances open in two different workspaces. I was using one Firefox instance to browse pixabay.com and when downloading a few wallpapers the display/s would freeze and turn white in color (also machine would freeze). The machine here has 16GiB of memory. I have attached the journal output to this message. The machine has been put together about one month ago. I have not had this occur before with this machine. I have completed 4 passes with memtest after incident. Regards -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1235540] workqueue: Failed to create a worker thread: -ENOMEM
by bugzilla_noreply＠suse.com 23 Jan '25

23 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235540 https://bugzilla.suse.com/show_bug.cgi?id=1235540#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Yes, it sounds like a different issue. But, as TW is already moving to 6.13, please verify the behavior with the latest 6.13.x kernel in OBS Kernel:stable repo, before opening another issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235499] Monitor freeze on 6.12: amdgpu [drm] *ERROR* [CRTC:83:crtc-1] flip_done timed out
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235499 https://bugzilla.suse.com/show_bug.cgi?id=1235499#c5 Hunter Wardlaw <wardlawhunter(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Hunter Wardlaw <wardlawhunter(a)gmail.com> --- I'm marking this as resolved, but I will let you know if it comes up again. For your awareness the following commit may also be related. commit c2eaa73bd542b0168a0519e4a1c6e94bc121ec3d Author: Melissa Wen <mwen(a)igalia.com> Date: Tue Dec 17 17:45:05 2024 -0300 drm/amd/display: fix divide error in DM plane scale calcs commit 5225fd2a26211d012533acf98a6ad3f983885817 upstream. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235938] New: ZSWAP config cleanup
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235938 Bug ID: 1235938 Summary: ZSWAP config cleanup Classification: SUSE Linux Framework One Product: SUSE Linux Enterprise Server 16.0 Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: jslaby(a)suse.com CC: kernel-bugs(a)opensuse.org, mgorman(a)suse.com, mhocko(a)suse.cz, mkubecek(a)suse.com, qa-bugs(a)suse.de, vbabka(a)suse.com Depends on: 1231416 Target Milestone: --- Group: novellonly Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1231416 +++ Following: commit 13a488ad6c85976074f78f80a06414914890703c Author: Yosry Ahmed <yosryahmed(a)google.com> Date: Mon Oct 7 19:21:16 2024 +0000 mm: z3fold: deprecate CONFIG_Z3FOLD The z3fold compressed pages allocator is rarely used, most users use zsmalloc. The only disadvantage of zsmalloc in comparison is the dependency on MMU, and zbud is a more common option for !MMU as it was the default zswap allocator for a long time. Historically, zsmalloc had worse latency than zbud and z3fold but offered better memory savings. This is no longer the case as shown by a simple recent analysis [1]. That analysis showed that z3fold does not have any advantage over zsmalloc or zbud considering both performance and memory usage. In a kernel build test on tmpfs in a limited cgroup, z3fold took 3% more time and used 1.8% more memory. The latency of zswap_load() was 7% higher, and that of zswap_store() was 10% higher. Zsmalloc is better in all metrics. Moreover, z3fold apparently has latent bugs, which was made noticeable by a recent soft lockup bug report with z3fold [2]. Switching to zsmalloc not only fixed the problem, but also reduced the swap usage from 6~8G to 1~2G. Other users have also reported being bitten by mistakenly enabling z3fold. Other than hurting users, z3fold is repeatedly causing wasted engineering effort. Apart from investigating the above bug, it came up in multiple development discussions (e.g. [3]) as something we need to handle, when there aren't any legit users (at least not intentionally). The natural course of action is to deprecate z3fold, and remove in a few cycles if no objections are raised from active users. Next on the list should be zbud, as it offers marginal latency gains at the cost of huge memory waste when compared to zsmalloc. That one will need to wait until zsmalloc does not depend on MMU. We should likely: * set CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD_DEPRECATED=n * set CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC=y and CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD=n We should likely do the same in SUSE-2025. This was switched in master: commit 7cce8ae7a3a847390718c88c87f264351e4f473e Author: Jiri Slaby <jslaby(a)suse.cz> Date: Wed Oct 9 12:52:47 2024 +0200 Update ZSWAP config files (bsc#1231416) * Z3FOLD is deprecated. * ZSMALLOC should be the default. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1235499] New: Monitor freeze on 6.12: amdgpu [drm] *ERROR* [CRTC:83:crtc-1] flip_done timed out
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235499 Bug ID: 1235499 Summary: Monitor freeze on 6.12: amdgpu [drm] *ERROR* [CRTC:83:crtc-1] flip_done timed out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: wardlawhunter(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879464 --> https://bugzilla.suse.com/attachment.cgi?id=879464&action=edit dmesg output My monitor has been intermittently freezing since updating to 6.12.8 (20250106) from 6.11.8 (20241218). I see the following from dmesg after a freeze. [ 3692.909069] [ T23491] amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:83:crtc-1] flip_done timed out [ 3716.799074] [ T2890] amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out [ 3716.799082] [ T2890] amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:83:crtc-1] commit wait timed out [ 3726.825819] [ T2890] amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out [ 3726.825826] [ T2890] amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:80:plane-7] commit wait timed out Full output is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1235536] Flickering screen on TUF Gaming A16 FA617NSR. Functioning workaround.
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235536 https://bugzilla.suse.com/show_bug.cgi?id=1235536#c5 --- Comment #5 from JuPing Chan <email(a)chanjp.me> --- Thanks for following up! I haven't filed the bug with them yet. Been looking at a few related reports to see if something similar has been reported to make sure there are no duplicates. Will update with the link here whether it's related, or a new one I will file. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215523] kernel 5.14.21.150400.24.84.1 amdgpu critical error
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1215523 https://bugzilla.suse.com/show_bug.cgi?id=1215523#c39 --- Comment #39 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0201-1: An update that solves 77 vulnerabilities and has 31 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250201-1 Category: security (important) Bug References: 1170891, 1173139, 1185010, 1190358, 1190428, 1203332, 1205521, 1209288, 1209798, 1211593, 1211595, 1214635, 1215304, 1215523, 1216813, 1216909, 1219608, 1222878, 1223044, 1225758, 1225820, 1226694, 1228190, 1229809, 1230422, 1230697, 1231388, 1231453, 1231854, 1232045, 1232157, 1232166, 1232419, 1232436, 1232472, 1232823, 1233038, 1233050, 1233070, 1233096, 1233127, 1233200, 1233239, 1233324, 1233467, 1233468, 1233469, 1233485, 1233547, 1233550, 1233558, 1233564, 1233568, 1233637, 1233642, 1233701, 1233769, 1233837, 1234072, 1234073, 1234075, 1234076, 1234077, 1234087, 1234120, 1234156, 1234219, 1234220, 1234240, 1234241, 1234281, 1234282, 1234294, 1234338, 1234357, 1234437, 1234464, 1234605, 1234639, 1234650, 1234727, 1234811, 1234827, 1234834, 1234843, 1234846, 1234853, 1234856, 1234891, 1234912, 1234920, 1234921, 1234960, 1234963, 1234971, 1234973, 1235004, 1235035, 1235037, 1235039, 1235054, 1235056, 1235061, 1235073, 1235220, 1235224, 1235246, 1235507 CVE References: CVE-2021-47202, CVE-2022-36280, CVE-2022-48742, CVE-2022-49033, CVE-2022-49035, CVE-2023-1382, CVE-2023-33951, CVE-2023-33952, CVE-2023-52920, CVE-2024-24860, CVE-2024-26886, CVE-2024-26924, CVE-2024-36915, CVE-2024-42232, CVE-2024-44934, CVE-2024-47666, CVE-2024-47678, CVE-2024-49944, CVE-2024-49952, CVE-2024-50018, CVE-2024-50143, CVE-2024-50154, CVE-2024-50166, CVE-2024-50181, CVE-2024-50202, CVE-2024-50211, CVE-2024-50256, CVE-2024-50262, CVE-2024-50278, CVE-2024-50279, CVE-2024-50280, CVE-2024-50296, CVE-2024-53051, CVE-2024-53055, CVE-2024-53056, CVE-2024-53064, CVE-2024-53072, CVE-2024-53090, CVE-2024-53095, CVE-2024-53101, CVE-2024-53113, CVE-2024-53114, CVE-2024-53119, CVE-2024-53120, CVE-2024-53122, CVE-2024-53125, CVE-2024-53130, CVE-2024-53131, CVE-2024-53142, CVE-2024-53146, CVE-2024-53150, CVE-2024-53156, CVE-2024-53157, CVE-2024-53158, CVE-2024-53161, CVE-2024-53162, CVE-2024-53173, CVE-2024-53179, CVE-2024-53206, CVE-2024-53210, CVE-2024-53213, CVE-2024-53214, CVE-2024-53239, CVE-2024-53240, CVE-2024-53241, CVE-2024-56539, CVE-2024-56548, CVE-2024-56549, CVE-2024-56570, CVE-2024-56571, CVE-2024-56575, CVE-2024-56598, CVE-2024-56604, CVE-2024-56605, CVE-2024-56619, CVE-2024-56755, CVE-2024-8805 Maintenance Incident: [SUSE:Maintenance:36972](https://smelt.suse.de/incident/36972/) Sources used: openSUSE Leap 15.5 (src): kernel-source-5.14.21-150500.55.91.1, kernel-livepatch-SLE15-SP5_Update_22-1-150500.11.3.1, kernel-syms-5.14.21-150500.55.91.1, kernel-obs-qa-5.14.21-150500.55.91.1, kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1, kernel-obs-build-5.14.21-150500.55.91.1 SUSE Linux Enterprise Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5_Update_22-1-150500.11.3.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP5 (src): kernel-syms-5.14.21-150500.55.91.1, kernel-source-5.14.21-150500.55.91.1, kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1, kernel-obs-build-5.14.21-150500.55.91.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP5 (src): kernel-syms-5.14.21-150500.55.91.1, kernel-source-5.14.21-150500.55.91.1, kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1, kernel-obs-build-5.14.21-150500.55.91.1 SUSE Linux Enterprise Server 15 SP5 LTSS (src): kernel-syms-5.14.21-150500.55.91.1, kernel-source-5.14.21-150500.55.91.1, kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1, kernel-obs-build-5.14.21-150500.55.91.1 SUSE Linux Enterprise Server for SAP Applications 15 SP5 (src): kernel-syms-5.14.21-150500.55.91.1, kernel-source-5.14.21-150500.55.91.1, kernel-default-base-5.14.21-150500.55.91.1.150500.6.41.1, kernel-obs-build-5.14.21-150500.55.91.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. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235536] Flickering screen on TUF Gaming A16 FA617NSR. Functioning workaround.
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235536 https://bugzilla.suse.com/show_bug.cgi?id=1235536#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Let us know the URL if you already reported (or joined) on the upstream bug tracker. I'll add it here for tracking. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234055] Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c32 --- Comment #32 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Otrebor Igorig from comment #31) > Stumbled over this article on Phoronix today: > https://www.phoronix.com/news/Linux-6.14-Intel-UHBR-TB > > Since an early 6.12 kernel worked with the full displays (leap only has > 6.4.x so far), Note that Leap 15.6 is based on 6.4.x, but received tons of backports for DRM drivers. So it might be some of backports that caused a regression. You can check the older 6.4.x kernel from OBS home:tiwai:kernel:6.4 repo https://download.opensuse.org/repositories/home:/tiwai:/kernel:/6.4/backpor… for installing on a Leap system. The package version looks newer (6.4.12), but it's certainly "older" than Leap 15.6 kernels that dropped the minor version number. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234623] New: DPC: RP PIO log size 0 is invalid (quirk needs to be added)
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234623 Bug ID: 1234623 Summary: DPC: RP PIO log size 0 is invalid (quirk needs to be added) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bjorn.lie(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879176 --> https://bugzilla.suse.com/attachment.cgi?id=879176&action=edit dmesg Hi Kernel people, this bug is mainly a "cosmetic" one that causes a "blip" during boot with plymouth, it has no real impact, but would be nice to have it fix in any case (device id added to quirk list). Kernel 6.11.8-1-default -- ASUSTeK COMPUTER INC. Zenbook UX3402VA_UX3402VA (CPU 13th Gen Intel(R) Core(TM) i5-1340P Raptor Lake) des. 15 11:21:37 localhost kernel: pci 0000:00:07.0: Overriding RP PIO Log Size to 4 des. 15 11:21:37 localhost kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid Please see closed upstream bug https://bugzilla.kernel.org/show_bug.cgi?id=209943 Closing comment is that new bugs should be filed for "new devices". --- lspci -nn 0000:00:00.0 Host bridge [0600]: Intel Corporation Raptor Lake-P/U 4p+8e cores Host Bridge/DRAM Controller [8086:a707] 0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) 0000:00:04.0 Signal processing controller [1180]: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant [8086:a71d] 0000:00:06.0 System peripheral [0880]: Intel Corporation RST VMD Managed Controller [8086:09ab] 0000:00:07.0 PCI bridge [0604]: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #0 [8086:a76e] 0000:00:07.2 PCI bridge [0604]: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port #2 [8086:a72f] 0000:00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator module [8086:a74f] 0000:00:0a.0 Signal processing controller [1180]: Intel Corporation Raptor Lake Crashlog and Telemetry [8086:a77d] (rev 01) 0000:00:0d.0 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller [8086:a71e] 0000:00:0d.2 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #0 [8086:a73e] 0000:00:0d.3 USB controller [0c03]: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI #1 [8086:a76d] 0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation [8086:a77f] 0000:00:14.0 USB controller [0c03]: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller [8086:51ed] (rev 01) 0000:00:14.2 RAM memory [0500]: Intel Corporation Alder Lake PCH Shared SRAM [8086:51ef] (rev 01) 0000:00:14.3 Network controller [0280]: Intel Corporation Raptor Lake PCH CNVi WiFi [8086:51f1] (rev 01) 0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 [8086:51e8] (rev 01) 0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Alder Lake PCH Serial IO I2C Controller #1 [8086:51e9] (rev 01) 0000:00:16.0 Communication controller [0780]: Intel Corporation Alder Lake PCH HECI Controller [8086:51e0] (rev 01) 0000:00:1c.0 PCI bridge [0604]: Intel Corporation Alder Lake PCH-P PCI Express Root Port #9 [8086:51bf] (rev 01) 0000:00:1e.0 Communication controller [0780]: Intel Corporation Alder Lake PCH UART #0 [8086:51a8] (rev 01) 0000:00:1e.2 Serial bus controller [0c80]: Intel Corporation Alder Lake SPI Controller [8086:51aa] (rev 01) 0000:00:1f.0 ISA bridge [0601]: Intel Corporation Raptor Lake LPC/eSPI Controller [8086:519d] (rev 01) 0000:00:1f.3 Multimedia audio controller [0401]: Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca] (rev 01) 0000:00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake PCH-P SMBus Host Controller [8086:51a3] (rev 01) 0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-P PCH SPI Controller [8086:51a4] (rev 01) 0000:55:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 10000:e0:06.0 PCI bridge [0604]: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port [8086:a74d] 10000:e1:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller PM9B1 (DRAM-less) [144d:a80b] (rev 02) -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1236022] New: ppc64le: "Processor reported Machine Check Exception (MCE) (0x10, 1 << 4)" it looks it is caused by zram01.sh on BTRFS
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236022 Bug ID: 1236022 Summary: ppc64le: "Processor reported Machine Check Exception (MCE) (0x10, 1 << 4)" it looks it is caused by zram01.sh on BTRFS Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP test zram01.sh sporadically hits unexpected taint: Processor reported Machine Check Exception (MCE) (0x10, 1 << 4). It's probably since 6.12 (first visible on 6.12.6-1-default (fb072de), the oldest build we have is with 6.11.8-1-default (099023b)). aarch64 and x86_64 are ok, we don't test atm on s390x (I can run it if useful). Snipped of dmesg: [ 0.000000][ T0] Linux version 6.12.9-1-default (geeko@buildhost) (gcc (SUSE Linux) 14.2.1 20241007 [revision 4af44f2cf7d281f3e4f3957efce10e8b2ccb2ad3], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.43.1.20241209-4) #1 SMP Fri Jan 10 08:30:10 UTC 2025 (0ae2136) ... [ 198.256273][ T1520] OpenQA::run_ltp.pm: Starting zram01 [ 199.074476][ T2543] /dev/zero: Can't lookup blockdev [ 199.125560][ T2543] /dev/zero: Can't lookup blockdev [ 199.144217][ T2543] /dev/zero: Can't lookup blockdev [ 199.528242][ T2551] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [ 199.531386][ T2543] /dev/zero: Can't lookup blockdev [ 199.874481][ T2543] bcachefs (/dev/zero): error reading superblock: error opening /dev/zero: ENOTBLK [ 199.875846][ T2543] bcachefs: bch2_fs_get_tree() error: ENOTBLK [ 199.960585][ T2543] /dev/zero: Can't lookup blockdev [ 200.020982][ T2543] /dev/zero: Can't lookup blockdev [ 200.039955][ T2543] request_module fs-ntfs succeeded, but still no fs? [ 200.418124][ T2581] zram: Added device: zram0 [ 200.419882][ T2581] zram: Added device: zram1 [ 200.422638][ T2581] zram: Added device: zram2 [ 200.454453][ T2581] zram: Added device: zram3 [ 200.456062][ T2581] zram: Added device: zram4 [ 200.457613][ T2581] zram: Added device: zram5 [ 200.458901][ T2581] zram: Added device: zram6 [ 200.460117][ T2581] zram: Added device: zram7 [ 200.696881][ T2517] zram0: detected capacity change from 0 to 51200 [ 200.698566][ T2517] zram1: detected capacity change from 0 to 51200 [ 200.705148][ T2517] zram2: detected capacity change from 0 to 51200 [ 200.711367][ T2517] zram3: detected capacity change from 0 to 614400 [ 200.715642][ T2517] zram4: detected capacity change from 0 to 786432 [ 200.719433][ T2517] zram5: detected capacity change from 0 to 51200 [ 200.721672][ T2517] zram6: detected capacity change from 0 to 51200 [ 200.723078][ T2517] zram7: detected capacity change from 0 to 51200 [ 201.036604][ T2633] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 202.335274][ T2690] EXT4-fs (zram0): mounting ext2 file system using the ext4 subsystem [ 202.351263][ T2690] EXT4-fs (zram0): mounted filesystem be003b6b-a355-4a75-a160-df200328639e r/w without journal. Quota mode: none. [ 202.375224][ T2694] EXT4-fs (zram1): mounting ext3 file system using the ext4 subsystem [ 202.383945][ T2694] EXT4-fs (zram1): mounted filesystem 4db5cd42-a887-4d0d-852c-439ef6ef745e r/w with ordered data mode. Quota mode: none. [ 202.434658][ T2698] EXT4-fs (zram2): mounted filesystem ef1cbfb5-32e2-4e93-aaf2-83b17ce45223 r/w with ordered data mode. Quota mode: none. [ 202.486598][ T2702] XFS (zram3): Mounting V5 Filesystem ed23db17-b643-4e79-ab27-394405eed009 [ 202.534378][ T2702] XFS (zram3): Ending clean mount [ 202.558059][ T2712] BTRFS: device fsid 18f606a5-e7e9-4095-89e9-f3e0b3f6c68d devid 1 transid 8 /dev/zram4 (252:4) scanned by mount (2712) [ 202.582767][ T2712] BTRFS info (device zram4): first mount of filesystem 18f606a5-e7e9-4095-89e9-f3e0b3f6c68d [ 202.583382][ T2712] BTRFS info (device zram4): using crc32c (crc32c-vpmsum) checksum algorithm [ 202.583832][ T2712] BTRFS info (device zram4): forcing free space tree for sector size 4096 with page size 65536 [ 202.584717][ T2712] BTRFS info (device zram4): using free-space-tree [ 202.593083][ T2712] BTRFS warning (device zram4): read-write for sector size 4096 with page size 65536 is experimental [ 202.650690][ T2712] BTRFS info (device zram4): checking UUID tree [ 636.432925][ C0] Disabling lock debugging due to kernel taint [ 636.433452][ C0] MCE: CPU0: machine check (Severe) SLB Multihit DAR: 00000100015f0008 [Recovered] [ 636.433884][ C0] MCE: CPU0: PID: 232029 Comm: dd NIP: [00007fffbde16170] [ 636.434288][ C0] MCE: CPU0: Initiator CPU [ 636.434681][ C0] MCE: CPU0: Unknown [ 636.435064][ C0] SLB contents of cpu 0x0 [ 636.435441][ C0] 00 c000000008000000 400ea1b217000510 VALID [ 636.435838][ C0] 1T ESID= c00000 VSID= ea1b217 LLP:110 [ 636.436231][ C0] 02 c00c000008000000 40066bdea7000510 VALID [ 636.436626][ C0] 1T ESID= c00c00 VSID= 66bdea7 LLP:110 [ 636.437012][ C0] 03 c008000008000000 4009287a77000510 VALID [ 636.437402][ C0] 1T ESID= c00800 VSID= 9287a77 LLP:110 [ 636.437791][ C0] 04 c00a000008000000 4007ca2c8f000510 VALID [ 636.438179][ C0] 1T ESID= c00a00 VSID= 7ca2c8f LLP:110 [ 636.438572][ C0] 05 0000010008000000 4006bf889f000d90 VALID [ 636.438968][ C0] 1T ESID= 1 VSID= 6bf889f LLP:110 [ 636.439369][ C0] 06 00007f0008000000 4004e95373000d90 VALID [ 636.439775][ C0] 1T ESID= 7f VSID= 4e95373 LLP:110 [ 636.440187][ C0] 07 0000000118000000 000601014602fd90 VALID [ 636.440601][ C0] 256M ESID= 11 VSID= 601014602f LLP:110 [ 636.441020][ C0] 08 0000000138000000 00060119301e1d90 VALID [ 636.441439][ C0] 256M ESID= 13 VSID= 60119301e1 LLP:110 [ 636.441890][ C0] 09 c009ff0008000000 40070adbb6000510 VALID [ 636.442329][ C0] 1T ESID= c009ff VSID= 70adbb6 LLP:110 [ 636.442760][ C0] 10 0000010008000000 4006bf889f000d90 VALID [ 636.443193][ C0] 1T ESID= 1 VSID= 6bf889f LLP:110 [ 636.443631][ C0] SLB RR allocator index 1 [ 636.444071][ C0] SLB cache ptr value = 5 [ 636.444490][ C0] Valid SLB cache entries: [ 636.444916][ C0] 00 EA[0-35]= 1000 [ 636.445327][ C0] 01 EA[0-35]= 7f000 [ 636.445729][ C0] 02 EA[0-35]= 11 [ 636.446120][ C0] 03 EA[0-35]= 13 [ 636.446510][ C0] 04 EA[0-35]= 1000 [ 636.446884][ C0] Rest of SLB cache entries: [ 636.447257][ C0] 05 EA[0-35]= 13 [ 636.447610][ C0] 06 EA[0-35]= 13 [ 636.447949][ C0] 07 EA[0-35]= 10 [ 1439.368280][T671192] EXT4-fs (zram0): unmounting filesystem be003b6b-a355-4a75-a160-df200328639e. [ 1439.379916][T671193] EXT4-fs (zram1): unmounting filesystem 4db5cd42-a887-4d0d-852c-439ef6ef745e. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1236027] Latest kernel kernel-default-6.12.8-2.2.x86_64 does not boot.
by bugzilla_noreply＠suse.com 20 Jan '25

20 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236027 https://bugzilla.suse.com/show_bug.cgi?id=1236027#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED CC| |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- You can use the kernel in OBS Kernel:stable or just wait for a while until this kernel is included in TW release, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235826] Resolution 5120x1440 @240hz causes flickering and display corruption
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235826 https://bugzilla.suse.com/show_bug.cgi?id=1235826#c5 --- Comment #5 from Pontus Gårdmo <pontus0077(a)gmail.com> --- (In reply to Jiri Slaby from comment #4) > (In reply to Jiri Slaby from comment #3) > > So it's only an amdgpu issue for some devices, but the patch changes the > > behavior for all cards and drivers. This needs to be resolved first. > > There is a different patch to try: > https://lore.kernel.org/all/7cf3ceed-056a-4be0-804f-91f946db2b33@amd.com/ > > Could you try it from: > https://build.opensuse.org/project/monitor/home:jirislaby:stable-bsc1235826 > ? Still an issue -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1236027] Latest kernel kernel-default-6.12.8-2.2.x86_64 does not boot.
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236027 https://bugzilla.suse.com/show_bug.cgi?id=1236027#c2 --- Comment #2 from Pieter Terpstra <kesang.neljor(a)yahoo.com> --- Yes it does, thanks! Should kernel upgrades now go from this repository? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1236027] Latest kernel kernel-default-6.12.8-2.2.x86_64 does not boot.
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236027 https://bugzilla.suse.com/show_bug.cgi?id=1236027#c1 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com --- Comment #1 from Michal Suchanek <msuchanek(a)suse.com> --- Does the kernel from https://download.opensuse.org/repositories/Kernel:/stable/standard/ boot correctly? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1236027] New: Latest kernel does not boot
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1236027 Bug ID: 1236027 Summary: Latest kernel does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kesang.neljor(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Build Identifier: Latest kernel 6.12.8 does not load modules for /dev/sda and boot fails #rpm -qi kernel-default-6.12.8-2.2.x86_64 Name : kernel-default Version : 6.12.8 Release : 2.2 Architecture: x86_64 Install Date: Sun 12 Jan 2025 02:35:28 PM PST Group : System/Kernel Size : 264937624 License : GPL-2.0-only Signature : RSA/SHA512, Fri 10 Jan 2025 09:12:20 AM PST, Key ID 35a2f86e29b700a4 Source RPM : kernel-default-6.12.8-2.2.nosrc.rpm Build Date : Thu 02 Jan 2025 08:46:27 AM PST Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2025-01-06 06:45:37 +0000 GIT Revision: 90b0f5bec3c74e2fb0bbf3d5a7738de0305f169e GIT Branch: stable Distribution: openSUSE Tumbleweed System has 2 disks /dev/sda has a swap partition and a local partition # grep LOCAL /var/log/boot.log [ **] (2 of 2) A start job is running for /dev/disk/by-label/LOCAL (1min 30s / 1min 30s) [ TIME ] Timed out waiting for device /dev/disk/by-label/LOCAL Reproducible: Always Steps to Reproduce: 1. boot or reboot into kernel-default-6.12.8-2.2.x86_64 2. 3. Actual Results: Boot fails [ **] (2 of 2) A start job is running for /dev/disk/by-label/LOCAL (1min 30s / 1min 30s) [ TIME ] Timed out waiting for device /dev/disk/by-label/LOCAL Expected Results: full boot kernel-default-6.12.6-1.1.x86_64 gives no problem at all. Had exactly the same problem a few (2?) years ago also, did a bug report an a bugfix was provided. But maybe i reported that directly at kernel.org and not here. Cannot find that back. Please let me know if you have questions and thank you so much in advance. Peter -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1234454] Compiling external modules fails with "/usr/src/linux-6.13.0-rc2-1.gf92fc5d/include/config/auto.conf: No such file or directory"
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234454 https://bugzilla.suse.com/show_bug.cgi?id=1234454#c17 --- Comment #17 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0154-1: An update that solves 117 vulnerabilities, contains one feature and has 102 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250154-1 Category: security (important) Bug References: 1214954, 1216813, 1220773, 1224095, 1224726, 1225743, 1225758, 1225820, 1227445, 1228526, 1229809, 1230205, 1230413, 1230697, 1231854, 1231909, 1231963, 1232193, 1232198, 1232201, 1232418, 1232419, 1232420, 1232421, 1232436, 1233038, 1233070, 1233096, 1233200, 1233204, 1233239, 1233259, 1233260, 1233324, 1233328, 1233461, 1233467, 1233468, 1233469, 1233546, 1233558, 1233637, 1233642, 1233772, 1233837, 1234024, 1234069, 1234071, 1234073, 1234075, 1234076, 1234077, 1234079, 1234086, 1234139, 1234140, 1234141, 1234142, 1234143, 1234144, 1234145, 1234146, 1234147, 1234148, 1234149, 1234150, 1234153, 1234155, 1234156, 1234158, 1234159, 1234160, 1234161, 1234162, 1234163, 1234164, 1234165, 1234166, 1234167, 1234168, 1234169, 1234170, 1234171, 1234172, 1234173, 1234174, 1234175, 1234176, 1234177, 1234178, 1234179, 1234180, 1234181, 1234182, 1234183, 1234184, 1234185, 1234186, 1234187, 1234188, 1234189, 1234190, 1234191, 1234192, 1234193, 1234194, 1234195, 1234196, 1234197, 1234198, 1234199, 1234200, 1234201, 1234203, 1234204, 1234205, 1234207, 1234208, 1234209, 1234219, 1234220, 1234221, 1234237, 1234238, 1234239, 1234240, 1234241, 1234242, 1234243, 1234278, 1234279, 1234280, 1234281, 1234282, 1234294, 1234338, 1234357, 1234381, 1234454, 1234464, 1234605, 1234651, 1234652, 1234654, 1234655, 1234657, 1234658, 1234659, 1234668, 1234690, 1234725, 1234726, 1234810, 1234811, 1234826, 1234827, 1234829, 1234832, 1234834, 1234843, 1234846, 1234848, 1234853, 1234855, 1234856, 1234884, 1234889, 1234891, 1234899, 1234900, 1234905, 1234907, 1234909, 1234911, 1234912, 1234916, 1234918, 1234920, 1234921, 1234922, 1234929, 1234930, 1234937, 1234948, 1234950, 1234952, 1234960, 1234962, 1234963, 1234968, 1234969, 1234970, 1234971, 1234973, 1234974, 1234989, 1234999, 1235002, 1235003, 1235004, 1235007, 1235009, 1235016, 1235019, 1235033, 1235045, 1235056, 1235061, 1235075, 1235108, 1235128, 1235134, 1235138, 1235246, 1235406, 1235409, 1235416, 1235507, 1235550 CVE References: CVE-2024-26924, CVE-2024-27397, CVE-2024-35839, CVE-2024-36908, CVE-2024-36915, CVE-2024-39480, CVE-2024-41042, CVE-2024-44934, CVE-2024-44996, CVE-2024-47678, CVE-2024-49854, CVE-2024-49884, CVE-2024-49915, CVE-2024-50016, CVE-2024-50018, CVE-2024-50039, CVE-2024-50047, CVE-2024-50143, CVE-2024-50154, CVE-2024-50202, CVE-2024-50203, CVE-2024-50211, CVE-2024-50228, CVE-2024-50256, CVE-2024-50262, CVE-2024-50272, CVE-2024-50278, CVE-2024-50279, CVE-2024-50280, CVE-2024-53050, CVE-2024-53064, CVE-2024-53090, CVE-2024-53095, CVE-2024-53099, CVE-2024-53103, CVE-2024-53105, CVE-2024-53111, CVE-2024-53113, CVE-2024-53117, CVE-2024-53118, CVE-2024-53119, CVE-2024-53120, CVE-2024-53122, CVE-2024-53125, CVE-2024-53126, CVE-2024-53127, CVE-2024-53129, CVE-2024-53130, CVE-2024-53131, CVE-2024-53133, CVE-2024-53134, CVE-2024-53136, CVE-2024-53141, CVE-2024-53142, CVE-2024-53144, CVE-2024-53146, CVE-2024-53148, CVE-2024-53150, CVE-2024-53151, CVE-2024-53154, CVE-2024-53155, CVE-2024-53156, CVE-2024-53157, CVE-2024-53158, CVE-2024-53159, CVE-2024-53160, CVE-2024-53161, CVE-2024-53162, CVE-2024-53166, CVE-2024-53169, CVE-2024-53171, CVE-2024-53173, CVE-2024-53174, CVE-2024-53179, CVE-2024-53180, CVE-2024-53188, CVE-2024-53190, CVE-2024-53191, CVE-2024-53200, CVE-2024-53201, CVE-2024-53202, CVE-2024-53206, CVE-2024-53207, CVE-2024-53208, CVE-2024-53209, CVE-2024-53210, CVE-2024-53213, CVE-2024-53214, CVE-2024-53215, CVE-2024-53216, CVE-2024-53217, CVE-2024-53222, CVE-2024-53224, CVE-2024-53229, CVE-2024-53234, CVE-2024-53237, CVE-2024-53240, CVE-2024-53241, CVE-2024-56536, CVE-2024-56539, CVE-2024-56549, CVE-2024-56551, CVE-2024-56562, CVE-2024-56566, CVE-2024-56567, CVE-2024-56576, CVE-2024-56582, CVE-2024-56599, CVE-2024-56604, CVE-2024-56605, CVE-2024-56645, CVE-2024-56667, CVE-2024-56752, CVE-2024-56754, CVE-2024-56755, CVE-2024-56756, CVE-2024-8805 Jira References: PED-10467 Maintenance Incident: [SUSE:Maintenance:36947](https://smelt.suse.de/incident/36947/) Sources used: openSUSE Leap 15.6 (src): kernel-default-base-6.4.0-150600.23.33.1.150600.12.14.1, kernel-source-6.4.0-150600.23.33.1, kernel-livepatch-SLE15-SP6_Update_7-1-150600.13.3.1, kernel-syms-6.4.0-150600.23.33.1, kernel-obs-qa-6.4.0-150600.23.33.1, kernel-obs-build-6.4.0-150600.23.33.1 Basesystem Module 15-SP6 (src): kernel-default-base-6.4.0-150600.23.33.1.150600.12.14.1, kernel-source-6.4.0-150600.23.33.1 Development Tools Module 15-SP6 (src): kernel-syms-6.4.0-150600.23.33.1, kernel-source-6.4.0-150600.23.33.1, kernel-obs-build-6.4.0-150600.23.33.1 SUSE Linux Enterprise Live Patching 15-SP6 (src): kernel-livepatch-SLE15-SP6_Update_7-1-150600.13.3.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. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1234454] Compiling external modules fails with "/usr/src/linux-6.13.0-rc2-1.gf92fc5d/include/config/auto.conf: No such file or directory"
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1234454 https://bugzilla.suse.com/show_bug.cgi?id=1234454#c16 --- Comment #16 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2025:0153-1: An update that solves 114 vulnerabilities, contains one feature and has 102 security fixes can now be installed. URL: https://www.suse.com/support/update/announcement/2025/suse-su-20250153-1 Category: security (important) Bug References: 1214954, 1216813, 1220773, 1224095, 1224726, 1225743, 1225820, 1227445, 1228526, 1229809, 1230205, 1230697, 1231854, 1231909, 1231963, 1232193, 1232198, 1232201, 1232418, 1232419, 1232420, 1232421, 1232436, 1233038, 1233070, 1233096, 1233200, 1233204, 1233239, 1233259, 1233260, 1233324, 1233328, 1233461, 1233467, 1233469, 1233546, 1233558, 1233637, 1233642, 1233772, 1233837, 1234024, 1234069, 1234071, 1234073, 1234075, 1234076, 1234077, 1234079, 1234086, 1234139, 1234140, 1234141, 1234142, 1234143, 1234144, 1234145, 1234146, 1234147, 1234148, 1234149, 1234150, 1234153, 1234155, 1234156, 1234158, 1234159, 1234160, 1234161, 1234162, 1234163, 1234164, 1234165, 1234166, 1234167, 1234168, 1234169, 1234170, 1234171, 1234172, 1234173, 1234174, 1234175, 1234176, 1234177, 1234178, 1234179, 1234180, 1234181, 1234182, 1234183, 1234184, 1234185, 1234186, 1234187, 1234188, 1234189, 1234190, 1234191, 1234192, 1234193, 1234194, 1234195, 1234196, 1234197, 1234198, 1234199, 1234200, 1234201, 1234203, 1234204, 1234205, 1234207, 1234208, 1234209, 1234219, 1234220, 1234221, 1234237, 1234238, 1234239, 1234240, 1234241, 1234242, 1234243, 1234278, 1234279, 1234280, 1234281, 1234282, 1234294, 1234338, 1234357, 1234381, 1234454, 1234464, 1234605, 1234651, 1234652, 1234654, 1234655, 1234657, 1234658, 1234659, 1234668, 1234690, 1234725, 1234726, 1234810, 1234811, 1234826, 1234827, 1234829, 1234832, 1234834, 1234843, 1234846, 1234848, 1234853, 1234855, 1234856, 1234884, 1234889, 1234891, 1234899, 1234900, 1234905, 1234907, 1234909, 1234911, 1234912, 1234916, 1234918, 1234920, 1234921, 1234922, 1234929, 1234930, 1234937, 1234948, 1234950, 1234952, 1234960, 1234962, 1234963, 1234968, 1234969, 1234970, 1234971, 1234973, 1234974, 1234989, 1234999, 1235002, 1235003, 1235004, 1235007, 1235009, 1235016, 1235019, 1235033, 1235045, 1235056, 1235061, 1235075, 1235108, 1235128, 1235134, 1235138, 1235246, 1235406, 1235409, 1235416, 1235507, 1235550 CVE References: CVE-2024-26924, CVE-2024-27397, CVE-2024-35839, CVE-2024-36908, CVE-2024-39480, CVE-2024-41042, CVE-2024-44934, CVE-2024-44996, CVE-2024-47678, CVE-2024-49854, CVE-2024-49884, CVE-2024-49915, CVE-2024-50016, CVE-2024-50018, CVE-2024-50039, CVE-2024-50047, CVE-2024-50143, CVE-2024-50154, CVE-2024-50202, CVE-2024-50203, CVE-2024-50211, CVE-2024-50228, CVE-2024-50256, CVE-2024-50262, CVE-2024-50272, CVE-2024-50278, CVE-2024-50280, CVE-2024-53050, CVE-2024-53064, CVE-2024-53090, CVE-2024-53099, CVE-2024-53103, CVE-2024-53105, CVE-2024-53111, CVE-2024-53113, CVE-2024-53117, CVE-2024-53118, CVE-2024-53119, CVE-2024-53120, CVE-2024-53122, CVE-2024-53125, CVE-2024-53126, CVE-2024-53127, CVE-2024-53129, CVE-2024-53130, CVE-2024-53131, CVE-2024-53133, CVE-2024-53134, CVE-2024-53136, CVE-2024-53141, CVE-2024-53142, CVE-2024-53144, CVE-2024-53146, CVE-2024-53148, CVE-2024-53150, CVE-2024-53151, CVE-2024-53154, CVE-2024-53155, CVE-2024-53156, CVE-2024-53157, CVE-2024-53158, CVE-2024-53159, CVE-2024-53160, CVE-2024-53161, CVE-2024-53162, CVE-2024-53166, CVE-2024-53169, CVE-2024-53171, CVE-2024-53173, CVE-2024-53174, CVE-2024-53179, CVE-2024-53180, CVE-2024-53188, CVE-2024-53190, CVE-2024-53191, CVE-2024-53200, CVE-2024-53201, CVE-2024-53202, CVE-2024-53206, CVE-2024-53207, CVE-2024-53208, CVE-2024-53209, CVE-2024-53210, CVE-2024-53213, CVE-2024-53214, CVE-2024-53215, CVE-2024-53216, CVE-2024-53217, CVE-2024-53222, CVE-2024-53224, CVE-2024-53229, CVE-2024-53234, CVE-2024-53237, CVE-2024-53240, CVE-2024-53241, CVE-2024-56536, CVE-2024-56539, CVE-2024-56549, CVE-2024-56551, CVE-2024-56562, CVE-2024-56566, CVE-2024-56567, CVE-2024-56576, CVE-2024-56582, CVE-2024-56599, CVE-2024-56604, CVE-2024-56605, CVE-2024-56645, CVE-2024-56667, CVE-2024-56752, CVE-2024-56754, CVE-2024-56755, CVE-2024-56756, CVE-2024-8805 Jira References: PED-10467 Maintenance Incident: [SUSE:Maintenance:37044](https://smelt.suse.de/incident/37044/) Sources used: openSUSE Leap 15.6 (src): kernel-source-rt-6.4.0-150600.10.23.1, kernel-syms-rt-6.4.0-150600.10.23.1 SUSE Linux Enterprise Live Patching 15-SP6 (src): kernel-livepatch-SLE15-SP6-RT_Update_7-1-150600.1.3.1 SUSE Real Time Module 15-SP6 (src): kernel-source-rt-6.4.0-150600.10.23.1, kernel-syms-rt-6.4.0-150600.10.23.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. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1235959] New: Kernel 6.6.69 & 6.6.71 does not boot
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235959 Bug ID: 1235959 Summary: Kernel 6.6.69 & 6.6.71 does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sanyi(a)dekom.hu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Community User Blocker: --- Created attachment 879676 --> https://bugzilla.suse.com/attachment.cgi?id=879676&action=edit screenshot of frozen boot process HW environment: HP Elitedesk G2 Micro, i5-6500T, 16Gbram, Nvme boot, ssd storage, integrated LAN. SW: NAME="openSUSE MicroOS" VERSION="20250113" with transactional update and kernel-longterm installed. kernels 6.6.68 and previous ones are booting and working fine. Automatic transactional update to 6.6.69 resulted in an unbootable system. After rolling back and locking 6.6.69 came release of 6.6.71: updating to this kernel also resulted in an unbootable system. Based on the update logs the initrd is correctly generated. The kernel boot stops after "clk: Disabling unused clocks", in a normal boot sequence after this comes "Freeing unused memory" and starting initrd, here the boot stops and sometimes 5-6 minutes later the system reboots. Attached are screenshots of the boot process through intel AMT remote desktip (MeshCommander) with kernel paraemteters mitigations=off, acpi=debug, and quiet removed from grub cmdline. Any advice on further debug possibilites? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1235826] Resolution 5120x1440 @240hz causes flickering and display corruption
by bugzilla_noreply＠suse.com 17 Jan '25

17 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235826 https://bugzilla.suse.com/show_bug.cgi?id=1235826#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pontus0077@gmail. | |com) Status|NEW |IN_PROGRESS --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #3) > So it's only an amdgpu issue for some devices, but the patch changes the > behavior for all cards and drivers. This needs to be resolved first. There is a different patch to try: https://lore.kernel.org/all/7cf3ceed-056a-4be0-804f-91f946db2b33@amd.com/ Could you try it from: https://build.opensuse.org/project/monitor/home:jirislaby:stable-bsc1235826 ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1233381] New: Tumbleweed won’t recover from sleep. Force shutdown required
by bugzilla_noreply＠suse.com 16 Jan '25

16 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233381 Bug ID: 1233381 Summary: Tumbleweed won’t recover from sleep. Force shutdown required Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kosimo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Once the computer enters sleep it won’t wake up anymore. I have to force a shut down and power it up again. Blank screen, not even cap loks light on the keyboard. ---------------- JJJJJJ =JJJJJJJ OS: openSUSE Tumbleweed x86_64 JJJJ =JJJ JJJJ Kernel: 6.11.7-1-default JJJ =JJJ JJJ Uptime: 1 hour, 1 min JJJJ =JJJ JJJ Packages: 42 (pip), 2744 (rpm), 12 (steam), 6 (flatpak-system) JJJJJJJJJJJJJJJ JJJJ Shell: bash 5.2.37 JJJJJJJJJJJJJJ JJJJ Resolution: 3840x2160 JJJJ JJJJ DE: Plasma 6.2.3 [KF 6.8.0] [Qt 6.8.0] (wayland) JJJJJ= JJJJ WM: kwin_wayland_wr JJJJJJJJJJJJJJJJJJJJJJJJJJJJJ= Theme: Breeze-Dark [GTK2/3] =JJJJJJJJJJJJJJJJJJJJJJJJJJJJJ Icons: breeze-dark [GTK2/3] JJJJ =JJJJJJ Terminal: konsole JJJJ =JJJJ CPU: AMD Ryzen 7 7800X3D (8) @ 5.050GHz JJJJ JJJJJJJJJJJJJJ GPU: AMD ATI TUF Gaming Radeon RX 7900 XTX OC JJJJ JJJJJJJJJJJJJJJ GPU: AMD ATI Raphael JJJJ JJJJ JJJJ Memory: 5884.57 MiB / 63432.22 MiB ----------------------- KDE 6.2.3 Frameworks: 6.8.0 QT: 6.8.0 -- You are receiving this mail because: You are the assignee for the bug.

1 6