December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1213757] New: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi
by bugzilla_noreply＠suse.com 20 Feb '24

20 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213757 Bug ID: 1213757 Summary: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: Other Status: NEW Severity: Major 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: --- Created attachment 868483 --> https://bugzilla.suse.com/attachment.cgi?id=868483&action=edit strace of hanging "ip a" The issue appears a few (~5) minutes after hostapd is started. Jul 28 12:47:40 openqa-piworker systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Jul 28 12:47:40 openqa-piworker hostapd[15307]: Configuration file: /etc/hostapd.conf Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered disabled state Jul 28 12:47:40 openqa-piworker kernel: device wlan0 entered promiscuous mode Jul 28 12:47:40 openqa-piworker hostapd[15307]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=0 pid=730 comm="/usr/sbin/wickedd --systemd --foreground ") Jul 28 12:47:41 openqa-piworker systemd[1]: Starting WPA Supplicant daemon... Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jul 28 12:47:41 openqa-piworker systemd[1]: Started WPA Supplicant daemon. Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: Could not connect to kernel driver Jul 28 12:47:45 openqa-piworker hostapd[15307]: Using interface wlan0 with hwaddr e4:5f:01:bb:63:41 and ssid "openQA-worker" Jul 28 12:47:45 openqa-piworker kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered forwarding state Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: AP-ENABLED openqa-piworker:~ # cat /etc/sysconfig/network/ifcfg-br0 IPADDR='192.168.7.1/24' BOOTPROTO='static' STARTMODE='auto' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_STP='off' BRIDGE_FORWARDDELAY='15' ZONE=dmz openqa-piworker:~ # cat /etc/hostapd.conf interface=wlan0 bridge=br0 ssid=openQA-worker wpa_passphrase=0foobar12345 driver=nl80211 country_code=DE hw_mode=g channel=7 # Bit field: bit0 = WPA, bit1 = WPA2, 3=both wpa=2 # Bit field: 1=wpa, 2=wep, 3=both auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK logger_stdout=-1 logger_stdout_level=2 openqa-piworker:~ # systemctl cat hostapd.service # /usr/lib/systemd/system/hostapd.service [Unit] Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator After=network.target [Service] ExecStart=/usr/sbin/hostapd /etc/hostapd.conf ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/hostapd.service.d/override.conf # Ensure that wlan0 is up before starting hostapd (otherwise hostapd will not add wlan0 to the bridge) [Unit] BindsTo=sys-subsystem-net-devices-wlan0.device After=sys-subsystem-net-devices-wlan0.device -- You are receiving this mail because: You are the assignee for the bug.

1 32

[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 1214049] New: USB audio dies after idle
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214049 Bug ID: 1214049 Summary: USB audio dies after idle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868666 --> https://bugzilla.suse.com/attachment.cgi?id=868666&action=edit lsusb -v output After a recent kernel update within the past week or so I have been experiencing a problem where if audio is stopped for a while it will never restart when using a USB HID audio device. In the logs I see the following: usb_set_interface failed (-19) I have swapped the cable and that made no difference. Note that if audio is constantly active it will continue to work without issues. [33346.442012] usb 7-4: New USB device found, idVendor=1852, idProduct=7022, bcdDevice= 0.01 [33346.442023] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [33346.442027] usb 7-4: Product: DigiHug USB Audio [33346.442031] usb 7-4: Manufacturer: GFEC ASSP [33346.529561] input: GFEC ASSP DigiHug USB Audio as /devices/pci0000:40/0000:40:07.1/0000:45:00.3/usb7/7-4/7-4:1.0/0003:1852:7022.001B/input/input54 [33346.586066] hid-generic 0003:1852:7022.001B: input,hidraw11: USB HID v1.00 Device [GFEC ASSP DigiHug USB Audio] on usb-0000:45:00.3-4/input0 [33360.314128] usb 3-1.3.1: reset high-speed USB device number 36 using xhci_hcd Note that the audio recovers if I unplug and reconnect the audio device. It does not matter which application is generating the audio. The USB audio device is also plugged directly into a motherboard USB port and not a hub. Desktop is running KDE factory. Kernel is 5.14.21-150400.24.74-default #1 SMP PREEMPT_DYNAMIC I have a lot of USB devices connected. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218005] New: Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 19 Jan '24

