June 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1200306] New: USB Mouse responds poorly when high bandwidth used by USB Ethernet adapter
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200306 Bug ID: 1200306 Summary: USB Mouse responds poorly when high bandwidth used by USB Ethernet adapter Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: php4fan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reproduce: - plug a usb ethernet adapter and connect to an Etherent LAN - plug a USB mouse (in my case, a wireless one) - stream video, download something heavy, or do a speedtest at speedtest.net or similar, and move the mouse meanwhile Expected: the mouse should always respond smoothly no matter what Observed: when network bandwidth usage is high, the mouse responds sluggishly This actually looks like the initial symptoms of bug 1184817 (which I had stopped observing and assumed was fixed), although for now I'm only experiencing mouse unsersponsiveness and not the whole system falling apart. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1200989] New: system crash on simultaneous power-on of two monitors
by bugzilla_noreply＠suse.com 02 Aug '22

02 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1200989 Bug ID: 1200989 Summary: system crash on simultaneous power-on of two monitors Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I had this already with 15.3, now tried again with 15.4 ... I have this PN50 with two monitors attached, it is always on but I power off the monitors in the evening and turn them on when I get to the system in the morning. If I turn on one monitor, wait for a picture and then turn on the second one, all is fine. If I turn on both at the same time the system freezes completely, does not even ping anymore. AMD Ryzen 7 4800U, AMD Renoir GPU, 2 LG 27 UHD monitors. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1200584] New: Alien:Isolation crashes to desktop after upgrade to 5.17.9
by bugzilla_noreply＠suse.com 01 Aug '22

01 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200584 Bug ID: 1200584 Summary: Alien:Isolation crashes to desktop after upgrade to 5.17.9 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: Michael.Zapf(a)mizapf.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859634 --> http://bugzilla.opensuse.org/attachment.cgi?id=859634&action=edit snapper status Alien:Isolation (game ported by Feral, run in Steam) crashes to desktop after some seconds in the game. Console output says segmentation fault, but no other helpful information. The crash occurs since the upgrade to 5.17.9 on 2022-05-24. The previous release that still works (verified by booting as a snapshot) is 5.17.7 of 2022-05-16. Later releases (5.18.x) are also affected. I attach a snapper status output between the last working and the first non-working release as available on my computer. My apologies if this bug tracker is not appropriate for this issue. As always, issues of this kind are difficult to report; you don't even know where to report first: distributor, video drivers, game, ... -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1200647] New: TW 20220614: MT7921K (RZ608) Wi-Fi (14c3:0608) fails to initialize with "probe of 0000:06:00.0 failed with error -5"
by bugzilla_noreply＠suse.com 27 Jul '22

