January 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 27 Jan '24

27 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c21 Urvi Monty <software_suseidp(a)orcadian.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |software_suseidp(a)orcadian.n | |et Resolution|FIXED |--- --- Comment #21 from Urvi Monty <software_suseidp(a)orcadian.net> --- This appears to be broken again as of kernel-default-6.7.1-1.1.aarch64 The wsa883x module is not present at all. Audio is no longer working. ls /usr/lib/modules 6.6.11-1-default 6.7.1-1-default find /usr/lib/modules -name *wsa883* /usr/lib/modules/6.6.11-1-default/kernel/sound/soc/codecs/snd-soc-wsa883x.ko.zst -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219195] /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min increased from 6.6. to 6.7 way too much
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219195 https://bugzilla.suse.com/show_bug.cgi?id=1219195#c1 Vasilis Liaskovitis <vliaskovitis(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vliaskovitis(a)suse.com --- Comment #1 from Vasilis Liaskovitis <vliaskovitis(a)suse.com> --- The change was possibly introduced in: commit 1958946858a62b6b5392ed075aa219d199bcae39 Author: Ma Jun <Jun.Ma2(a)amd.com> Date: Thu Oct 12 09:33:45 2023 +0800 drm/amd/pm: Support for getting power1_cap_min value Support for getting power1_cap_min value on smu13 and smu11. For other Asics, we still use 0 as the default value. Signed-off-by: Ma Jun <Jun.Ma2(a)amd.com> Reviewed-by: Kenneth Feng <kenneth.feng(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> The above commit may also be an indirect fix for this upstream issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2992 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219195] /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min increased from 6.6. to 6.7 way too much
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219195 Benedict Broy <benedictbroy(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219193] New: 5G Wifi Stopped Working after Kernel 6.7.1 Upgrade
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219193 Bug ID: 1219193 Summary: 5G Wifi Stopped Working after Kernel 6.7.1 Upgrade 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: ismettogay+linux(a)gmail.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/121.0.0.0 Safari/537.36 Build Identifier: Today, I have upgraded Tumbleweed release to 20240124 and 5G Wifi stopped working after the upgrade. Yet, 2G Wifi connection still works. My WLAN controller: Intel Dual Band Wireless-AC 7265 My Wifi Modem Router: ASUS DSL-AC51 Reproducible: Always Steps to Reproduce: 1. Connect to a 5G network 2. Wait 5-10 seconds Actual Results: You get the "Connection [SSID-5G] deactivated. The Wifi network could not be found" error. Expected Results: It should connect to the 5G network. A similar post on reddit for Arch Linux: https://www.reddit.com/r/archlinux/comments/19e103k/anyone_else_having_prob… -- 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 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215523 https://bugzilla.suse.com/show_bug.cgi?id=1215523#c38 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo? | Resolution|--- |FIXED --- Comment #38 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Teuniz XXX from comment #31) > After the latest kernel update (5.14.21-150500.55.31-default) the system > crashed. It's a completely different kernel from the original report, and the symptom is also different. Please open another bug report if you still hit the issue with very latest Leap 15.5 kernel. I close the entry as Leap 15.4 already reached EOL. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 25 Jan '24

25 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c37 --- Comment #37 from Johan Dot <jonte1(a)gmail.com> --- Hi! Sorry for late reply. Added "https://download.opensuse.org/repositories/Kernel:/SLE15-SP5/pool/" yesterday. Works fine to boot the server. Regards -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218948] kernel:[ 3380.214840][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 112s! [kworker/0:2:156]
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218948 https://bugzilla.suse.com/show_bug.cgi?id=1218948#c36 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |frank.kuehndel@embedded-bra | |ins.de --- Comment #36 from Michal Suchanek <msuchanek(a)suse.com> --- *** Bug 1219147 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219147] Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219147 https://bugzilla.suse.com/show_bug.cgi?id=1219147#c3 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Michal Suchanek <msuchanek(a)suse.com> --- Marking as duplicate *** This bug has been marked as a duplicate of bug 1218948 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219147] New: Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219147 Bug ID: 1219147 Summary: Kernel: NULL pointer dereference during boot, 5.14.21-150500.55.44, usb_unbind_interface Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: frank.kuehndel(a)embedded-brains.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872149 --> https://bugzilla.suse.com/attachment.cgi?id=872149&action=edit Screen photos showing kernel oops and systemd output. Since the update to kernel 5.14.21-150500.55.44-default, I experience a spontaneous kernel bug during boot (for the first time on Monday 2024-Jan-22). This did not happen with kernel 5.14.21-150500.55.39-default or the kernels before. This bug appears in about 50% of all starts. This is the sequence of actions: * I power-on my Laptop (Lenovo 20QN-005YGE "P53", NVIDIA GPU) with USB-C docking station connected. * I get the Grub2 menu and let it start the default entry. * I get the usual green text screen to enter the password to decrypt the disk and enter the phrase (see img_1.jpg). * A moment later I see the green kernel oops message (attached as screen photo img_2.jpg). * When I press a key, I can see that systemd got to the point where it wanted to decrypt the disk but then hangs in a filesystem check (see img_4.jpg). * I power my Laptop off (waiting for 15 minutes has no effect). I "believe" the system fails to mount "/" and "/home". Consequently, I cannot find any entry of this oops or the boot at all in /var/log/messages, the journal or with "last". Workaround: * In the Grub2 menu, I choose the "Advanced" entry and boot kernel 5.14.21-150500.55.39-default. * In /etc/zypp/zypp.conf I changed one line multiversion.kernels = latest,latest-1,running to multiversion.kernels = latest,latest-1,running,5.14.21-150500.55.39 in order to prevent the "good" Kernel from beeing deleted. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1219132] [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 https://bugzilla.suse.com/show_bug.cgi?id=1219132#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- This was deliberately changed by: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… to return an empty string in case EAS is not supported. See the commit log. So the test needs to be tuned. -- You are receiving this mail because: You are the assignee for the bug.

1 0