December 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1201963] New: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1201963 Bug ID: 1201963 Summary: 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70�C until it reaches 54�C 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: gryffus(a)hkfree.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860458 --> https://bugzilla.suse.com/attachment.cgi?id=860458&action=edit Turbostat log output I have a Dell Latitude 5420 laptop and i am experiencing CPU slowdown when using any graphical / CPU demanding application. The laptop contains 11th Gen Intel(R) Core(TM) i5-1145G7 which can do 4,4GHz on turbo. When the system reaches about 70�C, all cores switch to 400MHz and stay there until temperature hits 53-54�C. I can see this behavior especially in Vulkan graphics applications, but not only in them, it just happens almost instantly there, since the 70�C is reached within about 30 seconds there. I would want to raise the temperature limits to at least 80-90�C or disable throttling completely (at my own responsibility of cooking it). But throttling from 70�C seems as a complete nonsense to me - the CPU package gets to this temperature in 10-20 seconds under load, so i basically never make use of the 4,4GHz. What i have tried: 1) Kernel 5.19 from Kernel:HEAD - no change 2) installed throttled ( https://github.com/erpalma/throttled ) - no change 3) blacklisted intel_powerclamp, intel_rapl_msr, processor_thermal_rapl, intel_rapl_common kernel modules - no change 4) cpupower frequency-set -g performance - no change # cat /sys/devices/platform/*/uuids/current_uuid INVALID # cat /sys/devices/platform/*/uuids/available_uuids UNKNOWN # cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 4.40 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.16 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes # cpupower idle-info CPUidle driver: intel_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 4 Available idle states: POLL C1_ACPI C2_ACPI C3_ACPI POLL: Flags/Description: CPUIDLE CORE POLL IDLE Latency: 0 Usage: 265266 Duration: 8068126 C1_ACPI: Flags/Description: ACPI FFH MWAIT 0x0 Latency: 1 Usage: 10617293 Duration: 1984558460 C2_ACPI: Flags/Description: ACPI FFH MWAIT 0x31 Latency: 253 Usage: 273458 Duration: 261649941 C3_ACPI: Flags/Description: ACPI FFH MWAIT 0x60 Latency: 1048 Usage: 206150 Duration: 509227956 # cpupower info analyzing CPU 0: perf-bias: 0 Turbostat debug log attached. Some further reading with probably related reports: https://www.dell.com/community/Latitude/Latitude-5420-7420-7520-CPU-Throttl… https://github.com/intel/thermal_daemon/issues/341 https://github.com/intel/thermal_daemon/issues/293 https://github.com/erpalma/throttled Any clues? -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1204063] Kernel 5.19.8 appears to be missing lpuart earlycon and console
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1204063 https://bugzilla.suse.com/show_bug.cgi?id=1204063#c9 --- Comment #9 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Kernel config change was already merged. earlycon usage was clarified. Perhaps we could close this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206466] [kernel 6.1] User space regression (?) identified by python-ephemeral-port-reserve
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206466 https://bugzilla.suse.com/show_bug.cgi?id=1206466#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> --- Created attachment 863554 --> https://bugzilla.suse.com/attachment.cgi?id=863554&action=edit C reproducer Bisected to: commit 28044fc1d4953b07acec0da4d2fc4784c57ea6fb Author: Joanne Koong <joannelkoong(a)gmail.com> Date: Mon Aug 22 11:10:21 2022 -0700 net: Add a bhash2 table hashed by port and address I'm not sure if the issue is in the commit or in the test ;). I am attaching a simple repro. The second bind(), without SO_REUSEADDR used to fail, now it does not. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206466] New: [kernel 6.1] User space regression (?) identified by python-ephemeral-port-reserve
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206466 Bug ID: 1206466 Summary: [kernel 6.1] User space regression (?) identified by python-ephemeral-port-reserve 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel 6.1, as staged in :J passes most builds, except https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… That python script fails the test suite with [ 36s] + pytest-3.8 --ignore=_build.python38 --ignore=_build.python39 --ignore=_build.python310 -v [ 37s] ============================= test session starts ============================== [ 37s] platform linux -- Python 3.8.16, pytest-7.1.2, pluggy-1.0.0 -- /usr/bin/python3.8 [ 37s] cachedir: .pytest_cache [ 37s] rootdir: /home/abuild/rpmbuild/BUILD/ephemeral-port-reserve-1.1.4 [ 37s] collecting ... collected 4 items [ 37s] [ 37s] tests/ephemeral_port_test.py::test_localhost FAILED [ 25%] [ 37s] tests/ephemeral_port_test.py::test_fqdn FAILED [ 50%] [ 37s] tests/ephemeral_port_test.py::test_preferred_port PASSED [ 75%] [ 37s] tests/ephemeral_port_test.py::test_preferred_port_in_use PASSED [100%] [ 37s] [ 37s] =================================== FAILURES =================================== [ 37s] ________________________________ test_localhost ________________________________ [ 37s] [ 37s] def test_localhost(): [ 37s] > assert_ip(LOCALHOST) [ 37s] [ 37s] tests/ephemeral_port_test.py:44: [ 37s] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ [ 37s] [ 37s] ip = '127.0.0.1' [ 37s] [ 37s] def assert_ip(ip): [ 37s] port = reserve(ip) [ 37s] [ 37s] # show that we can't bind to it without SO_REUSEADDR [ 37s] error = bind_naive(ip, port) [ 37s] > assert error and error.errno == errno.EADDRINUSE, error [ 37s] E AssertionError: None [ 37s] E assert (None) [ 37s] [ 37s] tests/ephemeral_port_test.py:35: AssertionError [ 37s] __________________________________ test_fqdn ___________________________________ [ 37s] [ 37s] def test_fqdn(): [ 37s] fqip = socket.gethostbyname(getfqdn()) [ 37s] > assert_ip(fqip) [ 37s] [ 37s] tests/ephemeral_port_test.py:49: [ 37s] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ [ 37s] [ 37s] ip = '127.0.0.1' [ 37s] [ 37s] def assert_ip(ip): [ 37s] port = reserve(ip) [ 37s] [ 37s] # show that we can't bind to it without SO_REUSEADDR [ 37s] error = bind_naive(ip, port) [ 37s] > assert error and error.errno == errno.EADDRINUSE, error [ 37s] E AssertionError: None [ 37s] E assert (None) [ 37s] [ 37s] tests/ephemeral_port_test.py:35: AssertionError [ 37s] =========================== short test summary info ============================ [ 37s] FAILED tests/ephemeral_port_test.py::test_localhost - AssertionError: None [ 37s] FAILED tests/ephemeral_port_test.py::test_fqdn - AssertionError: None [ 37s] ========================= 2 failed, 2 passed in 0.10s ========================== -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206287] Kernel BUG fs/ext4/inode.c:3627 and kernel BUG at fs/ext4/super.c:493!
by bugzilla_noreply＠suse.com 16 Dec '22

