October 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 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 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 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

[Bug 1211117] New: 50-check-kernel-build-id fails to extract vmlinux
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1211117 Bug ID: 1211117 Summary: 50-check-kernel-build-id fails to extract vmlinux Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 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: --- When looking at build log from random stable kernel build I get this: [17308s] ... running 50-check-kernel-build-id [17309s] ... Verifying kernel build-ids for kernel-default 6.3.1-1.gdd8cfff s390x [17309s] ... Processing kernel rpms in '//home/abuild/rpmbuild/RPMS/s390x' [17909s] ... Unable to extract ./usr/lib/modules/6.3.1-1.gdd8cfff-default/vmlinux.xz from //home/abuild/rpmbuild/RPMS/s390x/kernel-default-debuginfo-6.3.1-1.1.gdd8cfff.s390x.rpm [17910s] Giving up vmlinux.xz is in kernel-default, not kernel-default-debuginfo. Either the message is misleading or the script is looking in the wrong place. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212467] New: i915 Xorg display flashing in 2k mode
by bugzilla_noreply＠suse.com 27 Nov '23

27 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1212467 Bug ID: 1212467 Summary: i915 Xorg display flashing in 2k mode 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: --- Created attachment 867636 --> https://bugzilla.suse.com/attachment.cgi?id=867636&action=edit dmesg every few seconds the display would flash I suspect buffer swap synchronization error Linux localhost.localdomain 6.3.8-lp154.2.g627a49e-default #1 SMP PREEMPT_DYNAMIC Wed Jun 14 10:30:38 UTC 2023 (627a49e) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1212169] New: drm:amdgpu_job_timeout
by bugzilla_noreply＠suse.com 18 Nov '23

18 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1212169 Bug ID: 1212169 Summary: drm:amdgpu_job_timeout 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: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867480 --> https://bugzilla.suse.com/attachment.cgi?id=867480&action=edit output of hwinfo After updating Tumbleweed to kernel 6.3.4 from 6.3.2, I encounter sporadic hangs of display: [11488.681228] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3214852, emitted seq=3214854 [11488.681693] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 3679 thread firefox:cs0 pid 3746 [11488.682121] amdgpu 0000:07:00.0: amdgpu: GPU reset begin! From what I read, KDE would have to be restarted to work again, however the original issue is probably seen before. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1212019] New: Thunderbolt USB audio disconnecting with Kernel 6.3.4
by bugzilla_noreply＠suse.com 08 Nov '23

08 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1212019 Bug ID: 1212019 Summary: Thunderbolt USB audio disconnecting with Kernel 6.3.4 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: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a laptop with a TB2 dock connected via TB3 using the TB3->TB2 Apple adapter. I'm using USB audio on this dock and since kernel 6.3.4, I get a random disconnection that can happen 1h or a few hours after boot: [Jun 5 11:25] xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 1 with no TDs queued? [ +0.033032] xhci_hcd 0000:09:00.0: WARN Event TRB for slot 1 ep 1 with no TDs queued? [ +0.906993] xhci_hcd 0000:09:00.0: xHCI host controller not responding, assume dead [ +0.000037] xhci_hcd 0000:09:00.0: HC died; cleaning up [ +0.000041] usb 3-4: USB disconnect, device number 2 When this happens and audio is playing, it stops playing via the dock and switches to my laptop speakers. Replugging the TB3 adapter usually make it work again (if audio is playing it switches automatically from speakers to TB USB audio), for a while. That setup was rock solid until updated to kernel 6.3.4. -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1216306] New: Error during Boot: SGX disabled by BIOS
by bugzilla_noreply＠suse.com 06 Nov '23

06 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216306 Bug ID: 1216306 Summary: Error during Boot: SGX disabled by BIOS 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: stefan.obermeier(a)uni-wuerzburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installation with a 202204?? version of Tumbleweed without activating the online repositories the system is booting up normally. Doing updates/Upgrades has created that error: SGX disabled by BIOS The boot process stops there. The same error with the activated online repositories during installation. I need help please -- You are receiving this mail because: You are the assignee for the bug.

1 3