19 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218005 Bug ID: 1218005 Summary: Leap 15.5 does not boot with any of the kernel-default from update repository Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: falolaf+suse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871315 --> https://bugzilla.suse.com/attachment.cgi?id=871315&action=edit rdosreport.txt from boot attempt with kernel version 5.14.21-150500.55.36.1 I have an Acer laptop that does not boot with any of the kernel-default from update repository. The boot process ends up with: " Starting Dracut Emergency Shell… Warning: /dev/disk/by-uuid/B2C3-C97D does not exist Warning: /dev/disk/by-uuid/d733130e-1ad1-4ee3-be20-8f74d7763d88 does not exist" B2C3-C97D refers to /boot/efi in a working system. d733130e-1ad1-4ee3-be20-8f74d7763d88 refers to / in a working system. With the following kernel parameters the boot succeed: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Default kernel 5.14.21-150500.53.2 is working. E.g. kernel 5.14.21-150500.55.36.1 from update repository is NOT working. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1216799] New: Bluetooth headphones disconnect from USB bluetooth dongle
by bugzilla_noreply＠suse.com 17 Jan '24

17 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216799 Bug ID: 1216799 Summary: Bluetooth headphones disconnect from USB bluetooth dongle 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: silviu_marin-caea(a)otpbank.ro QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have bluetooth headphones (Jabra Elite 65t) and bluetooth dongle (Asus USB-BT500). They work at first but when the dongle goes into USB powersave, the headphones get disconnected and don't reconnect properly unless I reinsert the dongle. When it's all good, the headphones appear as High Fidelity Playback A2DP Sink, codec AAC. hwinfo --bluetooth 05: USB 00.1: 11500 Bluetooth Device [Created at usb.122] Unique ID: XN68.bg_nBq8ya6A Parent ID: KgLP.erpEvbsFWX1 SysFS ID: /devices/pci0000:00/0000:00:13.0/usb9/9-4/9-4:1.1 SysFS BusID: 9-4:1.1 Hardware Class: bluetooth Model: "ASUSTek ASUS USB-BT500" Hotplug: USB Vendor: usb 0x0b05 "ASUSTek Computer, Inc." Device: usb 0x190e "ASUS USB-BT500" Revision: "2.00" Serial ID: "00E04C239987" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v0B05p190Ed0200dcE0dsc01dp01icE0isc01ip01in01" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #14 (Hub) dmesg | grep Bluetooth [ 6.357471] Bluetooth: Core ver 2.22 [ 6.357495] Bluetooth: HCI device and connection manager initialized [ 6.357499] Bluetooth: HCI socket layer initialized [ 6.357502] Bluetooth: L2CAP socket layer initialized [ 6.357506] Bluetooth: SCO socket layer initialized [ 6.413147] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 6.415122] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 6.415126] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 6.439520] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.444090] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 6.715122] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 6.841248] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.841252] Bluetooth: BNEP filters: protocol multicast [ 6.841257] Bluetooth: BNEP socket layer initialized [ 6.843260] Bluetooth: MGMT ver 1.22 [ 50.972325] Bluetooth: RFCOMM TTY layer initialized [ 50.972333] Bluetooth: RFCOMM socket layer initialized [ 50.972338] Bluetooth: RFCOMM ver 1.11 ... [ 54.394435] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input19 I see this in dmesg when it reconnects and it works: [ 486.890067] usb 9-4: USB disconnect, device number 2 [ 487.114036] usb 9-4: new full-speed USB device number 3 using ohci-pci [ 487.351164] usb 9-4: New USB device found, idVendor=0b05, idProduct=190e, bcdDevice= 2.00 [ 487.351171] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 487.351173] usb 9-4: Product: ASUS USB-BT500 [ 487.351175] usb 9-4: Manufacturer: Realtek [ 487.351177] usb 9-4: SerialNumber: 00E04C239987 [ 487.358124] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 [ 487.568138] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 487.570174] Bluetooth: hci1: RTL: rom_version status=0 version=1 [ 487.570177] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 487.572606] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin [ 487.572715] Bluetooth: hci1: RTL: cfg_sz 6, total sz 30210 [ 487.842193] Bluetooth: hci1: RTL: fw version 0xdfc6d922 [ 487.944392] Bluetooth: MGMT ver 1.22 [ 493.763658] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input20 And many of these when it disconnects and doesn't work anymore: [ 852.621709] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 856.465806] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 859.097858] usb 9-4: reset full-speed USB device number 3 using ohci-pci Then this: [ 923.675107] Bluetooth: hci1: command 0x0428 tx timeout [ 963.676107] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.176409] Bluetooth: hci1: link tx timeout [ 965.176429] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.692007] Bluetooth: hci1: command 0x041f tx timeout [ 967.712098] Bluetooth: hci1: command 0x0406 tx timeout [ 968.516073] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 969.698590] Bluetooth: hci1: link tx timeout [ 969.698605] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 971.512214] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 974.560260] usb 9-4: reset full-speed USB device number 3 using ohci-pci ... [ 1080.406158] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 1082.334436] Bluetooth: hci1: command 0x0408 tx timeout [ 1082.334458] Bluetooth: hci1: No gpio to reset Realtek device, ignoring [ 1084.350582] Bluetooth: hci1: command 0x0408 tx timeout [ 1084.350603] Bluetooth: hci1: No gpio to reset Realtek device, ignoring -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217787] New: Kernel 6.6 and KDE Plasma do not work together, executing programs does not work
by bugzilla_noreply＠suse.com 08 Jan '24