16 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206287 https://bugzilla.suse.com/show_bug.cgi?id=1206287#c6 --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Joe S from comment #5) > Any thoughts on whether kvm or virtualbox would be a better option with > better support? Whole opensuse build system runs on kvm. Many of us run kvm every day. virtualbox is well supported in opensuse too. Of course, both hit some bugs at times (I personally remember only few on TW.) Kvm is fully opensource and completely a part of the kernel, so we can support it. (Unlike virtualbox.) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1205597] ltp:pty03:slcan: null-ptr-deref in process_one_work
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205597 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206359] New: kernel 6.1: random build failures: "error: <random package>: install failed"
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206359 Bug ID: 1206359 Summary: kernel 6.1: random build failures: "error: <random package>: install failed" 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 CC: dimstar(a)opensuse.org, jack(a)suse.com, rgoldwyn(a)suse.com Found By: --- Blocker: --- kernel 6.1 is submitted to openSUSE:Factory:Staging:J. There, a lot of packages randomly fail. It happens usually at the installation phase and looks like (build rpm): > [ 12s] libdb-4_8-4.8.30-41.81 ######################################## > [ 12s] error: libdb-4_8-4.8.30-41.81.x86_64: install failed > [ 12s] perl-5.36.0-5.47 ######################################## > [ 13s] liblsan0-12.2.1+git537-2.20 ######################################## Note that the failure is intermittent. Only some package installations fail (here libdb only). Note this can happen later in the loop (samba rpm): > error: samba-libs-4.17.3+git.283.2157972742b-3.2.x86_64: install failed > ... > [ 2288s] failed to install rpms, aborting build >... > [ 2288s] [0;1;38;5;185mFailed to write wtmp record, ignoring: Read-only file system[0m > [ 2288s] [0;1;38;5;185mFailed to write utmp record: Read-only file system[0m I'm currently out of ideas. It looks like the VM image becomes RO and then RW randomly. The image is ext4. I cannot reproduce locally with --kvm-type=kvm. Any hint anyone? -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 1205149] New: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205149 Bug ID: 1205149 Summary: %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel rpm scriptlets will be moved to a separate subpackage (see https://github.com/openSUSE/suse-module-tools/pull/64). kmps do already (pre)require suse-kernel-rpm-scriptlets just fine. However during build those prerequires are not seen by the OBS schedule as they are hidden inside the %suse_kernel_module_package macro. So the package install check after build fails due to missing scriptlets. Therefore %kernel_module_package_buildreqs needs to list suse-kernel-rpm-scriptlets -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1206287] Kernel BUG fs/ext4/inode.c:3627 and kernel BUG at fs/ext4/super.c:493!
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206287 https://bugzilla.suse.com/show_bug.cgi?id=1206287#c4 --- Comment #4 from Jan Kara <jack(a)suse.com> --- So by the "trace" I think Jiri meant the stacktrace. In particular that: kernel: set_page_dirty_lock+0x2e/0x80 kernel: qp_release_pages+0x65/0xf0 [vmw_vmci 5e22bd5b5c5e7589ba0c625c044e209a9cc6e594] kernel: qp_host_unregister_user_memory+0x23/0x80 [vmw_vmci 5e22bd5b5c5e7589ba0c625c044e209a9cc6e594] kernel: vmci_qp_broker_detach+0x19a/0x3f0 [vmw_vmci 5e22bd5b5c5e7589ba0c625c044e209a9cc6e594] kernel: vmci_host_unlocked_ioctl+0x9b/0xb20 [vmw_vmci 5e22bd5b5c5e7589ba0c625c044e209a9cc6e594] kernel: __x64_sys_ioctl+0x90/0xd0 kernel: do_syscall_64+0x5b/0x80 comes from the vmw_vmci driver. Looking at this trace it is pretty clear VMCI driver is actually hitting the problem describe e.g. here: https://patchwork.kernel.org/project/linux-fsdevel/patch/CA+eFSM0U_i+rZH5PR… The problem is that the driver gets page reference with get_user_pages(), then reclaim attempts to reclaim these pages which strips fs private data from these pages and then when pages get dirtied, the filesystem complains. This does not have anything to do with the data=journal mode. The solution to this problem is twofold: 1) VMCI needs to call pin_user_pages() (instead of get_user_pages()) to properly inform MM that it's going to be accessing page contents with some out-of-band method. It also needs to use unpin_user_page() instead of put_page(). 2) Page reclaim needs to avoid stripping page private data from pinned pages (that is work in progress upstream, I guess I can kick that ball a bit further ;)). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1206321] New: livepatch test klp_tc_8.sh fails: rmmod: ERROR: Module klp_tc_8_4_livepatch is in use
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206321 Bug ID: 1206321 Summary: livepatch test klp_tc_8.sh fails: rmmod: ERROR: Module klp_tc_8_4_livepatch is in use Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-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 Found By: --- Blocker: --- This looks to be some race (does not fail always) [1]. It has been here at least since build 20221123 [2] which has 6.0.8-1.1 (1579d93) (likely before, but older failed logs cleared, it might be just on 6.0.x stable branch). ppc64le version looks to be OK [3]. I was not able to reproduce it on my laptop (6.1.0-rc8-2.g2fb1790-default), nor in my openQA instance [4] (might be related to o3 setup/infrastructure). Logs from openQA run (./klp_tc_8.sh) [5], nothing obvious in dmesg [6]. [19:26:53] Test Case 8: Patch with replace-all [19:26:53] *** Compiling live patches [19:26:53] make: Entering directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:54] CC [M] /tmp/live-patch/tc_8/patch_replace-all_1/klp_tc_8_1_livepatch.o [19:26:55] MODPOST /tmp/live-patch/tc_8/patch_replace-all_1/Module.symvers [19:26:55] CC [M] /tmp/live-patch/tc_8/patch_replace-all_1/klp_tc_8_1_livepatch.mod.o [19:26:55] LD [M] /tmp/live-patch/tc_8/patch_replace-all_1/klp_tc_8_1_livepatch.ko [19:26:55] BTF [M] /tmp/live-patch/tc_8/patch_replace-all_1/klp_tc_8_1_livepatch.ko [19:26:55] Skipping BTF generation for /tmp/live-patch/tc_8/patch_replace-all_1/klp_tc_8_1_livepatch.ko due to unavailability of vmlinux [19:26:55] make: Leaving directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:55] make: Entering directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:56] CC [M] /tmp/live-patch/tc_8/patch_replace-all_2/klp_tc_8_2_livepatch.o [19:26:56] MODPOST /tmp/live-patch/tc_8/patch_replace-all_2/Module.symvers [19:26:56] CC [M] /tmp/live-patch/tc_8/patch_replace-all_2/klp_tc_8_2_livepatch.mod.o [19:26:57] LD [M] /tmp/live-patch/tc_8/patch_replace-all_2/klp_tc_8_2_livepatch.ko [19:26:57] BTF [M] /tmp/live-patch/tc_8/patch_replace-all_2/klp_tc_8_2_livepatch.ko [19:26:57] Skipping BTF generation for /tmp/live-patch/tc_8/patch_replace-all_2/klp_tc_8_2_livepatch.ko due to unavailability of vmlinux [19:26:57] make: Leaving directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:57] make: Entering directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:58] CC [M] /tmp/live-patch/tc_8/patch_replace-all_3/klp_tc_8_3_livepatch.o [19:26:58] MODPOST /tmp/live-patch/tc_8/patch_replace-all_3/Module.symvers [19:26:58] CC [M] /tmp/live-patch/tc_8/patch_replace-all_3/klp_tc_8_3_livepatch.mod.o [19:26:58] LD [M] /tmp/live-patch/tc_8/patch_replace-all_3/klp_tc_8_3_livepatch.ko [19:26:58] BTF [M] /tmp/live-patch/tc_8/patch_replace-all_3/klp_tc_8_3_livepatch.ko [19:26:58] Skipping BTF generation for /tmp/live-patch/tc_8/patch_replace-all_3/klp_tc_8_3_livepatch.ko due to unavailability of vmlinux [19:26:58] make: Leaving directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:58] make: Entering directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:26:59] CC [M] /tmp/live-patch/tc_8/patch_replace-all_4/klp_tc_8_4_livepatch.o [19:27:00] MODPOST /tmp/live-patch/tc_8/patch_replace-all_4/Module.symvers [19:27:00] CC [M] /tmp/live-patch/tc_8/patch_replace-all_4/klp_tc_8_4_livepatch.mod.o [19:27:00] LD [M] /tmp/live-patch/tc_8/patch_replace-all_4/klp_tc_8_4_livepatch.ko [19:27:00] BTF [M] /tmp/live-patch/tc_8/patch_replace-all_4/klp_tc_8_4_livepatch.ko [19:27:00] Skipping BTF generation for /tmp/live-patch/tc_8/patch_replace-all_4/klp_tc_8_4_livepatch.ko due to unavailability of vmlinux [19:27:00] make: Leaving directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:27:00] make: Entering directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:27:01] CC [M] /tmp/live-patch/tc_8/patch_replace-all_5/klp_tc_8_5_livepatch.o [19:27:01] MODPOST /tmp/live-patch/tc_8/patch_replace-all_5/Module.symvers [19:27:01] CC [M] /tmp/live-patch/tc_8/patch_replace-all_5/klp_tc_8_5_livepatch.mod.o [19:27:01] LD [M] /tmp/live-patch/tc_8/patch_replace-all_5/klp_tc_8_5_livepatch.ko [19:27:01] BTF [M] /tmp/live-patch/tc_8/patch_replace-all_5/klp_tc_8_5_livepatch.ko [19:27:01] Skipping BTF generation for /tmp/live-patch/tc_8/patch_replace-all_5/klp_tc_8_5_livepatch.ko due to unavailability of vmlinux [19:27:01] make: Leaving directory '/usr/src/linux-6.0.12-1-obj/x86_64/default' [19:27:01] *** Inserting getpid patch 1 [19:27:02] *** Wait for completion (klp_tc_8_1_livepatch) [19:27:02] *** Inserting getpid patch 2 [19:27:02] *** Wait for completion (klp_tc_8_2_livepatch) [19:27:02] *** Inserting getpid patch 3 [19:27:02] *** Wait for completion (klp_tc_8_3_livepatch) [19:27:02] *** Inserting getpid patch 4 [19:27:02] *** Wait for completion (klp_tc_8_4_livepatch) [19:27:02] *** Inserting getpid patch 5 [19:27:02] *** Wait for completion (klp_tc_8_5_livepatch) [19:27:02] *** Removing getpid patch 1 [19:27:02] *** Removing getpid patch 2 [19:27:02] *** Removing getpid patch 3 [19:27:02] *** Removing getpid patch 4 [19:27:02] rmmod: ERROR: Module klp_tc_8_4_livepatch is in use [19:27:02] *** Removing patches [19:27:02] TEST FAILED while executing 'rmmod "$PATCH_MOD_NAME"' [1] https://openqa.opensuse.org/tests/2947725#next_previous [2] https://openqa.opensuse.org/tests/2899233 [3] https://openqa.opensuse.org/tests/2948060#next_previous [4] http://quasar.suse.cz/tests/1446#next_previous [5] https://openqa.opensuse.org/tests/2947725/file/serial_terminal.txt [6] https://openqa.opensuse.org/tests/2947725/file/serial0.txt -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1206288] New: "BIOS-provided physical RAM map" changing each boot, breaks suspend-to-disk
by bugzilla_noreply＠suse.com 14 Dec '22

