October 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1232536] New: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage'
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232536 Bug ID: 1232536 Summary: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage' 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bpftrace tests on Tumbleweed fails on # echo -e "\ninterval:s:5 { exit(); }" | cat /usr/share/bpftrace/tools/swapin.bt - | bpftrace - stdin:1-16: WARNING: swap_readpage is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail Attaching 3 probes... cannot attach kprobe, Invalid argument ERROR: Error attaching probe: 'kprobe:swap_readpage' echo $? 255 # bpftrace --info System OS: Linux 6.11.5-1-default #1 SMP PREEMPT_DYNAMIC Wed Oct 23 04:27:11 UTC 2024 (b4e3aa9) Arch: x86_64 Build version: v0.21.2 LLVM: 18.1.8 unsafe probe: no bfd: no liblldb (DWARF support): yes libsystemd (systemd notify support): no Kernel helpers probe_read: yes probe_read_str: yes probe_read_user: yes probe_read_user_str: yes probe_read_kernel: yes probe_read_kernel_str: yes get_current_cgroup_id: yes send_signal: yes override_return: no get_boot_ns: yes dpath: yes skboutput: yes get_tai_ns: yes get_func_ip: yes jiffies64: yes for_each_map_elem: yes Kernel features Instruction limit: 1000000 Loop support: yes btf: yes module btf: yes map batch: yes uprobe refcount (depends on Build:bcc bpf_attach_uprobe refcount): yes Map types hash: yes percpu hash: yes array: yes percpu array: yes stack_trace: yes perf_event_array: yes ringbuf: yes Probe types kprobe: yes tracepoint: yes perf_event: yes kfunc: yes kprobe_multi: yes uprobe_multi: yes raw_tp_special: yes iter: yes Running the same test on Debian with kernel 6.11.5, and with these different build options it pass: LLVM: 18.1.8 bfd: no liblldb (DWARF support): yes -- You are receiving this mail because: You are the assignee for the bug.

1 23

