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

[kernel-bugs] [Bug 1177800] New: [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177800 Bug ID: 1177800 Summary: [Ten64] getsysinfo caused kernel error (synchronous external abort) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matt(a)traverse.com.au, snwint(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- Running `getsysinfo` (via ssh) on Tumbleweed 20201011 with kernel-default 5.9.0 from Kernel:HEAD repository caused a kernel error, with ssh getting stuck and reconnections failing. Serial login still worked. zehn:~ # getsysinfo /proc/bus/input /proc/cpuinfo /proc/device-tree /proc/devices /proc/fb /proc/filesystems /proc/interrupts /proc/iomem /proc/ioports /proc/meminfo /proc/modules /proc/net/dev /proc/partitions /proc/scsi /proc/tty /proc/version /sys /usr/sbin/getsysinfo: line 23: 2761 Segmentation fault cp -x -a --parents "$i" "$dir/$host" 2> /dev/null /var/lib/hardware/udi /proc/mounts System data written to: /tmp/zehn.tar.gz zehn:~ # [ 544.956478] Internal error: synchronous external abort: 96000210 [#1] SMP [ 544.963295] Modules linked in: af_packet ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables rfkill ip6table_filter ip6_tables iptable_filter ip_tables x_tables fsl_dpaa2_ptp ptp_qoriq fsl_dpaa2_eth phylink xgmac_mdio hid_generic fsl_mc_dpio usbhid cdc_acm i2c_mux_pca954x i2c_mux tpm_i2c_atmel spi_fsl_qspi qoriq_thermal leds_gpio optee tee uio_pdrv_genirq uio qoriq_cpufreq nls_iso8859_1 nls_cp437 vfat fat drm xhci_plat_hcd xhci_hcd usbcore caam_jr mmc_block libdes authenc caamhash_desc caamalg_desc crypto_engine rtc_ds1307 mp886x aes_ce_blk crypto_simd cryptd aes_ce_cipher crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce dpaa2_console nvme nvme_core dwc3 sdhci_of_esdhc caam sdhci_pltfm ulpi [ 544.963547] error sdhci udc_core roles mmc_core i2c_imx btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 545.066303] CPU: 0 PID: 2761 Comm: cp Not tainted 5.9.0-1.g11733e1-default #1 openSUSE Tumbleweed (unreleased) [ 545.076303] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g1d4a3d9d5c 07/28/2020 [ 545.084393] pstate: 60000085 (nZCv daIf -PAN -UAO BTYPE=--) [ 545.089967] pc : dw_pcie_read+0x48/0xc0 [ 545.093799] lr : dw_pcie_access_other_conf.isra.0+0xc4/0x120 [ 545.099452] sp : ffff800012203bf0 [ 545.102759] x29: ffff800012203bf0 x28: 0000000000000400 [ 545.108067] x27: ffff00833e683400 x26: ffff008348240000 [ 545.113375] x25: ffff800010085000 x24: 0000000000000000 [ 545.118683] x23: ffff00834b239880 x22: ffff800012203cc4 [ 545.123991] x21: 0000000000000004 x20: 0000000000000400 [ 545.129299] x19: ffff00834b2398a8 x18: 0000000000000000 [ 545.134607] x17: 0000000000000000 x16: ffffafadaf1be170 [ 545.139915] x15: 0000000000000000 x14: 0000000000000000 [ 545.145222] x13: 0000000000000000 x12: 0000000000000040 [ 545.150530] x11: ffff00834bd8c920 x10: 0000000000000000 [ 545.155837] x9 : ffffafadaf12e8f4 x8 : 0000000002080000 [ 545.161145] x7 : 0000000000000000 x6 : ffff800010f00000 [ 545.166452] x5 : 0000000000000000 x4 : 0000000000000908 [ 545.171759] x3 : 0000000000000003 x2 : ffff800012203cc4 [ 545.177066] x1 : 0000000000000004 x0 : ffff800010085400 [ 545.182374] Call trace: [ 545.184816] dw_pcie_read+0x48/0xc0 [ 545.188298] dw_pcie_rd_conf+0x11c/0x150 [ 545.192217] pci_user_read_config_dword+0xa8/0x190 [ 545.197004] pci_read_config+0x1f8/0x264 [ 545.200923] sysfs_kf_bin_read+0x78/0xa0 [ 545.204840] kernfs_file_direct_read+0x90/0x220 [ 545.209365] kernfs_fop_read+0x44/0x50 [ 545.213111] vfs_read+0xb8/0x1e4 [ 545.216334] ksys_read+0x78/0x110 [ 545.219643] __arm64_sys_read+0x28/0x34 [ 545.223476] el0_svc_common.constprop.0+0x84/0x230 [ 545.228261] do_el0_svc+0x30/0xa0 [ 545.231572] el0_svc+0x18/0x50 [ 545.234621] el0_sync_handler+0x90/0x254 [ 545.238538] el0_sync+0x158/0x180 [ 545.241849] Code: 528010e0 d50323bf b900005f d65f03c0 (b9400001) [ 545.247941] ---[ end trace 68383e7eecaae870 ]--- -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1177288] New: Raspberry pi3 (model b) crashes with network gadget
by bugzilla_noreply＠suse.com 03 Jul '22

03 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177288 Bug ID: 1177288 Summary: Raspberry pi3 (model b) crashes with network gadget 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: coolo(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com, nsaenzjulienne(a)suse.com Found By: --- Blocker: --- I use the official Leap 15.2 Jeos image on a pi3b and have a USB network device attached to it (a very special one, https://www.fibrecode.com/fc602-usb-oabr-broadr-reach-100base-t1-stick.html) and it crashes the kernel pretty reliably with the following crash dump. [ 86.184109] usb 1-1.3: USB disconnect, device number 5 [ 86.184427] cdc_ether 1-1.3:1.0 eth2: unregister 'cdc_ether' usb-3f980000.usb-1.3, CDC Ethernet Device [ 99.795717] usb 1-1.3: new high-speed USB device number 7 using dwc2 [ 99.926758] usb 1-1.3: New USB device found, idVendor=152a, idProduct=857b, bcdDevice= 2.24 [ 99.926780] usb 1-1.3: New USB device strings: Mfr=2, Product=1, SerialNumber=3 [ 99.926788] usb 1-1.3: Product: FibreCode FC602 Stick [ 99.926796] usb 1-1.3: Manufacturer: FibreCode [ 99.926804] usb 1-1.3: SerialNumber: FC01330000018a69 [ 99.930380] cdc_ether 1-1.3:1.0 eth1: register 'cdc_ether' at usb-3f980000.usb-1.3, CDC Ethernet Device, fc:c2:3d:1f:7f:ad [ 99.949857] cdc_ether 1-1.3:1.0 eth2: renamed from eth1 [ 740.880346] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 740.880360] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.461843] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 741.461858] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x06400001 [ 741.880374] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 741.880386] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04400001 [ 741.880395] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 741.880573] WARNING: CPU: 0 PID: 0 at ../drivers/usb/dwc2/hcd.c:2683 dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880578] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs vc4 drm_kms_helper drm btsdio snd_soc_core bluetooth snd_compress snd_bcm2835(C) nls_iso8859_1 ac97_bus nls_cp437 snd_pcm_dmaengine ecdh_generic snd_pcm bcm2835_v4l2(C) ecc vfat v4l2_common snd_timer fat videobuf2_vmalloc brcmfmac videobuf2_memops videobuf2_v4l2 snd videobuf2_common videodev mc brcmutil cpufreq_dt soundcore fb_sys_fops cfg80211 syscopyarea sysfillrect microchip sysimgblt rfkill ftdi_sio cdc_ether usbnet lan78xx usbserial mii raspberrypi_hwmon bcm2835_thermal raspberrypi_cpufreq vchiq(C) bcm2835_rng bcm2835_wdt crct10dif_ce uio_pdrv_genirq uio leds_gpio ext4 mbcache jbd2 mmc_block dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci bcm2835 gpio_raspberrypi_exp mmc_core clk_raspberrypi i2c_bcm2835 bcm2835_dma fixed phy_generic dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod efivarfs [ 741.880754] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C 5.3.18-lp152.36-default #1 openSUSE Leap 15.2 (unreleased) [ 741.880759] Hardware name: raspberrypi rpi/rpi, BIOS 2020.01 06/02/2020 [ 741.880765] pstate: 60000085 (nZCv daIf -PAN -UAO) [ 741.880799] pc : dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.880834] lr : dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.880838] sp : ffff000010003c60 [ 741.880842] x29: ffff000010003c60 x28: ffff3bd997683dc0 [ 741.880849] x27: ffffa6ec7c4c4000 x26: ffff3bd997679000 [ 741.880857] x25: 0000000000000008 x24: ffffa6ec7c6a55e0 [ 741.880864] x23: ffffa6ec6bbc5080 x22: ffffa6ec77d12830 [ 741.880871] x21: ffffa6ec79871600 x20: ffffa6ec7c6a5080 [ 741.880878] x19: ffffa6ec6bbc50c8 x18: ffffffffffffffff [ 741.880885] x17: 0000000000000001 x16: 0000000000000007 [ 741.880891] x15: ffff3bd997679708 x14: ffff3bd9978cfa28 [ 741.880898] x13: ffff3bd9978cf67e x12: ffff3bd9976a2000 [ 741.880905] x11: 0000000000000000 x10: ffff3bd9978ce000 [ 741.880912] x9 : 0000000000000000 x8 : 0000000000000003 [ 741.880919] x7 : 0000000000000176 x6 : ffff3bd9978cec90 [ 741.880925] x5 : 0000000000000001 x4 : ffffa6ec79871698 [ 741.880932] x3 : 0000000000000000 x2 : 00000000000005ee [ 741.880939] x1 : 0000000000000000 x0 : 0000000000000002 [ 741.880946] Call trace: [ 741.880984] dwc2_assign_and_init_hc+0x664/0xa10 [dwc2] [ 741.881018] dwc2_hcd_select_transactions+0x104/0x1a0 [dwc2] [ 741.881052] dwc2_release_channel+0xfc/0x280 [dwc2] [ 741.881087] dwc2_halt_channel+0xac/0x158 [dwc2] [ 741.881121] dwc2_hc_n_intr+0x860/0x8c0 [dwc2] [ 741.881155] dwc2_handle_hcd_intr+0x38c/0x450 [dwc2] [ 741.881188] _dwc2_hcd_irq+0x20/0x30 [dwc2] [ 741.881278] usb_hcd_irq+0x3c/0x60 [usbcore] [ 741.881291] __handle_irq_event_percpu+0x74/0x268 [ 741.881299] handle_irq_event_percpu+0x40/0x98 [ 741.881307] handle_irq_event+0x50/0xa8 [ 741.881314] handle_level_irq+0xd4/0x178 [ 741.881321] generic_handle_irq+0x34/0x50 [ 741.881332] bcm2836_chained_handle_irq+0x4c/0x70 [ 741.881339] generic_handle_irq+0x34/0x50 [ 741.881346] __handle_domain_irq+0x68/0xc0 [ 741.881354] bcm2836_arm_irqchip_handle_irq+0x78/0xe0 [ 741.881360] el1_irq+0xcc/0x180 [ 741.881369] arch_cpu_idle+0x40/0x1c0 [ 741.881377] default_idle_call+0x24/0x44 [ 741.881385] do_idle+0x1dc/0x2c0 [ 741.881392] cpu_startup_entry+0x28/0x30 [ 741.881400] rest_init+0xc4/0xd0 [ 741.881409] arch_call_rest_init+0x14/0x1c [ 741.881414] start_kernel+0x4e8/0x51c [ 741.881419] ---[ end trace 29007ab7897c5716 ]--- [ 742.880425] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown [ 742.880437] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 742.880445] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 743.880453] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown [ 743.880465] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 743.880474] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 744.880491] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown [ 744.880505] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 744.880514] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 745.880537] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 745.880549] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 745.880557] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 746.880564] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown [ 746.880576] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 746.880585] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 747.880601] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 747.880612] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 747.880621] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 748.880641] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown [ 748.880654] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600009 [ 748.880664] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 749.880675] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown [ 749.880686] dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04600001 [ 749.880695] dwc2 3f980000.usb: dwc2_update_urb_state_abn(): trimming xfer length [ 750.880718] dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 30 Jun '22

30 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1201066 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Kernel Assignee|kubic-bugs(a)opensuse.org |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199618] [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 30 Jun '22

30 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199618 https://bugzilla.suse.com/show_bug.cgi?id=1199618#c2 --- Comment #2 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-ltp-syscalls@aarch64-HD24G https://openqa.opensuse.org/tests/2440899#step/fanotify16/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 56 days if nothing changes in this ticket. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201017] New: kernel-uname-r dependency invalid
by bugzilla_noreply＠suse.com 29 Jun '22

29 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1201017 Bug ID: 1201017 Summary: kernel-uname-r dependency invalid 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mls(a)suse.com, mmarek(a)suse.com, tiwai(a)suse.com Depends on: 1001196 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1001196 +++ During build, we get warnings like [ 3723s] warning: Invalid version (double separator '-'): 4.4.21-3-default: kernel-uname-r = 4.4.21-3-default The dependency does get generated in the end, but it would be nice to get rid of the warning. This was allegedly fixed in Leap 42.2, but the bug is back with recent versions. Example from openSUSE:Factory kernel-default standard x86_64: > [ 3690s] warning: Invalid version (double separator '-'): 5.18.6-1-default > [ 3690s] warning: Invalid version (double separator '-'): 5.18.6-1-default > [ 3691s] warning: Invalid version (double separator '-'): 5.18.6-1-default It looks more scary (and less obvious) for kernel-default-base, which just copies the provides from kernel-default: > [ 45s] warning: line 44: Invalid version (double separator '-'): 5.18.6-1-default: Provides: kernel = 5.18.6-1 kernel-base = 5.18.6-1 kernel-bigsmp = 3.1 kernel-bigsmp-base = 3.1 kernel-default-base = 5.18.6-1 kernel-default-base = 5.18.6-1.1 kernel-default(x86-64) = 5.18.6-1.1 kernel-default-5.18.6-1 kernel-default-base-srchash-5aa0763ab4a847fd47695452ea91641a21b210e7 kernel-default-base-srchash-5aa0763ab4a847fd47695452ea91641a21b210e7 kernel-default_x86_64 = 5.18.6-1 kernel-desktop = 4.3 kernel-desktop-base = 4.3 kernel-ec2 = 4.4 kernel-ec2-base = 4.4 kernel-smp = 2.6.17 kernel-srchash-5aa0763ab4a847fd47695452ea91641a21b210e7 kernel-trace = 3.13 kernel-trace-base = 3.13 kernel-uname-r = 5.18.6-1-default kernel-xen = 4.4 kernel-xen-base = 4.4 multiversion(kernel) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201013] New: intel_pstate: cpu frequency is always above maximum
by bugzilla_noreply＠suse.com 29 Jun '22

29 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201013 Bug ID: 1201013 Summary: intel_pstate: cpu frequency is always above maximum Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aturan.work(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With intel_pstate driver, the cpu frequency never goes under maximum frequency but may go under turbo frequency so it is in range 2.80GHz - 3.40GHz. Intel�� Core�� i5-4200H CPU @ 2.80GHz with no kernel parameters: $ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 800 MHz - 3.40 GHz available cpufreq governors: performance powersave current policy: frequency should be within 800 MHz and 3.40 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 3.21 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes $ grep MHz /proc/cpuinfo cpu MHz : 2793.606 cpu MHz : 3058.532 cpu MHz : 2793.606 cpu MHz : 2793.606 with intel_pstate=disable: $ cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us hardware limits: 800 MHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.50 GHz, 1.40 GHz, 1.20 GHz, 1.10 GHz, 900 MHz, 800 MHz available cpufreq governors: ondemand performance schedutil current policy: frequency should be within 800 MHz and 2.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 1.03 GHz (asserted by call to kernel) boost state support: Supported: yes Active: yes $ grep MHz /proc/cpuinfo cpu MHz : 800.000 cpu MHz : 1073.813 cpu MHz : 1100.000 cpu MHz : 800.000 $ uname --kernel-release --kernel-version 5.14.21-150400.22-default #1 SMP PREEMPT_DYNAMIC Wed May 11 06:57:18 UTC 2022 (49db222) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1201012] Raspberry Pi 4: sound via HDMI not working
by bugzilla_noreply＠suse.com 29 Jun '22

29 Jun '22

1 0

[Bug 1199425] Undefined status of process hangs in system, causing other processes to hang too
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199425 http://bugzilla.opensuse.org/show_bug.cgi?id=1199425#c12 --- Comment #12 from Freek de Kruijf <freek(a)opensuse.org> --- Any progress in the analyses? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200963] New: About 1% of the time AR9485 wifi is not able to associate after wake from sleep
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200963 Bug ID: 1200963 Summary: About 1% of the time AR9485 wifi is not able to associate after wake from sleep 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: --- 03:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) Sometimes - very rarely - after wake from sleep the WiFi adapter is unable to associate with access point. Scan works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1199211] New: set buildflags exclude on kernel devel project so that branched projects have proper build disables
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199211 Bug ID: 1199211 Summary: set buildflags exclude on kernel devel project so that branched projects have proper build disables 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel:stable has an optimized build setup where the kernel-binaries flavor (kernel-default, debug and so on) are only build-enabled for the "standard"/"ports" repositories, not for the "QA repositories. This makes sense to me and is sensible to optimize rebuild performance on the build service. however, when I do branch kernel-source, a full project is replicated under my OBS home project, and that one has build flags enabled for all the repositories. So with other words the branch projects have a lot more packages to build than the main project. This is because build disables are not inheriting over branches, they get reset. After a chat with the OBS folks, these two options are there: * set a OBS:BranchSkipRepositories attribute on the project. that means that new project branches will entirely have the given repositories skipped when creating a branch. I personally think that isn't the desired behavior, as it would means things like kernel-obs-build etc are not properly tested * add a BuildFlags: excludebuild:$packagename to the prjconf. this inherits to all derived projects, also existing ones, and makes the disabled-flags setting obsolete. I have tested the following configuration successfully. There might be a script somewhere that needs to be adapted to generate this project config. otherwise I think manually maintaining it for now is fine also. %if "%_repository" == "QA" || "%_repository" == "QA_ports" || "%_repository" == "QA_ARM" || "%_repository" == "QA_PPC" || "%_repository" == "QA_RISCV" || "%_repository" == "QA_S390" BuildFlags: excludebuild:dtb-aarch64 BuildFlags: excludebuild:dtb-armv6l BuildFlags: excludebuild:dtb-armv7l BuildFlags: excludebuild:dtb-riscv64 BuildFlags: excludebuild:kernel-64kb BuildFlags: excludebuild:kernel-debug BuildFlags: excludebuild:kernel-default BuildFlags: excludebuild:kernel-docs BuildFlags: excludebuild:kernel-firmware BuildFlags: excludebuild:kernel-firmware:compressed BuildFlags: excludebuild:kernel-kvmsmall BuildFlags: excludebuild:kernel-lpae BuildFlags: excludebuild:kernel-pae BuildFlags: excludebuild:kernel-source BuildFlags: excludebuild:kernel-syms BuildFlags: excludebuild:kernel-syzkaller BuildFlags: excludebuild:kernel-vanilla BuildFlags: excludebuild:kernel-zfcpdump BuildFlags: excludebuild:pesign-obs-integration BuildFlags: excludebuild:qlogic-rules BuildFlags: excludebuild:systemtap %endif %if "%_repository" == "standard" || "%_repository" == "ports" || "%_repository" == "PPC" || "%_repository" == "RISCV" || "%_repository" == "S390" BuildFlags: excludebuild:kernel-obs-build BuildFlags: excludebuild:kernel-obs-qa %endif -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200953] New: device mapper support gone again in kernel-obs-build
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200953 Bug ID: 1200953 Summary: device mapper support gone again in kernel-obs-build 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: marcus.schaefer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I maintain a matrix of integration tests to build images in OBS. One part of the tests also builds images using device mapper features like dm-crypt or dm-raid For building such images the OBS worker environment (kernel + initrd) requires support for device mapper modules. For building in OBS the kernel-obs-build package is used. All tests were successful until an update/change of the kernel-obs-build package happened: kernel-obs-build-5.18.2-1.1 For details on the error please visit: * Encrypted image test using dm-crypt osc rbl Virtualization:Appliances:Images:Testing_x86:tumbleweed test-image-luks images x86_64 --- [ 399s] [ DEBUG ]: 13:57:17 | EXEC: [cryptsetup --key-file /var/tmp/kiwi _pt2cp3qu luksOpen /dev/mapper/loop0p3 luksRoot] [ 402s] [ 379.030150][ T4832] device-mapper: table: 254:3: crypt: Error a llocating crypto tfm (-ENOENT) --- * Software raid image test using dm-raid osc rbl Virtualization:Appliances:Images:Testing_x86:tumbleweed test-im age-raid images x86_64 --- [ 137s] modprobe: FATAL: Module md_mod not found in directory /lib/modules /5.18.2-1-default --- The image builds started to fail ~2weeks ago Would be great if this could be fixed. Thanks much -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1200950] New: systemd-vconsole-setup: /usr/bin/loadkeys failed with exit status 1.
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200950 Bug ID: 1200950 Summary: systemd-vconsole-setup: /usr/bin/loadkeys failed with exit status 1. 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: --- After installing today's snapshot 20220625 I no longer can enter the encryption password for my root partition easily, because I am left with a keyboard layout other than German. Reason seems to be: systemd-vconsole-setup[226]: /usr/bin/loadkeys failed with exit status 1. systemd[1]: Failed to start Setup Virtual Console. which appears two times during boot. systemctl start systemd-vconsole-setup in the running system works, though: systemctl status systemd-vconsole-setup �� systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static) Active: active (exited) since Sun 2022-06-26 21:46:10 CEST; 1min 24s ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Process: 1423 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS) Main PID: 1423 (code=exited, status=0/SUCCESS) CPU: 60ms -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1200951] Dracut v57 update breaks (at least) loading of keymaps during boot
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200951 https://bugzilla.suse.com/show_bug.cgi?id=1200951#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |DUPLICATE --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- . *** This bug has been marked as a duplicate of bug 1200950 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1200951] New: Dracut v57 update breaks (at least) loading of keymaps during boot
by bugzilla_noreply＠suse.com 27 Jun '22

27 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200951 Bug ID: 1200951 Summary: Dracut v57 update breaks (at least) loading of keymaps during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating to the latest tumbleweed snapshot, the boot prompt used to decrypt my LUKS root partition has switched to QWERTY, which is not my normal keyboard layout and thus makes it harder to type the password. The following log in journalctl seems like the most likely explanation... juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[682]: cannot open include file azerty-layout juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[682]: syntax error, unexpected ERROR juin 26 22:59:31 silent-graloufotron systemd-vconsole-setup[680]: /usr/bin/loadkeys failed with exit status 1. ...and indeed, if I rollback to the previous snapper snapshot and install everything but the dracut update (this still includes a minor kernel update and thus an initrd rebuild), everything is fine. So clearly the dracut update is somehow involved in this. It looks like somehow, after the dracut update, the initrd does not feature the azerty-layout keymap anymore. There might be more initrd breakage that I cannot see. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1200947] New: Error message on resume
by bugzilla_noreply＠suse.com 26 Jun '22

26 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200947 Bug ID: 1200947 Summary: Error message on resume 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: aloisio(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using a Lenovo 15ADA05 laptop, whenever I resume from suspend I see this warning on console: --- Message from syslogd@myhost at Jun 26 17:53:20 ... kernel:[ 130.733822][ C0] Uhhuh. NMI received for unknown reason 2c on CPU 0. Message from syslogd@myhost at Jun 26 17:53:20 ... kernel:[ 130.733828][ C0] Do you have a strange power saving mode enabled? Message from syslogd@myhost at Jun 26 17:53:20 ... --- I switched to the Kernel:stable:Backports image and also upgraded the bios to the latest version, without apparent change. Before Leap 15.4 I used Fedora 35 for a few months and I don't recall ever seeing this. -- You are receiving this mail because: You are the assignee for the bug.

1 0