08 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217787 Bug ID: 1217787 Summary: Kernel 6.6 and KDE Plasma do not work together, executing programs does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rigo(a)w3.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell latitude 7490. I have tumbleweed installed since 4 years, updated monthly. After upgrade to TW 2023-12-01, I got the following behaviour: When installing, dracut took much longer as usual and did 8 times the same module compilation/installation. The system boots until the login screen (SDDM) into the Xorg session. When logging into the KDE Plasma, the system gets stuck. Only the mouse pointer is shown on a back screen. Looking at the console, it says Failed to start powerdevil and it continues to try to start and fails. Trying to execute programs in a console terminal, the computer gets stuck and does not execute the program. Suggestion was to upgrade the Kernel. I installed OBS kernel:stable 6.6.4. The behaviour slightly changes. Now if trying to log in, the plasma screen shows the background images, but nothing else, except for the mouse pointer. Kernel 6.5.9 works fine and I can boot into my KDE session. So this is NOT a KDE issue. For the moment, I will not be able to upgrade anything and I will remain with kernel 6.5.9. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 08 Jan '24

08 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218163] New: debugging symbols missing in debug kernel
by bugzilla_noreply＠suse.com 04 Jan '24

04 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218163 Bug ID: 1218163 Summary: debugging symbols missing in debug kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin(a)dev2day.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi :) The debugging symbols are missing in the debug kernel. Steps to reproduce: ``` # update and install sudo zypper dup sudo zypper install kernel-debug # some additional information uname -a Linux opensuse-Tumbleweed-x86-64 6.6.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Dec 11 09:46:39 UTC 2023 (a946a9f) x86_64 x86_64 x86_64 GNU/Linux cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20231215" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20231215" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20231215" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ``` After the installation of `kernel-debug` a new kernel appears under `/usr/lib/modules/6.6.6-1-debug/vmlinux.xz`. Decompress the kernel with `xz -d vmlinux.xz`. Show file information about the kernel with `file vmlinux` (note this is the decompressed kernel): ``` vmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=9d90cec54c25e489b986b1c3a586c994e6b4842a, not stripped ``` `not stripped` is good but `with debug_info` is missing. Also `readelf` cannot find any information: ``` readelf --debug-dump=info vmlinux <no output here...> ``` The sections look like this: ``` readelf -S vmlinux There are 48 section headers, starting at offset 0x40779d0: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .text PROGBITS ffffffff81000000 00200000 0000000001000000 0000000000000000 AX 0 0 4096 [ 2] .rodata PROGBITS ffffffff82000000 01200000 00000000006f7006 0000000000000000 WA 0 0 4096 [ 3] .pci_fixup PROGBITS ffffffff826f7010 018f7010 0000000000003b70 0000000000000000 A 0 0 16 [ 4] .tracedata PROGBITS ffffffff826fab80 018fab80 0000000000000078 0000000000000000 A 0 0 1 [ 5] .printk_index PROGBITS ffffffff826fabf8 018fabf8 0000000000012f70 0000000000000000 WA 0 0 8 [ 6] __ksymtab PROGBITS ffffffff8270db68 0190db68 00000000000110d0 0000000000000000 A 0 0 4 [ 7] __ksymtab_gpl PROGBITS ffffffff8271ec38 0191ec38 000000000001206c 0000000000000000 A 0 0 4 [ 8] __kcrctab PROGBITS ffffffff82730ca4 01930ca4 0000000000005af0 0000000000000000 A 0 0 1 [ 9] __kcrctab_gpl PROGBITS ffffffff82736794 01936794 0000000000006024 0000000000000000 A 0 0 1 [10] __ksymtab_strings PROGBITS ffffffff8273c7b8 0193c7b8 000000000003a63b 0000000000000001 AMS 0 0 1 [11] __init_rodata PROGBITS ffffffff82776e00 01976e00 00000000000000b0 0000000000000000 A 0 0 32 [12] __param PROGBITS ffffffff82776eb0 01976eb0 00000000000031d8 0000000000000000 A 0 0 8 [13] __modver PROGBITS ffffffff8277a088 0197a088 0000000000000288 0000000000000000 WA 0 0 8 [14] __ex_table PROGBITS ffffffff8277a310 0197a310 0000000000001c20 0000000000000000 A 0 0 4 [15] .notes NOTE ffffffff8277bf30 0197bf30 00000000000001d8 0000000000000000 A 0 0 4 [16] .BTF PROGBITS ffffffff8277c108 0197c108 00000000004c7bec 0000000000000000 A 0 0 1 [17] .BTF_ids PROGBITS ffffffff82c43cf4 01e43cf4 0000000000000b00 0000000000000000 A 0 0 1 [18] .data PROGBITS ffffffff82e00000 02000000 00000000003092c0 0000000000000000 WA 0 0 8192 [19] __bug_table PROGBITS ffffffff831092c0 023092c0 000000000001c5f0 0000000000000000 WA 0 0 1 [20] .orc_header PROGBITS ffffffff831258b0 023258b0 0000000000000014 0000000000000000 A 0 0 4 [21] .orc_unwind_ip PROGBITS ffffffff831258c4 023258c4 00000000001a81f4 0000000000000000 A 0 0 1 [22] .orc_unwind PROGBITS ffffffff832cdab8 024cdab8 000000000027c2ee 0000000000000000 A 0 0 1 [23] .orc_lookup NOBITS ffffffff83549da8 02749da6 0000000000040004 0000000000000000 WA 0 0 1 [24] .vvar PROGBITS ffffffff8358a000 0278a000 0000000000001000 0000000000000000 WA 0 0 16 [25] .data..percpu PROGBITS 0000000000000000 02800000 000000000003d000 0000000000000000 WA 0 0 16384 [26] .init.text PROGBITS ffffffff835c8000 029c8000 00000000000a53e4 0000000000000000 AX 0 0 16 [27] .altinstr_aux PROGBITS ffffffff8366d3e4 02a6d3e4 00000000000035a6 0000000000000000 AX 0 0 1 [28] .init.data PROGBITS ffffffff83672000 02a72000 00000000001d6208 0000000000000000 WA 0 0 8192 [29] .x86_cpu_dev.init PROGBITS ffffffff83848208 02c48208 0000000000000028 0000000000000000 A 0 0 8 [30] .parainstructions PROGBITS ffffffff83848230 02c48230 0000000000010870 0000000000000000 A 0 0 8 [31] .retpoline_sites PROGBITS ffffffff83858aa0 02c58aa0 00000000000095f0 0000000000000000 A 0 0 1 [32] .return_sites PROGBITS ffffffff83862090 02c62090 00000000000391f4 0000000000000000 A 0 0 1 [33] .call_sites PROGBITS ffffffff8389b288 02c9b288 00000000000e9958 0000000000000000 A 0 0 1 [34] .ibt_endbr_seal PROGBITS ffffffff83984be0 02d84be0 000000000000b34c 0000000000000000 A 0 0 1 [35] .altinstructions PROGBITS ffffffff8398ff30 02d8ff30 00000000000110d6 0000000000000000 A 0 0 1 [36] .altinstr_re[...] PROGBITS ffffffff839a1006 02da1006 000000000000353a 0000000000000000 AX 0 0 1 [37] .apicdrivers PROGBITS ffffffff839a4540 02da4540 0000000000000030 0000000000000000 WA 0 0 8 [38] .exit.text PROGBITS ffffffff839a4570 02da4570 0000000000001ebb 0000000000000000 AX 0 0 16 [39] .smp_locks PROGBITS ffffffff839a7000 02da7000 000000000000a000 0000000000000000 A 0 0 4 [40] .data_nosave PROGBITS ffffffff839b1000 02db1000 0000000000001000 0000000000000000 WA 0 0 4 [41] .bss NOBITS ffffffff839b2000 02db2000 000000000044e000 0000000000000000 WA 0 0 4096 [42] .brk NOBITS ffffffff83e00000 02db2000 0000000000030000 0000000000000000 WA 0 0 1 [43] .init.scratch PROGBITS ffffffff84000000 03400000 0000000000400000 0000000000000000 WA 0 0 32 [44] .gnu_debuglink PROGBITS 0000000000000000 03800000 0000000000000014 0000000000000000 0 0 4 [45] .symtab SYMTAB 0000000000000000 03800018 0000000000501d38 0000000000000018 46 159778 8 [46] .strtab STRTAB 0000000000000000 03d01d50 0000000000375a61 0000000000000000 0 0 1 [47] .shstrtab STRTAB 0000000000000000 040777b1 000000000000021c 0000000000000000 0 0 1 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings), I (info), L (link order), O (extra OS processing required), G (group), T (TLS), C (compressed), x (unknown), o (OS specific), E (exclude), D (mbind), l (large), p (processor specific) ``` Expected result: I would like to have debug symbols when installing the `kernel-debug` package. Thanks a lot! -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218461] New: Missing bluetooth support for MediaTek MT7922 (0489:e0f2)
by bugzilla_noreply＠suse.com 31 Dec '23

