November 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211796] New: kernel modules not usrmerged
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1211796 Bug ID: 1211796 Summary: kernel modules not usrmerged 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently kernel modules are installed through compatibility symlink, and te assumed location is in /lib. Patch kmod and kernel-binary.spec.in to not rely on this symlink. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 1210791] New: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1210791 Bug ID: 1210791 Summary: KMP builds fails with ld: cannot find arch/s390/lib/expoline/expoline.o Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ptesarik(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Out-of-tree kernel modules can no longer be built for openSUSE:Factory:zSystems. See See https://build.opensuse.org/build/Kernel:kdump/openSUSE_Factory_zSystems/s39… [ 783s] + make -C /usr/src/linux-obj/s390x/default modules M=/home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default [ 783s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.o [ 784s] MODPOST /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/Module.symvers [ 784s] CC [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.mod.o [ 784s] LD [M] /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko [ 784s] ld: cannot find arch/s390/lib/expoline/expoline.o: No such file or directory [ 784s] make[1]: *** [/usr/src/linux-6.2.12-1/scripts/Makefile.modfinal:61: /home/abuild/rpmbuild/BUILD/crash-8.0.2/kbuild/default/crash.ko] Error 1 [ 784s] make: *** [../../../linux-6.2.12-1/Makefile:1953: modules] Error 2 [ 784s] error: Bad exit status from /var/tmp/rpm-tmp.6wzRBp (%build) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1214133] New: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes
by bugzilla_noreply＠suse.com 25 Feb '24

25 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214133 Bug ID: 1214133 Summary: bluetooth disabled after update to 20230808, firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failes 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: hofmann(a)shiphrah.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868726 --> https://bugzilla.suse.com/attachment.cgi?id=868726&action=edit dmesg on TW 20230808 After update to Tumbleweed 20230808 bluetooth is disabled and can not be enabled again. dmesg | grep luetooth (on TW 20230806) [ 6.098671] Bluetooth: Core ver 2.22 [ 6.098681] Bluetooth: HCI device and connection manager initialized [ 6.098683] Bluetooth: HCI socket layer initialized [ 6.098684] Bluetooth: L2CAP socket layer initialized [ 6.098685] Bluetooth: SCO socket layer initialized [ 26.836464] Bluetooth: hci0: Device setup in 20228164 usecs [ 26.836469] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 27.115864] Bluetooth: hci0: AOSP extensions version v1.00 [ 27.115870] Bluetooth: hci0: AOSP quality report is supported dmesg | grep luetooth (on TW 20230808) [ 4.355787] Bluetooth: Core ver 2.22 [ 4.355794] Bluetooth: HCI device and connection manager initialized [ 4.355797] Bluetooth: HCI socket layer initialized [ 4.355798] Bluetooth: L2CAP socket layer initialized [ 4.355799] Bluetooth: SCO socket layer initialized [ 4.368031] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin failed with error -2 [ 4.368034] Bluetooth: hci0: Failed to load firmware file (-2) [ 4.368045] Bluetooth: hci0: Failed to set up firmware (-2) [ 4.368053] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [ 4.438485] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.438487] Bluetooth: BNEP filters: protocol multicast [ 4.438489] Bluetooth: BNEP socket layer initialized unfortunately I can not say if it was working in TW 20230807 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[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 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 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 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 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 1212839] New: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212839 Bug ID: 1212839 Summary: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LTP test cve-2021-22555 setsockopt08.c fails with ENOENT [1], but it expects EINVAL on mostly all archs on Tumbleweed (all but s390x, i.e. aarch64, ppc64le, x86_64 and x86_64 compiled as 32bit). The test has been failing for very long time (our history goes to 6.3.2 20230517, but it's failing on my VM with 6.2.12-1-default 20230502). When test run more times (200x with -i200 [3]) it fails only on first time, the rest happily have EINVAL. And indeed, when verifying manually on VM, only first run fails dmesg on affected archs contains: [ 1514.789118][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.792200][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.795209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.798209][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.801190][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.804092][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.807159][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.810210][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.813257][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 [ 1514.816227][T28992] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 But when running manually I see on first (failing): [ 208.455124] bpfilter: Loaded bpfilter_umh pid 1223 [ 208.456650] Started bpfilter (this is also in openQA jobs, but earlier, triggered by setsockopt03.c, which runs earlier). And x_tables run is reported on later (successful run): [ 221.292549] x_tables: ip_tables: state.0 match: invalid size 8 (kernel) != (user) 776 => Maybe there is a problem with loading x_tables on these 3 archs Interestingly x_tables is loaded on all archs, including s390x (which does not fail) and the same dmesg [4] FYI we stop and disable firewall in openQA install_ltp job (this qcow is then used for LTP tests) [5]: systemctl --no-pager disable firewalld Removed "/etc/systemd/system/multi-user.target.wants/firewalld.service". Removed "/etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service". systemctl --no-pager stop firewalld [1] https://openqa.opensuse.org/tests/3390125#step/setsockopt08/7 [2] https://github.com/linux-test-project/ltp/blob/a564d3e1672e9cd7ac302d597ffa… [3] https://openqa.opensuse.org/tests/3391862#step/cve-2021-22555/7 [4] https://openqa.opensuse.org/tests/3380876/file/shutdown_ltp-dmesg.txt [5] https://openqa.opensuse.org/tests/3391842/file/serial_terminal.txt -- You are receiving this mail because: You are the assignee for the bug.

1 11