October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c12 --- Comment #12 from Andreas <opendreas(a)gmail.com> --- Created attachment 877848 --> https://bugzilla.suse.com/attachment.cgi?id=877848&action=edit dmesg-6.4.0-150600.23.25 (In reply to Takashi Iwai from comment #11) > Care to check the latest Leap 15.6 kernel in OBS Kernel:SLE15-SP6 repo, too? > http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ With the latest kernel, I had errors in two scenarios: 1. Using VirtualBox 2. After a standby, when trying to intensively download something, for example, large updates or Youtube. Errors with Virtualbox remained with the new kernel, dmesg log after starting Windows in Virtualbox. I'll be testing more; but there are no errors in the quick test yet. But it is impossible to work with Virtualbox. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231416] New: ZSWAP config cleanup
by bugzilla_noreply＠suse.com 09 Oct '24

09 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231416 Bug ID: 1231416 Summary: ZSWAP config cleanup 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 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 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1230414] kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 https://bugzilla.suse.com/show_bug.cgi?id=1230414#c13 --- Comment #13 from Michal Suchanek <msuchanek(a)suse.com> --- The issue exists downto SLE15-SP5 where the commit introducing the non-deterministic BTF generation was backported, it's not part of the base kernel. Prerequisites: c1177979af9c616661a126a80dd486ad0543b836 v6.3-rc1 btf, scripts: Exclude Rust CUs with pahole noop on 5.14, no Rust support 7b99f75942da332e3f4f865e55a10fec95a30d4f v6.5-rc1 bpf: Add --skip_encoding_btf_inconsistent_proto, Fix preventing attachment of functions specialized by the compiler 72d091846de935e0942a8a0f1fe24ff739d85d76 v6.7-rc1 kbuild: avoid too many execution of scripts/pahole-flags.sh Rewrite of how pahole flags are passed around in make fcd1ed89a0439c45e1336bd9649485c44b7597c7 v6.10-rc1 kbuild,bpf: Switch to using --btf_features for pahole v1.26 Another flag passing change, and only for pahole 1.26, we only use 1.25 34021caef79f76e70ac31247d321ecd0683c4939 v6.11-rc1 kbuild, bpf: Use test-ge check for v1.25-only pahole And another one ebb79e96f1ea454fbcc8fe27dfe44e751bd74b4b v6.11-rc1 kbuild: bpf: Tell pahole to DECL_TAG kfuncs Looking at the history this has no prerequisites. bpftool might make use of the data, the kernel does not have support for it and should ignore it. Also requires pahole 1.27 46fb0b62ea29c0dbcb3e44f1d67aafe79bc6e045 v6.11-rc1 kbuild,bpf: Add module-specific pahole flags for distilled Adds new section that might be used by current bpftool, should not affect kernel. Also our pahole does not support it. With the prerequisites applied whatever fix is finally merged upstream should apply cleanly to our kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1230414] kernel: reproducible builds issue with BTF
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230414 https://bugzilla.suse.com/show_bug.cgi?id=1230414#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > I guess the -j1 hack is acceptable as a temporary solution for us, while we > should ping upstream devs for the more proper fix. I pushed the temporary fix with -j1 option to users/tiwai/master/for-next and */stable/for-next branches now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231050] What does this error mean: xs_tcp_setup_socket...unhandled error -107
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231050 https://bugzilla.suse.com/show_bug.cgi?id=1231050#c6 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Neil Brown <nfbrown(a)suse.com> --- I think this is simply an omission from the switch statement in xs_tcp_setup_socket(). -ENOTCONN should be handled the same way as -ECONNREFUSED set. If it was, the error would be passed to xprt_wake_pending_tasks which end up calling call_connect_status() which does handle -ENOTCONN. I'll look thorough the code again when I get a bit more time and ensure that makes sense - then will suggest a patch upstream. Thanks for the report. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1227144] iwlwifi 0000:6f:00.0: Microcode SW error detected. Restarting 0x0.
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1227144 https://bugzilla.suse.com/show_bug.cgi?id=1227144#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- Care to check the latest Leap 15.6 kernel in OBS Kernel:SLE15-SP6 repo, too? http://download.opensuse.org/repositories/Kernel:/SLE15-SP6/pool/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c4 --- Comment #4 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- You are right, my fault. There is an unsolvable: https://build.opensuse.org/package/show/Kernel:stable:Backport:KMP/virtualb… So the Repo might be out of sync. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c3 --- Comment #3 from Daniel Pecka <nettezzaumanaa(a)gmail.com> --- Hi Stefan .. https://download.opensuse.org/repositories/Kernel:/stable:/KMP/standard/x86… is for TW and not leap o.O ... Kernel:/stable:/Backport/standard/ + Kernel:/stable:/Backport:/KMP/standard/ are meant for leap ... regards, ~dan -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c2 --- Comment #2 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- And enable the refresh for the Repos....... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c1 Stephan Hemeier <Sauerlandlinux(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Sauerlandlinux(a)gmx.de --- Comment #1 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- Virtualbox is on Version 7.1: https://download.opensuse.org/repositories/Kernel:/stable:/KMP/standard/x86… So update your System. -- You are receiving this mail because: You are the assignee for the bug.

1 0