31 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218461 Bug ID: 1218461 Summary: Missing bluetooth support for MediaTek MT7922 (0489:e0f2) 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: manfred99(a)gmx.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a HP Envy x360 laptop with a MediaTek 7922 network chip, with integrated Foxconn bluetooth chip 0489:e0f2. BTW, the corresponding wlan chip works fine with the mt7921e driver. When booting Leap 15.5, I get "Bluetooth: hci0: Opcode 0x c03 failed: -110". I found https://patchwork.kernel.org/project/bluetooth/patch/20221215021854.1429-1-… which exactly matches my case. For completeness, here my inxi output: #> inxi -Exxxz Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 0489:e0f2 class-ID: e001 serial: <filter> Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: N/A Could this patch be backported to Leap/SLE 15.5 ? Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218400] New: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log
by bugzilla_noreply＠suse.com 26 Dec '23

26 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218400 Bug ID: 1218400 Summary: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log 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: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_IMA_DISABLE_HTABLE is disabled except for ppc64le. I guess it should be enabled everywhere like in SLE15-SP5. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212139] New: [amdgpu]] *ERROR* ring sdma0 timeout
by bugzilla_noreply＠suse.com 24 Dec '23

24 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 Bug ID: 1212139 Summary: [amdgpu]] *ERROR* ring sdma0 timeout 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: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867453 --> https://bugzilla.suse.com/attachment.cgi?id=867453&action=edit dmesg-mohamed-mehany-steps-reproduce Linux steamdeck.lan 6.4.0-rc5-1.g2cab33e-default #1 SMP PREEMPT_DYNAMIC Sun Jun 4 20:15:10 UTC 2023 (2cab33e) x86_64 x86_64 x86_64 GNU/Linux Step to reproduce. ``` sudo -i echo "low" > /sys/class/drm/card1/device/power_dpm_force_performance_level exit sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover ``` LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230605 Codename: n/a Information for package plasma5-mobile: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : plasma5-mobile Version : 5.27.5-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 2.3 MiB Installed : Yes Status : out-of-date (version 5.27.4-1.1 installed) Source package : plasma5-mobile-5.27.5-1.1.src Upstream URL : http://www.kde.org/ Summary : Plasma Mobile Description : Plasma shell and components targeted for phones. https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_1948249 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c13 --- Comment #13 from ted chang <monkeyboyted(a)yahoo.com> --- The commit is a workaround. Not a fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c12 --- Comment #12 from ted chang <monkeyboyted(a)yahoo.com> --- Movement on the bug https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=… drm/amdgpu/sdma5.2: add begin/end_use ring callbacks commit ab4750332dbe535243def5dcebc24ca00c1f98ac upstream. Add begin/end_use ring callbacks to disallow GFXOFF when SDMA work is submitted and allow it again afterward. This should avoid corner cases where GFXOFF is erroneously entered when SDMA is still active. For now just allow/disallow GFXOFF in the begin and end helpers until we root cause the issue. This should not impact power as SDMA usage is pretty minimal and GFXOSS should not be active when SDMA is active anyway, this just makes it explicit. v2: move everything into sdma5.2 code. No reason for this to be generic at this point. v3: Add comments in new code Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2220 Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Tested-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Reviewed-by: Christian König <christian.koenig(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org # 5.15+ Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> I might close this bug since I cannot reproduce this bug myself. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c12 --- Comment #12 from Anders Stedtlund <falolaf+suse(a)gmail.com> --- Anything else I can provide to help trouble shoot this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218187] New: tumbleweed crashes very quickly after 6.6 update
by bugzilla_noreply＠suse.com 20 Dec '23

