January 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1219056] New: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle
by bugzilla_noreply＠suse.com 05 Feb '24

05 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219056 Bug ID: 1219056 Summary: ASUS Expertbook B5302F - system doesn't sleep properly, no s0 residency in s2idle 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: davor.virag(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:121.0) Gecko/20100101 Firefox/121.0 Build Identifier: I'm using Intel's S0ixSelftestTool (https://github.com/intel/S0ixSelftestTool/) as I was getting seemingly high battery drain in sleep. According to the logs, it can get the CPU into PC10 state, but the logs state: "Your system supports S0ix substates, but did not achieve the shallowest s0i2.0" I have tried "powertop --calibrate" and "powertop --auto-tune", but the s0 self-etst logs still look the same Reproducible: Always Steps to Reproduce: 1. Run "s0ix-selftest-tool.sh -s" 2. Check for s0 residency Actual Results: CPU Core C7 residency after S2idle is: 98.34 GFX RC6 residency after S2idle is: CPU Package C-state 2 residency after S2idle is: 2.79 CPU Package C-state 3 residency after S2idle is: 2.26 CPU Package C-state 8 residency after S2idle is: 0.21 CPU Package C-state 9 residency after S2idle is: 1.33 CPU Package C-state 10 residency after S2idle is: 88.21 S0ix residency after S2idle is: 0.00 Your system supports S0ix substates, but did not achieve the shallowest s0i2.0 Here is the S0ix substates status: Substate Residency S0i2.0 0 S0i3.0 0 (...) Did not detect the potential blockers from substate_requirements, need to check substate_status_registers file for the advanced debug. (...) Your system south port controller power gating state is OK after 30 seconds runtime check. Expected Results: Residency in one of the s0 states -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1219242] New: [Build 20240125] openQA test fails in fallocate06
by bugzilla_noreply＠suse.com 02 Feb '24

02 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1219242 Bug ID: 1219242 Summary: [Build 20240125] openQA test fails in fallocate06 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3895229/modules/fall ocate06/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation There wasn't a kernel update today but this LTP test started failing in different workers: ----snip---- # wait_serial expected: qr/### TEST fallocate06 COMPLETE >>> \d+\./u # Result: tst_device.c:293: TWARN: Failed to create test_dev.img: ENOSPC (28) tst_device.c:354: TBROK: Failed to acquire device HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 ### TEST fallocate06 COMPLETE >>> 6. ----snip---- openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-ltp-syscalls@uefi_virtio-2G fails in [fallocate06](https://openqa.opensuse.org/tests/3895229/modules/fallocate06/… ## Test suite description ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888826) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886452) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1219275] New: user interface slow (regression)
by bugzilla_noreply＠suse.com 31 Jan '24

31 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219275 Bug ID: 1219275 Summary: user interface slow (regression) 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: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the latest kernel-default 6.7.1-1.1 the user interface is slower than before with 6.6.11-1.1. E.g. I can clearly see how windows are redrawn (e.g. content of xterm). I can pinpoint this to the kernel since booting the old kernel resolves the problem. System information: Intel(R) Xeon(R) W-2123 CPU @ 3.60GHz 32 GiB RAM NVIDIA Corporation GP107GL [Quadro P600] (rev a1) using nouveau -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1219361] New: Kernel 6.7.1-2.1 module conflict during update
by bugzilla_noreply＠suse.com 31 Jan '24

31 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219361 Bug ID: 1219361 Summary: Kernel 6.7.1-2.1 module conflict during update 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: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872326 --> https://bugzilla.suse.com/attachment.cgi?id=872326&action=edit zypper logs Ran `zypper dup` today and got errors about conflicting kernel module files. The following 2 packages are going to be upgraded: openSUSE-release openSUSE-release-appliance-custom The following product is going to be upgraded: openSUSE Tumbleweed 20240126-0 -> 20240128-0 The following 2 packages are going to be reinstalled: kernel-default-6.7.1-2.1 kernel-default-devel-6.7.1-2.1 Was there a packaging error or is something messed up on my system? I already have kernel-default-6.7.1-2.1 installed but zypper seems to see the one installed as different from the one in the repo: > sudo zypper se -s kernel-default Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+-----------------------------+---------+----------------+--------+----------------------------- i+ | kernel-default | package | 6.7.1-2.1 | x86_64 | (System Packages) i+ | kernel-default | package | 6.7.1-1.1 | x86_64 | (System Packages) v | kernel-default | package | 6.7.1-2.1 | x86_64 | openSUSE-Tumbleweed-Main-OSS Attached zypper logs. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c16 --- Comment #16 from Michal Hocko <mhocko(a)suse.com> --- (In reply to Daniel Wagner from comment #14) > Ah Thorsten Leemhuise corrected himself, it seems to be > > 4ef9ad19e17676 ("mm: huge_memory: don't force huge page alignment on 32 > bit") > > but according some testing by the Arch folks it is not a complete fix. Nope, this only affects 32b apps on 64b systems. And it mostly breaks ASLR (see bug 1218800. This should be already in stable kernel branch -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c15 --- Comment #15 from Michal Hocko <mhocko(a)suse.com> --- (In reply to Daniel Wagner from comment #14) > Ah Thorsten Leemhuise corrected himself, it seems to be > > 4ef9ad19e17676 ("mm: huge_memory: don't force huge page alignment on 32 > bit") > > but according some testing by the Arch folks it is not a complete fix. I can see how this can over consume on thread's stacks because those are usually 2MB in size by default (by glibs) and the alignment would make it more likely THP target. I do not see THP would consume all the additional memory, though. Runtime overhead is likely a more likely visible effect. That being said. No objection to taking the patch from my end. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c14 --- Comment #14 from Daniel Wagner <daniel.wagner(a)suse.com> --- Ah Thorsten Leemhuise corrected himself, it seems to be 4ef9ad19e17676 ("mm: huge_memory: don't force huge page alignment on 32 bit") but according some testing by the Arch folks it is not a complete fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c13 --- Comment #13 from Daniel Wagner <daniel.wagner(a)suse.com> --- apparently the fix is: c4608d1bf7c653 ("mm: mmap: map MAP_STACK to VM_NOHUGEPAGE") -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218283] New: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218283 Bug ID: 1218283 Summary: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto 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: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fail: https://build.opensuse.org/package/live_build_log/filesystems/zfs/openSUSE_… [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end' [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin' Upstream tracks the issue here https://github.com/openzfs/zfs/issues/15401 and here https://github.com/openzfs/zfs/issues/14555 It could be fixed by reverting this kernel patch: https://github.com/torvalds/linux/commit/aaeca98456431a8d9382ecf48ac4843e25… -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1219284] increased ram usage after upgrading from 6.6.x to 6.7.x
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219284 https://bugzilla.suse.com/show_bug.cgi?id=1219284#c12 --- Comment #12 from Andrea Manzini <andrea.manzini(a)suse.com> --- all the measurements were taken from the same fresh installed tumbleweed virtual machine with XFCE desktop environment, so same userspace. Just did these action to reproduce: - boot choosing the 6.6 kernel - start the DE - open a terminal to run commands - reboot - choose 6.7 kernel - start the DE - open a terminal to run commands -- You are receiving this mail because: You are the assignee for the bug.

1 0