[Bug 1231167] New: Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231167 Bug ID: 1231167 Summary: Enable CONFIG_SCSI_UFS_QCOM for UFS support on QCOM platforms Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rsalveti(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877673 --> https://bugzilla.suse.com/attachment.cgi?id=877673&action=edit kernel config diff Hi, I'm validating openSUSE Tumbleweed on QCOM-based arm64 platforms (e.g. rb3gen2) and noticed the installer can't find the UFS controller. This patch enables CONFIG_SCSI_UFS_QCOM as module so it can identify UFS controllers on QCOM platforms. Patch attached. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1231832] New: [Build 20241020] openQA test fails in podman_netavark
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231832 Bug ID: 1231832 Summary: [Build 20241020] openQA test fails in podman_netavark Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other URL: https://openqa.opensuse.org/tests/4580879/modules/podm an_netavark/steps/183 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 Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Error: netavark: unable to append rule '-j MARK --set-xmark 0x2000/0x2000' to table 'nat': code: 2, msg: Warning: Extension MARK revision 0 not supported, missing kernel module? ip6tables v1.8.10 (legacy): unknown option "--set-xmark" Try `ip6tables -h' or 'ip6tables --help' for more information The 'missing kernel module', and the fact that we updated the kernel to 6.11.4 in this snapshot (and I did not see anything podman/netavark related) triggered me to file this bug against Kernel component openQA test in scenario microos-Tumbleweed-DVD-x86_64-container-host@64bit fails in [podman_netavark](https://openqa.opensuse.org/tests/4580879/modules/podman_n… ## Test suite description ## Reproducible Fails since (at least) Build [20241020](https://openqa.opensuse.org/tests/4580329) ## Expected result Last good: [20241018](https://openqa.opensuse.org/tests/4577907) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1231825] New: Kernel 6.11.4 bluetooth scan stops working
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231825 Bug ID: 1231825 Summary: Kernel 6.11.4 bluetooth scan stops working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: novell(a)tower-net.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With Kernel 6.11.4 from https://build.opensuse.org/project/show/Kernel:stable:Backport the bluetooth scan doesn't find my mouse any longer. Rebooting 6.11.3 I can pair mouse and booting 6.11.4 I can use a pre-connected but no reconnect possible. dmesg | grep -i blue: [ 1.826585] usb 3-3: Product: Bluetooth Radio [ 2.947702] Bluetooth: Core ver 2.22 [ 2.947728] NET: Registered PF_BLUETOOTH protocol family [ 2.947730] Bluetooth: HCI device and connection manager initialized [ 2.947739] Bluetooth: HCI socket layer initialized [ 2.947743] Bluetooth: L2CAP socket layer initialized [ 2.947748] Bluetooth: SCO socket layer initialized [ 3.118618] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 3.120636] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 3.120645] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 3.126553] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin [ 3.128658] Bluetooth: hci0: RTL: cfg_sz 6, total sz 65603 [ 3.192619] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 3.192622] Bluetooth: BNEP filters: protocol multicast [ 3.192628] Bluetooth: BNEP socket layer initialized [ 3.711634] Bluetooth: hci0: RTL: fw version 0x04479301 [ 3.840057] Bluetooth: hci0: AOSP extensions version v1.00 [ 3.840061] Bluetooth: hci0: AOSP quality report is supported [ 4.081505] Bluetooth: MGMT ver 1.23 [ 15.909955] Bluetooth: hci0: AOSP extensions version v1.00 [ 15.909971] Bluetooth: hci0: AOSP quality report is supported [ 17.644507] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input19 [ 17.644841] input: Lenovo Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input20 [ 17.645123] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input21 [ 17.645391] hid-generic 0005:17EF:60EF.0002: input,hidraw1: BLUETOOTH HID v0.15 Mouse [Lenovo Bluetooth Mouse] on f4:6a:dd:7d:17:10 [ 131.404331] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input22 [ 131.405030] input: Lenovo Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input23 [ 131.405255] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input24 [ 131.405436] hid-generic 0005:17EF:60EF.0003: input,hidraw1: BLUETOOTH HID v0.15 Mouse [Lenovo Bluetooth Mouse] on f4:6a:dd:7d:17:10 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1232650] New: Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 Bug ID: 1232650 Summary: Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode 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: 2835365572zty(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Description: I recently received a new Lenovo Yoga Pro 7 14ASP9 and installed Linux on it (kernel version 6.11.5). Most hardware functions as expected out of the box, including Wi-Fi, Bluetooth, touchpad, keyboard backlight, audio, touchscreen, and graphics card. However, the system fails to wake up after entering sleep/suspend mode. When the system goes into suspend, the power button indicator light continues flashing, but attempting to wake it by pressing the keyboard or the power button has no effect. The system remains unresponsive. I also tried running sudo rtcwake -m mem -s 20 to test suspend mode, but the system did not wake up after the specified 20 seconds. Hardware Information: Device Model: Lenovo Yoga Pro 7 14ASP9 Linux Kernel Version: 6.11.5 dmesg log: https://linux-hardware.org/?probe=414716466d&log=dmesg.1 Full Hardware Probe: https://linux-hardware.org/?probe=414716466d https://pastebin.com/eMTCCPp3 Here is loglevel7 version. Steps to Reproduce: 1.Put the device into suspend/sleep mode via the power menu or by using sudo rtcwake -m mem -s 20. 2.Wait for the device to enter suspend, as indicated by the flashing power button light. 3.Attempt to wake the device by pressing any key or the power button. Expected Behavior: The device should resume from suspend mode, with the display and other system functions restored to a usable state. Actual Behavior: The device remains unresponsive, with only the power button indicator flashing. The system does not respond to key presses or the power button, requiring a forced reboot to recover. Additional Notes: 1.This issue has been observed consistently with kernel version 6.11.5. 2.No errors or warnings related to this behavior appear in the logs leading up to suspend. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1232292] New: Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232292 Bug ID: 1232292 Summary: Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Machine locks on restore from hibernation after upgrade to kernel-default 5.14.21-150500.55.83-default, three days on a row. Machine hibernates normally, but on restore, keyboard leds freeze, does not respond. Display shows the frozen screen saver animation. Machine appears frozen. There is nothing saved on the log after the apparently successful hibernation. I am removing this kernel and going back to 5.14.21-150500.55.73-default, but I still have the journal if you are interested. journal entries: Oct 24 02:37:36 Telcontar sudo[20578]: root : TTY=pts/43 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl hibernate Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:36 Telcontar sudo[20578]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. Oct 24 02:37:36 Telcontar ModemManager[1718]: <info> [sleep-monitor] system is about to suspend Oct 24 02:37:36 Telcontar sudo[20578]: pam_unix(sudo:session): session closed for user root Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session Oct 24 02:37:36 Telcontar sudo[20578]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:36 Telcontar leafnode[19718]: <QUIT Oct 24 02:37:36 Telcontar leafnode[19718]: >205 Always happy to serve! Oct 24 02:37:36 Telcontar dovecot[3429]: [redacted] Oct 24 02:37:36 Telcontar systemd[1]: Reached target Sleep. Oct 24 02:37:36 Telcontar systemd[1]: Starting Hibernate... Oct 24 02:37:36 Telcontar systemd-sleep[20599]: INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate Oct 24 02:37:36 Telcontar systemd-sleep[20599]: INFO: Running prepare-grub .. Oct 24 02:37:36 Telcontar mine-time[20608]: Inside /usr/lib/systemd/system-sleep/mine-time. Params -pre--hibernate-. Oct 24 02:37:36 Telcontar mine-sleep[20609]: Hibernating the system now (pre)... Oct 24 02:37:36 Telcontar systemd-sleep[20606]: service: no such service upsd.service Oct 24 02:37:37 Telcontar systemd-sleep[20599]: running kernel is grub menu entry main-os (vmlinuz-5.14.21-150500.55.83-default) Oct 24 02:37:37 Telcontar systemd-sleep[20599]: preparing boot-loader: selecting entry main-os, kernel /boot/5.14.21-150500.55.83-default Oct 24 02:37:37 Telcontar systemd-sleep[20599]: running /usr/sbin/grub2-once "main-os" Oct 24 02:37:37 Telcontar systemd-sleep[20599]: time needed for sync: 0.0 seconds, time needed for grub: 0.2 seconds. Oct 24 02:37:37 Telcontar systemd-sleep[20599]: INFO: Done. Oct 24 02:37:39 Telcontar xinetd[3425]: EXIT: nntp status=0 duration=392(sec) Oct 24 02:37:39 Telcontar sudo[21410]: root : TTY=pts/43 ; PWD=/root ; USER=root ; COMMAND=/usr/local/sbin/beep Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:39 Telcontar sudo[21410]: pam_unix(sudo:session): session opened for user root by (uid=0) Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. Oct 24 02:37:39 Telcontar sudo[21410]: pam_unix(sudo:session): session closed for user root Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session Oct 24 02:37:39 Telcontar sudo[21410]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Oct 24 02:37:41 Telcontar systemd-sleep[20593]: Entering sleep state 'hibernate'... Oct 24 02:37:41 Telcontar kernel: PM: hibernation: hibernation entry -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1232650] Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 https://bugzilla.suse.com/show_bug.cgi?id=1232650#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- Could you check with "nomodeset" boot option and try suspend/resume? This will disable the native graphics and uses EFI framebuffer, so the graphics might be broken after resume. But it's interesting to see whether the resume finishes without AMDGPU or it still hangs somewhere. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232650] Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 https://bugzilla.suse.com/show_bug.cgi?id=1232650#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Is AMDGPU issue with 6.12 kernel? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232650] Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 https://bugzilla.suse.com/show_bug.cgi?id=1232650#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Interesting. It means that it can be some race condition; with no_console_suspend, some resume procedure is delayed, and it starts working. In anyway, you can check some basic debug info: https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1232650] Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 https://bugzilla.suse.com/show_bug.cgi?id=1232650#c9 --- Comment #9 from Takashi Iwai <tiwai(a)suse.com> --- On 6.11 and 6.12, how is the resume behavior exactly? LED flashing changed? e.g. it's rather blinking? If it's blinking, it might indicate a kernel panic, and we have a chance to catch the crash via kdump. Try to install and setup kdump. -- You are receiving this mail because: You are the assignee for the bug.

1 0