20 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218187 Bug ID: 1218187 Summary: tumbleweed crashes very quickly after 6.6 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: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed seems to crash very quickly after the 6.6 update for me. I have a bit suspicision it might be noveau. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218235] New: Built in Sreen won't wake up
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218235 Bug ID: 1218235 Summary: Built in Sreen won't wake up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mail(a)bewi.at QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello all! I’ve a problem with the wake up from screen sleep and latest kernels. When the computer screen goes to sleep it won’t wake up anymore. No mouse cursor nor i can change the tty (Strg + Alt + F1 …). The journals logs are also empty and only a hard reset helps. I’ve tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the whole computer goes to sleep (for example Sleep, Hybrid Sleep and Hibernate), and i disable Screen Sleep before, the screen wakes up. The problem exists only when the screen goes to sleep. With older kernels (i don't know the exact version) it does work. Info for my System: Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 30,1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21F80041GE System Version: ThinkPad T14s Gen 4 Maybe someone have an idea or an tip where i should submit a bug ticket. Thank you very much. Best regards! -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218231] New: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218231 Bug ID: 1218231 Summary: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I boot with these kernel options for CPU security: "mitigations=auto,nosmt mds=full,nosmt", on a laptop with Skylake i5-6200U. However, in the BIOS/UEFI options I enabled all virtualization features of this CPU. This means VT-x/VMX should be available, since Skylake supports this according to product pages. The kernel's iTLB multihit mitigation documentation does NOT suggest that any mitigation option will ever disable VT-x/VMX fully. Therefore, I would strongly expect it to be enabled on this system with this configuration. Now here comes the problem: $ lscpu | grep VMX Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled $ cat /sys/devices/system/cpu/vulnerabilities/itlb_multihit KVM: Mitigation: VMX disabled Something seems to be wrong here. As a semi naive uninformed user, I am guessing the following possible options for what happened: Option A: VMX is actually disabled by the kernel through some mitigation option. In this case this is a documentation issue, since the kernel help explaining this "KVM: Mitigation: VMX disabled" text ( https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/multihit.html ) is written like no mitigation would actively disable it, suggesting "VMX disabled" is only meant to show when the BIOS/UEFI turned it off. So the help page should then say what may mess with VMX on a kernel level beyond BIOS/UEFI. Option B: VMX is actually enabled, and the iTLB mitigation is set to "Split huge pages" (this would as far as I can tell be the "correct" option for this system). In this case, there seems to be some mostly benign iTLB info output bug. Option C: VMS is actually enabled, and the iTLB mitigation is NOT active and the device is vulnerable. This potential outcome is why I marked this as SECURITY ISSUE until it can be ruled out, since if that is true then lscpu clearly tells me I'm safe while I'm actually not. So this outcome could trick admins into making expensive hardening missteps. Option D: Maybe I'm just not smart enough to use my BIOS/UEFI, lol, or I misunderstand VMX/VT-x fundamentally. I'm not a kernel developer, after all. Vaguely related, this server fault post suggests this may also happen on many distributions: https://serverfault.com/questions/1073247/if-kvm-is-working-why-does-vmx-sh… (Not entirely sure though if it's the same cause) First seen with Fedora's 5.13.15-200.fc34.x86_64, still present with OpenSUSE slowroll's 6.5.9-1-default. Steps to reproduce: 1. Boot an Intel Skylake computer with Fedora installed. Ensure all virtualization features are enabled in the UEFI/BIOS options. 2. Once Linux has booted, change /etc/default/grub to add in "mitigations=auto,nosmt mds=full,nosmt" and update your generated grub2 files, and reboot. 3. Once inside Linux again, check "lscpu" output and /sys/devices/system/cpu/vulnerabilities/itlb_multihit output. Expected output would be something else than "VMX disabled". -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211226] Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1211226 Frederic Crozat <fcrozat(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1218184 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] enable regulator modules (REGULATOR_MT6323, REGULATOR_MT6380, MFD_MT6397)
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 https://bugzilla.suse.com/show_bug.cgi?id=1218133#c1 Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|enable regulator modules |enable regulator modules |(REGULATOR_MT6323, |(REGULATOR_MT6323, |MFD_MT6397) |REGULATOR_MT6380, | |MFD_MT6397) --- Comment #1 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- And also REGULATOR_MT6380. I think it would be better to enable them all if they can be build as modules. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218153] New: reduce SERIAL_8250_RUNTIME_UARTS?
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218153 Bug ID: 1218153 Summary: reduce SERIAL_8250_RUNTIME_UARTS? 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 Target Milestone: --- Found By: --- Blocker: --- CONFIG_SERIAL_8250_RUNTIME_UARTS is currently set to 32 which leads to 32 /dev/ttyS*. The upstream default is 4. Is there a need to pre-create that many nodes? I noticed that it clutters the `systemd-analyze blame` quite a bit when looking for boot times. Maybe reduce it back to 4? Users that really need that many ports can set 8250.nr_uarts=32 on the kernel command line as documented upstream: https://github.com/torvalds/linux/blob/master/drivers/tty/serial/8250/Kconf… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] New: Missing modules
by bugzilla_noreply＠suse.com 17 Dec '23