14 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206288 Bug ID: 1206288 Summary: "BIOS-provided physical RAM map" changing each boot, breaks suspend-to-disk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: draeath(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently updated my kernel to "kernel-default-6.0.10-1.1.x86_64" and since then, suspend-to-disk resumption fails with the following: [ 13.325035] PM: Loading and decompressing image data (1158298 pages)... [ 13.325044] Hibernate inconsistent memory map detected! [ 13.325085] PM: hibernation: Image mismatch: architecture specific data [ 13.325114] PM: hibernation: Read 4633192 kbytes in 0.01 seconds (463319.20 MB/s) [ 13.326883] PM: Error -1 resuming [ 13.326890] PM: hibernation: Failed to load image, recovering. A stab in the dark found that the physical RAM map is changing each boot. I found an old kernel bug from many (6?) years ago where this occurred (redhat's bugzilla) so there is precedent for this causing this sort of problem: https://bugzilla.redhat.com/show_bug.cgi?id=1442601 I performed a diff (with git so it can localize where in the line the changes are) of the RAM map dmesg lines: diff --git a/prior-rammap.txt b/current-rammap.txt index ebd9618..ef28665 100644 --- a/prior-rammap.txt +++ b/current-rammap.txt @@ -12,9 +12,9 @@ BIOS-e820: [mem 0x0000000076953000-0x0000000076953fff] reserved BIOS-e820: [mem 0x0000000076954000-0x0000000076954fff] usable BIOS-e820: [mem 0x0000000076955000-0x00000000803fffff] reserved BIOS-e820: [mem 0x00000000ff610000-0x00000000ff64ffff] reserved BIOS-e820: [mem 0x0000000100000000-0x000000047e8[-2c-]{+4b+}fff] usable BIOS-e820: [mem 0x000000047e8[-2d-]{+4c+}000-0x000000047e8[-2d-]{+4c+}fff] ACPI data BIOS-e820: [mem 0x000000047e8[-2e-]{+4d+}000-0x000000047f800fff] usable BIOS-e820: [mem 0x000000047f801000-0x000000047f802fff] reserved BIOS-e820: [mem 0x000000047f803000-0x000000047f824fff] usable BIOS-e820: [mem 0x000000047f825000-0x000000047f82cfff] ACPI NVS I should note, it's not impossible this is a firmware problem. I updated my machine's firmware around the same time. I'm engaging vendor support regarding that. (System76 Darter Pro "darp8" running coreboot 4.17) -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1206084] pynfs fails in test nfs4.0 on x86-64 and aarch64
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206084 https://bugzilla.suse.com/show_bug.cgi?id=1206084#c5 --- Comment #5 from Yong Sun <yosun(a)suse.com> --- The openqa test script use a single command to test them all. Hard to add code to get client number after each test, I'm updating my local TW machine to have a manually test later. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c9 --- Comment #9 from Chris Friedmann <friedmann.christopher(a)gmail.com> --- Can confirm that 6.1 from stable repo has the same issue, and that the same parameter fixes it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206371] New: Perf trace may display bogus timings
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206371 Bug ID: 1206371 Summary: Perf trace may display bogus timings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863498 --> http://bugzilla.opensuse.org/attachment.cgi?id=863498&action=edit Reproducer You will find attached a simple C program that sleeps in a loop, meant to mimick the behavior of the slurmctld Slurm daemon on which I actually observed the bug. You can compile it and run it with "gcc -std=c99 sleeper.c && ./a.out". While it's running, monitor clock_nanosleep syscalls with "perf trace -e clock_nanosleep", and if you're like me, you will eventually observe bogus timings (though it may take a few seconds and/or multiple runs) : --- [ ... ] 7615.211 (100.191 ms): slurmctld/2280 clock_nanosleep(which_clock: 0, flags: 0, rqtp: 0x7fff25018b60, rmtp: NULL) = 0 7715.414 (100.213 ms): slurmctld/2280 clock_nanosleep(which_clock: 0, flags: 0, rqtp: 0x7fff25018b60, rmtp: NULL) = 0 7815.640 ( ): slurmctld/2280 clock_nanosleep(which_clock: 0, flags: 0, rqtp: 0x7fff25018b60, rmtp: NULL) ... 7915.876 (18446744073709.516 ms): slurmctld/2280 clock_nanosleep(which_clock: 0, flags: 0, rqtp: 0x7fff25018b60, rmtp: NULL) = 0 7915.876 (100.095 ms): slurmctld/2280 ... [continued]: clock_nanosleep()) = 0 8016.012 (100.073 ms): slurmctld/2280 clock_nanosleep(which_clock: 0, flags: 0, rqtp: 0x7fff25018b60, rmtp: NULL) = 0 [ ... ] --- I cannot reproduce this on another system running Tumbleweed, perhaps it has been fixed on newer kernel/perf releases? Or perhaps this is somehow specific to this Leap system in another, unknown way. If I were to bet on a possible explanation, I would wager that perf trace may not correctly handle task CPU migrations, but this is just an educated guess and advice on rigorously debugging this further is very much welcome. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c8 --- Comment #8 from Chris Friedmann <friedmann.christopher(a)gmail.com> --- The command line parameter fixes it, thank you! I've never installed a kernel outside of zypper dup, do I simply download the .rpm and install it as normal, then choose the kernel from e.g yast? And is this the best choice to use: kernel-default-6.1.0-1.1.gc3232e1.x86_64.rpm ? Thanks for your help. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- Also can you test 6.1 from Kernel:stable if it is broken the same way? I.e. without the parameter it doesn't work and with the parameter it does. https://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c6 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(friedmann.christo | |pher(a)gmail.com) --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- Does this kernel command line parameter fix it: psmouse.synaptics_intertouch=0 ? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c5 --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- commit 268d3f4435477c819cfac3d63eb68f846ef98788 Refs: v6.0.10-214-g268d3f443547 Author: Aman Dhoot <amandhoot12(a)gmail.com> AuthorDate: Sat Oct 15 20:41:17 2022 -0700 Commit: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> CommitDate: Fri Dec 2 17:43:13 2022 +0100 Input: synaptics - switch touchpad on HP Laptop 15-da3001TU to RMI mode [ Upstream commit ac5408991ea6b06e29129b4d4861097c4c3e0d59 ] The device works fine in native RMI mode, there is no reason to use legacy PS/2 mode with it. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(friedmann.christo | |pher(a)gmail.com) | --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- > -psmouse serio1: synaptics: Your touchpad (PNP: SYN3286 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input(a)vger.kernel.org. > +psmouse serio1: synaptics: Trying to set up SMBus access > +psmouse serio1: synaptics: SMbus companion is not ready yet -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c3 --- Comment #3 from Chris Friedmann <friedmann.christopher(a)gmail.com> --- Created attachment 863495 --> https://bugzilla.suse.com/attachment.cgi?id=863495&action=edit dmesg 6.0.12-1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c2 --- Comment #2 from Chris Friedmann <friedmann.christopher(a)gmail.com> --- Created attachment 863494 --> https://bugzilla.suse.com/attachment.cgi?id=863494&action=edit dmesg 6.0.10-1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206358] Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206358 https://bugzilla.suse.com/show_bug.cgi?id=1206358#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |friedmann.christopher@gmail | |.com, jslaby(a)suse.com Flags| |needinfo?(friedmann.christo | |pher(a)gmail.com) --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Can you collect dmesg output from both kernels? E.g. by remote login. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206287] Kernel BUG fs/ext4/inode.c:3627 and kernel BUG at fs/ext4/super.c:493!
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1206287 https://bugzilla.suse.com/show_bug.cgi?id=1206287#c1 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Provided the trace shows this came from the vmw_vmci module, you'd have to complain to VMWare. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 1206358] New: Complete loss of keyboard function with kernel 6.0.12-1
by bugzilla_noreply＠suse.com 13 Dec '22

13 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1206358 Bug ID: 1206358 Summary: Complete loss of keyboard function with kernel 6.0.12-1 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: friedmann.christopher(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- HP DA1004no laptop with OpenSUSE Tumbleweed. Updating kernel from 6.0.10-1 to 6.0.12-1 results in complete loss of keyboard functionality, verified that reverting kernel to older version resolves issue. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 12 Dec '22

12 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c13 --- Comment #13 from Philippe Cond� <conde.philippe(a)skynet.be> --- Created attachment 863457 --> https://bugzilla.suse.com/attachment.cgi?id=863457&action=edit journalctl output with kernel 6.0.12 (3 locks) -- You are receiving this mail because: You are the assignee for the bug.

1 0