27 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200647 Bug ID: 1200647 Summary: TW 20220614: MT7921K (RZ608) Wi-Fi (14c3:0608) fails to initialize with "probe of 0000:06:00.0 failed with error -5" 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: develop7(a)develop7.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Repro: 1. Have a MediaTek's MT7921K (RZ608) wireless adapter (onboard in my case) 2. Boot openSUSE Tumbleweed Expected: the wireless adapter gets picked up because it's recognized by a kernel since 5.17 Instead: the adapter fails to initialize, citing following kernel log messages (filtered): ``` Fri 2022-06-17 10:44:55.928623 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2aba0;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=68a5b1;t=5e1a0c4c6bb2f;x=ef38ece4e198f878] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 PRIORITY=6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel _KERNEL_SUBSYSTEM=pci _KERNEL_DEVICE=+pci:0000:06:00.0 _UDEV_SYSNAME=0000:06:00.0 MESSAGE=mt7921e 0000:06:00.0: enabling device (0000 -> 0002) _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=7014740 Fri 2022-06-17 10:44:57.120626 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2ac1b;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=7ad5f3;t=5e1a0c4d8eb72;x=6d724dccc54a1a] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel PRIORITY=3 _KERNEL_SUBSYSTEM=pci _KERNEL_DEVICE=+pci:0000:06:00.0 _UDEV_SYSNAME=0000:06:00.0 MESSAGE=mt7921e 0000:06:00.0: driver own failed _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=8206250 Fri 2022-06-17 10:44:57.120769 CEST [s=63f81405409f47938b3898fedbbf5334;i=c2ac1c;b=ef5ffbd5c3d84acf800cb529f2f9f4b9;m=7ad682;t=5e1a0c4d8ec01;x=ac1fa6e037cee22d] _MACHINE_ID=4ee51e58105a4f0da4915e69b1ba2c63 _HOSTNAME=linux-4kt6 _TRANSPORT=kernel SYSLOG_FACILITY=0 SYSLOG_IDENTIFIER=kernel PRIORITY=4 MESSAGE=mt7921e: probe of 0000:06:00.0 failed with error -5 _BOOT_ID=ef5ffbd5c3d84acf800cb529f2f9f4b9 _SOURCE_MONOTONIC_TIMESTAMP=8206256 ``` https://linux-hardware.org/?id=pci:14c3-0608-14c3-0608 proves kernel supports it already, https://linux-hardware.org/?probe=83733f81bd#d35 proves it didn't initialize for me -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1188934] New: bluetooth not automatically powered on
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1188934 Bug ID: 1188934 Summary: bluetooth not automatically powered on 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 Found By: --- Blocker: --- There is yet another way to make bluetooth devices unusable. The beluetooth adapter is by default powered off, and has to be manually powered on to be able to connect devices. [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady Failed to set power on: org.bluez.Error.Failed [DEL] Controller 00:E0:3C:87:B8:03 naga [default] [NEW] Controller 00:E0:3C:87:B8:03 naga [default] [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001112-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001800-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 00001801-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Controller 00:E0:3C:87:B8:03 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb [bluetooth]# power on [CHG] Controller 00:E0:3C:87:B8:03 Class: 0x006c010c Changing power on succeeded [CHG] Controller 00:E0:3C:87:B8:03 Powered: yes [bluetooth]# scan on Discovery started I think that it's quite clear you wanted your adapter powered on if you tried to scan for devices. The Linux kernel got automatic power management ages ago. Can't that apply to bluetooth as well? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume
by bugzilla_noreply＠suse.com 22 Jul '22

22 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1174622 Bug ID: 1174622 Summary: System not reconnecting to WLAN after suspend/resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 840122 --> https://bugzilla.suse.com/attachment.cgi?id=840122&action=edit Output of hwinfo --netcard System with NetworkManger is connected to a wifi network. After suspend and resume later, it is not able to reconnect to the same wifi network. After a reboot, system is connecting to the same wifi network without any problems. -- You are receiving this mail because: You are the assignee for the bug.

1 27

[kernel-bugs] [Bug 1174868] New: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed
by bugzilla_noreply＠suse.com 20 Jul '22

20 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174868 Bug ID: 1174868 Summary: Upgrade to LEAP 15.2 makes Thinkpad 480s sometimes completely freezes, 20°C warmer and journal is trimmed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of our machines here a Thinkpad T480s on openSUSE 15.2 kernel 5.3.18-lp152.33-default. In general this machine was upgraded from LEAP 15.1 to 15.2 and then the problems started to show. The CPU is constantly hotter while working. by 20°C. This machine now freezes sometimes completely. The machine is then - not pingable - no keyboard interaction works - lid close/open does nothng - no mouse interaction works - the notebook is really warm - When a freeze happens also a trim of the journal happens... e.g. we loose the whole journal for the day. - We SSH'ed into the machine and watched via "htop", "journal -f" and "sensors". WHen the machine freezes, there is no significant load via htop seeable, there are no interesting logs in journal and sensors shows that it is simply hotter. Interestingly, we upgraded another machine before (also a Thinkpad T480s) and this does not have any problems. We are btw on the latest firmwares using fwupdmgr. What should we try? How can we debug it? -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 1198565] New: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not.
by bugzilla_noreply＠suse.com 19 Jul '22

19 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198565 Bug ID: 1198565 Summary: 5.17.2-1-default shows ACPI BIOS Errors - 5.17.1-1-default did not. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: daniel.becker(a)quippy.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 858213 --> http://bugzilla.opensuse.org/attachment.cgi?id=858213&action=edit acpidump > acpidump.raw After latest update to kernel 5.17.2-1 today, boot shows ACPI BIOS Errors: Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Apr 18 13:33:20 ****** kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20211217/psargs-330) Apr 18 13:33:20 ****** kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20211217/psparse-529) Previous 5.17.1-1-default did not show these. I added "acpidump > acpidump.raw" to this error report. uname -a shows: Linux quippy 5.17.2-1-default #1 SMP PREEMPT Sat Apr 9 06:30:15 UTC 2022 (b49cf22) x86_64 x86_64 x86_64 GNU/Linux Does not seem to be a show stopper, but something changed and could be wrong now so someone might want to look into this. -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 1200984] New: motebook - no resume from hibernation
by bugzilla_noreply＠suse.com 18 Jul '22

18 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200984 Bug ID: 1200984 Summary: motebook - no resume from hibernation 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 Found By: --- Blocker: --- Created attachment 859873 --> https://bugzilla.suse.com/attachment.cgi?id=859873&action=edit start screen Starting with kernel versions 5.17.x I got the problem, that my notebook refuses to resume from hibernation state in about 95% of all cases. This is a Dell Inc. XPS 13 9310 2-in-1/0NVVG0, BIOS 2.8.1 running openSUSE Tumbleweed with latest snapshot. I didn't open a bug yet, because I hoped, that 5.18.x would solve the problem, but no go. I'm not sure, what diagnostic data you need, because resuming stops at several stages of the process, mostly when plymouth tries to initialize the environment, which is the last message then. There are no log entries at this point, so I took a photo of the start screen. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1199355] New: aarch64 oopses on raspberry pi4 KVM host (OBS worker)
by bugzilla_noreply＠suse.com 13 Jul '22

13 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199355 Bug ID: 1199355 Summary: aarch64 oopses on raspberry pi4 KVM host (OBS worker) 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: seife(a)novell.slipkontur.de QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com Found By: --- Blocker: --- I have two raspberry pi 4 OBS workers for packman build service running, both with 8GB RAM. One of them (configured to run one build worker with 4 jobs/7,5GB RAM) recently started crashing. First I guessed it was related to overclocking, but reducing the overclocking did not change anything. It always crashes towards the end of a rather long, big build job (kodi), with the following Oops message: [ 8891.760241] Unable to handle kernel access to user memory outside uaccess routines at virtual address 0000000000000134 [ 8891.771989] Mem abort info: [ 8891.775574] ESR = 0x96000004 [ 8891.779609] EC = 0x25: DABT (current EL), IL = 32 bits [ 8891.785850] SET = 0, FnV = 0 [ 8891.789772] EA = 0, S1PTW = 0 [ 8891.793819] FSC = 0x04: level 0 translation fault [ 8891.799591] Data abort info: [ 8891.803330] ISV = 0, ISS = 0x00000004 [ 8891.808174] CM = 0, WnR = 0 [ 8891.811900] user pgtable: 4k pages, 48-bit VAs, pgdp=000000015e6f2000 [ 8891.819194] [0000000000000134] pgd=0000000000000000, p4d=0000000000000000 [ 8891.826833] Internal error: Oops: 96000004 [#1] SMP [ 8891.832496] Modules linked in: loop tun af_packet iscsi_ibft iscsi_boot_sysfs nls_iso8859_1 xfs nls_cp437 vfat fat btsdio bluetooth libcrc32c ecdh_generic cpufreq_dt brcmfmac broadcom brcmutil bcm_phy_lib cfg80211 rfkill bcm2711_thermal raspberrypi_cpufreq iproc_rng200 genet mdio_bcm_unimac leds_gpio uio_pdrv_genirq uio nvmem_rmem efi_pstore drm fuse ip_tables x_tables ext4 mbcache jbd2 uas usb_storage xhci_pci xhci_pci_renesas xhci_hcd usbcore usb_common raspberrypi_hwmon crct10dif_ce gpio_raspberrypi_exp clk_raspberrypi bcm2835_wdt bcm2835_dma virt_dma sdhci_iproc sdhci_pltfm sdhci mmc_core gpio_regulator pcie_brcmstb phy_generic fixed sg efivarfs [ 8891.891666] CPU: 0 PID: 6193 Comm: qemu-system-aar Not tainted 5.17.4-1-default #1 openSUSE Tumbleweed 3c702964721983dd61af41a493a0755b03b09b96 [ 8891.905435] Hardware name: Unknown Unknown Product/Unknown Product, BIOS 2022.04 04/01/2022 [ 8891.914612] pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 8891.922381] pc : blk_mq_submit_bio+0x178/0x680 [ 8891.927612] lr : blk_mq_submit_bio+0x15c/0x680 [ 8891.932830] sp : ffff800009d62d90 [ 8891.936894] x29: ffff800009d62d90 x28: fffffcd369257208 x27: fffffcd369257200 [ 8891.944844] x26: ffff800009d63128 x25: 0000000000000001 x24: ffffa8dc6edaaae0 [ 8891.952793] x23: 0000000000000000 x22: ffff34da90f7c8e0 x21: ffff34da8680c1a0 [ 8891.960740] x20: ffff34da90fbf300 x19: ffff34da86849000 x18: 0000000000000003 [ 8891.968686] x17: 0000000000000001 x16: ffffa8dc6edd8840 x15: 0000000000000003 [ 8891.976631] x14: 0000000000000000 x13: 0000000000000038 x12: 0000000000000000 [ 8891.984578] x11: 0000000000000040 x10: 0000000000001b60 x9 : ffffa8dc6f0228c0 [ 8891.992526] x8 : ffff34da80917b00 x7 : 0000000000000000 x6 : 0000000000000001 [ 8892.000472] x5 : 00000000410fd080 x4 : 0000000000000000 x3 : ffff8bff0e894000 [ 8892.008419] x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000004000001 [ 8892.016366] Call trace: [ 8892.019549] blk_mq_submit_bio+0x178/0x680 [ 8892.024417] __submit_bio+0x118/0x180 [ 8892.028843] submit_bio_noacct+0x1ec/0x240 [ 8892.033707] submit_bio+0x64/0x140 [ 8892.037864] __swap_writepage+0x1b4/0x4a0 [ 8892.042641] swap_writepage+0x50/0x114 [ 8892.047150] pageout+0x104/0x340 [ 8892.051133] shrink_page_list+0x6b0/0xe84 [ 8892.055909] shrink_lruvec+0x584/0xb40 [ 8892.060419] shrink_node+0x3e8/0x774 [ 8892.064756] do_try_to_free_pages+0xec/0x580 [ 8892.069796] try_to_free_pages+0x118/0x210 [ 8892.074660] __alloc_pages+0x4a8/0xd04 [ 8892.079172] alloc_pages+0xb8/0x16c [ 8892.083425] folio_alloc+0x28/0x64 [ 8892.087583] filemap_alloc_folio+0xd8/0xf0 [ 8892.092447] page_cache_ra_unbounded+0xac/0x220 [ 8892.097751] ondemand_readahead+0x12c/0x2b0 [ 8892.102701] page_cache_async_ra+0xc4/0xe0 [ 8892.107565] filemap_get_pages+0x4b8/0x684 [ 8892.112430] filemap_read+0xc4/0x30c [ 8892.116763] generic_file_read_iter+0x114/0x1b0 [ 8892.122068] xfs_file_buffered_read+0xb4/0xe0 [xfs cbfa202397a50e39d50211b94f5332ed2c6954f4] [ 8892.131638] xfs_file_read_iter+0xa8/0x124 [xfs cbfa202397a50e39d50211b94f5332ed2c6954f4] [ 8892.140936] io_read+0xe4/0x3dc [ 8892.144834] io_issue_sqe+0x218/0x1aa0 [ 8892.149346] io_submit_sqes+0x28c/0x15f4 [ 8892.154033] __arm64_sys_io_uring_enter+0x4f0/0x76c [ 8892.159689] invoke_syscall+0x78/0x100 [ 8892.164202] el0_svc_common.constprop.0+0x180/0x184 [ 8892.169859] do_el0_svc+0x34/0x9c [ 8892.173931] el0_svc+0x30/0x100 [ 8892.177830] el0t_64_sync_handler+0xa4/0x130 [ 8892.182871] el0t_64_sync+0x1a4/0x1a8 [ 8892.187300] Code: 37c00060 72001c1f 1a9f17e1 f9400a62 (79426842) [ 8892.194187] ---[ end trace 0000000000000000 ]--- After that, I most of the time can still log in to the box via ssh, examine dmesg etc, but no writing to storage is possible anymore (sync, ... all hangs). Usually, I then reboot the box via "echo b > /proc/syrq-trigger" The raspberry pi 4 is running off a USB3-connected SATA ssd, it has a good passive-cooling case (CPU temperature always below 70�C) and the original raspberry pi USB-C power supply. Running up to date tumbleweed/ARM Another raspberry pi 4 8GB, set up tu run two workers with 2 jobs / 3,7GB each does run fine without crashes or issues. -- You are receiving this mail because: You are the assignee for the bug.

1 29