17 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 Bug ID: 1218133 Summary: Missing modules 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: opensuse(a)1.opensuse.bgcomp.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There are quite a number of regulator modules not being built. Some of these at least depend on the multifunction device drivers. I am looking to get tumbleweed up and running on the BananaPi-R3, and perhaps the new BananaPi-R4 in the future. This needs REGULATOR_MT6323 enabled, at least as a module, and it depend on MFD_MT6397. There seems to be an awful lot of regulators not being build, mainly because the multi function devices have not been selected. As many of these can be built as modules, can these all be enables? As in all the PMICs? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1217344] New: Linux 6.6.1 fails to boot
by bugzilla_noreply＠suse.com 16 Dec '23

16 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 Bug ID: 1217344 Summary: Linux 6.6.1 fails to boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: neronio(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The default 6.6.1 kernel installed on my Tumbleweed system does not boot. Upon selecting it in GRUB, I see: "Loading Linux 6.6.1-1-default ..." "Loading initial ramdisk ..." and the system hangs on this screen forever. My workstation's diagnostic LEDs turn on in a pattern that, according to the service manual, indicates an "other type of failure". The workstation is a Dell T5600. CPU: 2x Intel Xeon E5-2680 (v1) RAM: 8x 8 GB DDR3 1600 MHz GPU: Nvidia NVS510, I'm using nouveau drivers. My kernel cmdline: root=UUID=5136bb35-acaa-4796-b463-8c9ef307025d splash=silent quiet mitigations=auto The latest default 6.5.9 kernel works fine on this machine. I'm available for all kinds of testing/debugging, including kernel recompilation with experimental patches and the like. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1213830] New: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213830 Bug ID: 1213830 Summary: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c22 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(neronio(a)outlook.c | |om) | --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- The upstream fix commit 50d7cdf7a9b1 landed to Linus tree: efi/x86: Avoid physical KASLR on older Dell systems I'm going to backport the fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1210335 -- You are receiving this mail because: You are the assignee for the bug.

1 0