December 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1217428] New: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths
by bugzilla_noreply＠suse.com 26 Dec '24

26 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217428 Bug ID: 1217428 Summary: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/385844/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: luca.boccassi(a)gmail.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: thomas.leroy(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Side-channel proofing PKCS#1 1.5 paths (Marvin) Ref: https://github.com/latchset/pkcs11-provider/pull/308 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6258 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212947] New: Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 19 Dec '24

19 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212947 Bug ID: 1212947 Summary: Disable fbdev userspace interfaces and programs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: tzimmermann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We want to remove fbdev from kernel and userspace as far as possible. Linux 6.6 will allow us to disable fbdev's userspace interfaces, most noteably /dev/fb*. Enable this feature in the TW kernel. Framebuffer support has been an endless source of bugs. Not giving userspace access to it's internals and framebuffer memory will close a possible entry point for all sorts of malware. Please note that the framebuffer console is implemented entirely within the kernel and will not be affected by this change. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1212877] New: [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 Bug ID: 1212877 Summary: [RPi4] cannot wake up after suspend triggered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867900 --> https://bugzilla.suse.com/attachment.cgi?id=867900&action=edit yast2 logs ssh to my RPi 4 Model B, later I see following -- p200300ea3707b36b055205817bcf9853:~ # Broadcast message from root@localhost (Fri 2023-06-30 06:03:37 UTC): The system will suspend now! -- then I try to wake it up by hitting keyboard and click on mouse, nothing happened on screen. attache yast2logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216919] New: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services
by bugzilla_noreply＠suse.com 09 Dec '24

09 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1216919 Bug ID: 1216919 Summary: dkimproxy broken after upgrade to Leap 15.4/conversion to systemd services Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: All OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have upgrade to Leap 15.4 to find my dkimproxy setup broken. I noticed the following things: 1. there was one dkimproxy service, now there are two dkimproxy-in and dkimproxy-out. The new services are disabled even though the old one was enabled 2. The dkimproxy_in.service file references the /run/sysconfig/dkimproxy environment file 2a. The dkimproxy_env.sh script is supposed to create that file, but /run/sysconfig is not created at all to that script fails 2b. The dkimproxy_env.sh sets "HFQHN=$( hostname -f )" dkimproxy-in.service uses --hostname=${FQHN} While problem 1 is a one-time fix, the problems from 2 are more persistent and are ideally solved in the package. Note: systemd integration was contributed in bug #1116007 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213380] New: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213380 Bug ID: 1213380 Summary: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: samcon(a)protonmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I encountered a black screen issue while attempting to boot the openSUSE Tumbleweed ISO after the BIOS on my system. This issue specifically occurs when using a DP-HDMI video output. This problem does not arise when using the same video output with other operating systems like Leap, Fedora, and Ubuntu LTS. In those cases, I am able to get video output without any black screen problems. Steps to Reproduce: 1. Start the computer and access the BIOS. 2. Configure the boot order to prioritize booting from the openSUSE Tumbleweed ISO. 3. Save the changes and exit the BIOS. 4. The system attempts to boot from the ISO. 5. First I see the kernal or bootloader messages, then it jumps to a black screen - with waiting for source message on projector. Expected Behavior: Upon booting from the openSUSE Tumbleweed ISO, the system should display zypper installer instead of a black screen, just like other operating systems do when using the DP-HDMI video output. Additional Information: - Operating System: openSUSE Tumbleweed - Video Output: DP-HDMI - Other operating systems (Leap, Fedora, Ubuntu LTS) do not exhibit the black screen issue with the same video output. - When I connect the same system to the monitor using DP-to-DP instead of DP-to-HDMI, the video output is successfully displayed. - Have used tried with iso from few weeks back and latest Snapshot20230714-Media.iso Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1215927] New: kernel-default-6.5.4 reboots instead of resuming from suspend
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215927 Bug ID: 1215927 Summary: kernel-default-6.5.4 reboots instead of resuming from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: mrmazda(a)earthlink.net Target Milestone: --- Found By: --- Blocker: --- I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. I always suspend my computer at night (with systemctl suspend) and wake it the next morning. With the new kernel, the computer always restarts instead of resuming from suspend. The problem does not occur with the old kernel. Interestingly, the problem is reproducible only when I leave the computer suspended overnight. Simply suspending the computer and then waking it a few seconds later does not trigger the bug. hwinfo output (with the old kernel) is available in Attachment 869836 of Bug 1215826. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217314] New: [LenovoX13s] Unable to boot from USB
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217314 Bug ID: 1217314 Summary: [LenovoX13s] Unable to boot from USB 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: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: chester.lin(a)suse.com Target Milestone: --- Found By: --- Blocker: --- On the Lenovo X13s laptop, we are able to boot DVD ISO from USB and install openSUSE Tumbleweed on a 2nd USB stick, but on reboot, the system hangs after grub loaded kernel+initrd. Live images and JeOS images are not able to boot from USB either. Fedora wiki suggests to blacklist 'modprobe.blacklist=qcom_q6v5_pas' to keep the USB from being reset/renamed. [0] But this does not work in my tests. [0]: https://fedoraproject.org/wiki/Thinkpad_X13s#Rawhide_hacking -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214969] New: r8169: transmit queue 0 timed out
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1214969 Bug ID: 1214969 Summary: r8169: transmit queue 0 timed out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jbaier(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I hit a possible regression in kernel 6.4.x, it seems to me that this is a very similar (or same) issue like bsc#1106833 and similar. After some time (depending on the network usage, usually within 24 hours) the kernel panic happens and the network interface becomes unusable (in fact it probably generates some nonsense on the line as it also takes down the whole network segment). This behavior can be observed in 6.4.3-1-default, 6.4.6-1-default, 6.4.9-1-default and now in 6.4.11-1-default. The issue is not happening in 6.3.9-1-default which I am using right now as a workaround. --- zář 04 21:39:12 valiant kernel: ------------[ cut here ]------------ zář 04 21:39:12 valiant kernel: NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out 8160 ms zář 04 21:39:12 valiant kernel: WARNING: CPU: 11 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Modules linked in: tun rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device af_packet vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 nls_cp437 vfat fat snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_hda_codec_realtek snd_sof_utils snd_hda_codec_generic mt7921e snd_hda_codec_hdmi snd_soc_core mt7921_common mt76_connac_lib snd_compress intel_rapl_msr btusb mt76 snd_hda_intel snd_pcm_dmaengine intel_rapl_common btrtl snd_intel_dspcfg btbcm snd_intel_sdw_acpi snd_pci_ps btintel edac_mce_amd snd_hda_codec btmtk asus_nb_wmi eeepc_wmi mac80211 asus_wmi snd_rpl_pci_acp6x r8169 snd_hda_core snd_acp_pci battery snd_pci_acp6x kvm_amd snd_hwdep ledtrig_audio bluetooth snd_pcm libarc4 snd_pci_acp5x sparse_keymap realtek kvm joydev ecdh_generic platform_profile snd_rn_pci_acp3x snd_timer snd_acp_config mdio_devres irqbypass wmi_bmof cfg80211 pcspkr snd acpi_cpufreq snd_soc_acpi tiny_power_button efi_pstore soundcore zář 04 21:39:12 valiant kernel: k10temp libphy i2c_piix4 snd_pci_acp3x rfkill serial_multi_instantiate button fuse configfs dmi_sysfs ip_tables x_tables hid_generic usbhid dm_crypt essiv authenc trusted asn1_encoder tee amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_ttm_helper ttm drm_suballoc_helper iommu_v2 drm_buddy xhci_pci xhci_pci_renesas gpu_sched xhci_hcd aesni_intel drm_display_helper nvme crypto_simd ucsi_acpi usbcore cryptd typec_ucsi cec nvme_core roles ccp rc_core sp5100_tco typec video wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg br_netfilter bridge stp llc dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs zář 04 21:39:12 valiant kernel: CPU: 11 PID: 0 Comm: swapper/11 Tainted: G O 6.4.11-1-default #1 openSUSE Tumbleweed b71e9da2e7bdf20ad15c36d48af8b3d0ec2bfcc0 zář 04 21:39:12 valiant kernel: Hardware name: ASUSTeK COMPUTER INC. MINIPC PN52/PN52, BIOS 11800 09/07/2022 zář 04 21:39:12 valiant kernel: RIP: 0010:dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: Code: ff ff ff 48 89 df c6 05 ba 31 5d 01 01 e8 fa 38 fa ff 45 89 f8 44 89 f1 48 89 de 48 89 c2 48 c7 c7 70 16 cb a6 e8 12 d9 5e ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a180438ea0 EFLAGS: 00010282 zář 04 21:39:12 valiant kernel: RAX: 0000000000000000 RBX: ffff942ec3f90000 RCX: 0000000000000000 zář 04 21:39:12 valiant kernel: RDX: ffff943af5db4528 RSI: ffff943af5da74c0 RDI: 0000000000000300 zář 04 21:39:12 valiant kernel: RBP: ffff942ec3f904c8 R08: 0000000000000000 R09: ffffb3a180438d48 zář 04 21:39:12 valiant kernel: R10: 0000000000000003 R11: ffff943b2e0fcfe8 R12: ffff942e08ca6000 zář 04 21:39:12 valiant kernel: R13: ffff942ec3f9041c R14: 0000000000000000 R15: 0000000000001fe0 zář 04 21:39:12 valiant kernel: FS: 0000000000000000(0000) GS:ffff943af5d80000(0000) knlGS:0000000000000000 zář 04 21:39:12 valiant kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 zář 04 21:39:12 valiant kernel: CR2: 00007f1ff7fec980 CR3: 00000000bbc36000 CR4: 0000000000750ee0 zář 04 21:39:12 valiant kernel: PKRU: 55555554 zář 04 21:39:12 valiant kernel: Call Trace: zář 04 21:39:12 valiant kernel: <IRQ> zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __warn+0x81/0x130 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? report_bug+0x171/0x1a0 zář 04 21:39:12 valiant kernel: ? handle_bug+0x3c/0x80 zář 04 21:39:12 valiant kernel: ? exc_invalid_op+0x17/0x70 zář 04 21:39:12 valiant kernel: ? asm_exc_invalid_op+0x1a/0x20 zář 04 21:39:12 valiant kernel: ? dev_watchdog+0x21e/0x230 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: ? __pfx_dev_watchdog+0x10/0x10 zář 04 21:39:12 valiant kernel: call_timer_fn+0x27/0x130 zář 04 21:39:12 valiant kernel: __run_timers.part.0+0x1d8/0x280 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: ? ktime_get+0x3c/0xa0 zář 04 21:39:12 valiant kernel: ? __x86_return_thunk+0x9/0x10 zář 04 21:39:12 valiant kernel: run_timer_softirq+0x2a/0x50 zář 04 21:39:12 valiant kernel: __do_softirq+0xca/0x2a5 zář 04 21:39:12 valiant kernel: __irq_exit_rcu+0xae/0xe0 zář 04 21:39:12 valiant kernel: sysvec_apic_timer_interrupt+0x72/0x90 zář 04 21:39:12 valiant kernel: </IRQ> zář 04 21:39:12 valiant kernel: <TASK> zář 04 21:39:12 valiant kernel: asm_sysvec_apic_timer_interrupt+0x1a/0x20 zář 04 21:39:12 valiant kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x440 zář 04 21:39:12 valiant kernel: Code: 2a ea 47 ff e8 d5 f1 ff ff 8b 53 04 49 89 c5 0f 1f 44 00 00 31 ff e8 b3 f6 46 ff 45 84 ff 0f 85 56 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d zář 04 21:39:12 valiant kernel: RSP: 0018:ffffb3a1801d7e90 EFLAGS: 00000246 zář 04 21:39:12 valiant kernel: RAX: ffff943af5dba080 RBX: ffff942e08d7bc00 RCX: 000000000000045a zář 04 21:39:12 valiant kernel: RDX: 000000000000000b RSI: 000011088cb991b0 RDI: 0000000000000000 zář 04 21:39:12 valiant kernel: RBP: 0000000000000003 R08: ffffffffffcd2371 R09: 000000002690b399 zář 04 21:39:12 valiant kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa7632be0 zář 04 21:39:12 valiant kernel: R13: 000011088cb991b0 R14: 0000000000000003 R15: 0000000000000000 zář 04 21:39:12 valiant kernel: cpuidle_enter+0x2d/0x40 zář 04 21:39:12 valiant kernel: do_idle+0x20d/0x270 zář 04 21:39:12 valiant kernel: cpu_startup_entry+0x1d/0x20 zář 04 21:39:12 valiant kernel: start_secondary+0x12e/0x150 zář 04 21:39:12 valiant kernel: secondary_startup_64_no_verify+0x10b/0x10b zář 04 21:39:12 valiant kernel: </TASK> zář 04 21:39:12 valiant kernel: ---[ end trace 0000000000000000 ]--- --- 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 87d7 Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 12 I/O ports at f000 [size=256] Memory at fce00000 (64-bit, non-prefetchable) [size=64K] Memory at fce10000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=32 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [178] Transaction Processing Hints Capabilities: [204] Latency Tolerance Reporting Capabilities: [20c] L1 PM Substates Capabilities: [21c] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Kernel driver in use: r8169 Kernel modules: r8169 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215251] New: BTRFS: transaction aborted, forced readonly
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215251 Bug ID: 1215251 Summary: BTRFS: transaction aborted, forced readonly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My laptop hit this today (latest TW): Sep 12 11:26:53 hermes.in-addr.de kernel: ------------[ cut here ]------------ Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: Transaction aborted (error -17) Sep 12 11:26:53 hermes.in-addr.de kernel: WARNING: CPU: 3 PID: 1289 at fs/btrfs/delayed-inode.c:1158 __btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Modules linked in: tun ccm michael_mic snd_seq_dummy snd_hrtimer snd_seq af_packet algif_hash af_alg r8153_ecm cdc_ether usbnet r8152 mii snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_seq_device nft_masq nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat iscsi_ibft iscsi_boot_sysfs nf_tables 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 cdc_acm ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr_mhi uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 videobuf2_common bnep binfmt_misc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel Sep 12 11:26:53 hermes.in-addr.de kernel: soundwire_cadence snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda nls_iso8859_1 snd_hda_ext_core snd_soc_acpi_intel_match nls_cp437 snd_soc_acpi soundwire_generic_allocation soundwire_bus vfat xxhash_generic fat snd_soc_core qrtr snd_compress snd_pcm_dmaengine ath11k_pci hid_multitouch ath11k spi_nor snd_hda_intel iTCO_wdt snd_intel_dspcfg snd_intel_sdw_acpi mtd x86_pkg_temp_thermal intel_pmc_bxt intel_powerclamp iTCO_vendor_support qmi_helpers mei_pxp snd_hda_codec dell_laptop coretemp pmt_telemetry mei_hdcp kvm_intel snd_hda_core intel_rapl_msr pmt_class dell_smm_hwmon snd_hwdep hci_uart mac80211 btqca dell_wmi snd_pcm kvm btrtl btbcm snd_timer dell_smbios pcspkr efi_pstore btintel irqbypass dcdbas libarc4 dell_wmi_ddv cfg80211 bluetooth dell_wmi_sysman ledtrig_audio dell_wmi_descriptor firmware_attributes_class wmi_bmof snd processor_thermal_device_pci_legacy i2c_i801 spi_intel_pci processor_thermal_device hid_sensor_als spi_intel Sep 12 11:26:53 hermes.in-addr.de kernel: i2c_smbus mhi soundcore hid_sensor_trigger tiny_power_button processor_thermal_rfim mei_me hid_sensor_iio_common processor_thermal_mbox industrialio_triggered_buffer processor_thermal_rapl kfifo_buf thunderbolt mei intel_rapl_common industrialio intel_lpss_pci ecdh_generic intel_vsec intel_lpss intel_soc_dts_iosf igen6_edac idma64 int3403_thermal button rfkill int340x_thermal_zone intel_skl_int3472_tps68470 intel_hid tps68470_regulator intel_skl_int3472_discrete int3400_thermal sparse_keymap acpi_thermal_rel intel_pmc_core acpi_tad ac acpi_pad joydev nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs dmi_sysfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee uas usb_storage hid_logitech_hidpp hid_logitech_dj typec_displayport usbhid hid_sensor_hub hid_generic intel_ishtp_hid nvme nvme_core i915 crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 i2c_algo_bit drm_buddy drm_display_helper rtsx_pci_sdmmc xhci_pci xhci_pci_renesas Sep 12 11:26:53 hermes.in-addr.de kernel: mmc_core cec xhci_hcd rc_core aesni_intel ucsi_acpi typec_ucsi intel_ish_ipc crypto_simd cryptd usbcore roles rtsx_pci intel_ishtp vmd ttm typec video battery i2c_hid_acpi i2c_hid wmi pinctrl_tigerlake serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log v4l2loopback(O) videodev mc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua br_netfilter bridge stp llc msr efivarfs Sep 12 11:26:53 hermes.in-addr.de kernel: Unloaded tainted modules: bbswitch(O):2 Sep 12 11:26:53 hermes.in-addr.de kernel: CPU: 3 PID: 1289 Comm: btrfs-transacti Tainted: G O 6.4.12-1-default #1 openSUSE Tumbleweed 90d5a85b7d5cd5540ea49c35d1d7246e55e75794 Sep 12 11:26:53 hermes.in-addr.de kernel: Hardware name: Dell Inc. XPS 13 9310/0F7M4C, BIOS 3.17.0 07/12/2023 Sep 12 11:26:53 hermes.in-addr.de kernel: RIP: 0010:__btrfs_run_delayed_items+0x27d/0x290 [btrfs] Sep 12 11:26:53 hermes.in-addr.de kernel: Code: e9 49 fe ff ff 49 8b 7c 24 50 44 89 fa 48 c7 c6 50 f7 7a c0 e8 c4 73 04 00 eb ac 44 89 fe 48 c7 c7 20 f7 7a c0 e8 73 64 ff f9 <0f> 0b eb 99 41 bf f4 ff ff ff e9 f0 fe ff ff 0f 1f 40 00 90 90 90 Sep 12 11:26:53 hermes.in-addr.de kernel: RSP: 0018:ffffbbb60212be18 EFLAGS: 00010286 Sep 12 11:26:53 hermes.in-addr.de kernel: RAX: 0000000000000000 RBX: ffff95de205f2918 RCX: 0000000000000027 Sep 12 11:26:53 hermes.in-addr.de kernel: RDX: ffff95e32f5a74c8 RSI: 0000000000000001 RDI: ffff95e32f5a74c0 Sep 12 11:26:53 hermes.in-addr.de kernel: RBP: ffff95de205f28c0 R08: 0000000000000000 R09: ffffbbb60212bcc0 Sep 12 11:26:53 hermes.in-addr.de kernel: R10: 0000000000000003 R11: ffff95e34f7401e8 R12: ffff95dbf8902a90 Sep 12 11:26:53 hermes.in-addr.de kernel: R13: ffff95de778c1850 R14: ffff95dc00467800 R15: 00000000ffffffef Sep 12 11:26:53 hermes.in-addr.de kernel: FS: 0000000000000000(0000) GS:ffff95e32f580000(0000) knlGS:0000000000000000 Sep 12 11:26:53 hermes.in-addr.de kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 12 11:26:53 hermes.in-addr.de kernel: CR2: 00007f3e63a04960 CR3: 00000001796c4001 CR4: 0000000000f70ee0 Sep 12 11:26:53 hermes.in-addr.de kernel: PKRU: 55555554 Sep 12 11:26:53 hermes.in-addr.de kernel: Call Trace: Sep 12 11:26:53 hermes.in-addr.de kernel: <TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __warn+0x81/0x130 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? report_bug+0x171/0x1a0 Sep 12 11:26:53 hermes.in-addr.de kernel: ? handle_bug+0x3c/0x80 Sep 12 11:26:53 hermes.in-addr.de kernel: ? exc_invalid_op+0x17/0x70 Sep 12 11:26:53 hermes.in-addr.de kernel: ? asm_exc_invalid_op+0x1a/0x20 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __btrfs_run_delayed_items+0x27d/0x290 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: btrfs_commit_transaction+0x15f/0xe90 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? start_transaction+0xc5/0x5d0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: transaction_kthread+0x141/0x1b0 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_transaction_kthread+0x10/0x10 [btrfs 0cfc88295dbffd2ce4d9688602336acd1498cf39] Sep 12 11:26:53 hermes.in-addr.de kernel: kthread+0xe5/0x120 Sep 12 11:26:53 hermes.in-addr.de kernel: ? __pfx_kthread+0x10/0x10 Sep 12 11:26:53 hermes.in-addr.de kernel: ret_from_fork+0x29/0x50 Sep 12 11:26:53 hermes.in-addr.de kernel: </TASK> Sep 12 11:26:53 hermes.in-addr.de kernel: ---[ end trace 0000000000000000 ]--- Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state A) in __btrfs_run_delayed_items:1158: errno=-17 Object already exists Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS info (device dm-4: state EA): forced readonly Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS warning (device dm-4: state EA): Skipping commit of aborted transaction. Sep 12 11:26:53 hermes.in-addr.de kernel: BTRFS: error (device dm-4: state EA) in cleanup_transaction:1984: errno=-17 Object already exists Sep 12 11:27:03 hermes.in-addr.de wireplumber[18046]: could not save restore-stream: Failed to create file “/home/lmb/.local/state/wireplumber/restore-stream.EN8MB2”: Read-only file system After a subsequent reboot, btrfs check did not find any errors on the file system, and the system has been up and running since. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215665] New: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow"
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215665 Bug ID: 1215665 Summary: Lenovo ThinkPad T14s Gen 2a intermittent freezing / "your system is too slow" 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: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, said machine will randomly freeze for a marginal period of time (1-5 seconds). This is particularly noticeable while performing touch-typing, where the short freezes result in irregular text input (missing, duplicate, or infinite characters). I attempted booting with `amd_pstate=active` with no change in behavior. My desktop environment is openSUSEway (Sway/Wayland). This problem started occurring some Tumbleweed snapshots ago, though I don't recall exactly - there were other freezing issues with this hardware model before, though not in the current form where it happens consistently for short periods throughout the day. There's nothing printed in the kernel log when this happens, but the system journal is spammed with the following: ``` Sep 25 13:09:44 dreamland sway[2704]: 25:10:18.402 [ERROR] [wlr] [libinput] event5 - Microsoft Microsoft Ergonomic Mouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. Sep 25 13:10:03 dreamland sway[2704]: 25:10:36.590 [ERROR] [wlr] [libinput] event6 - Logitech K350: client bug: event processing lagging behind by 26ms, your system is too slow ``` Currently I am running: ``` $ grep ^VERSION /etc/os-release ; uname -r ; cpupower frequency-info --driver VERSION_ID="20230921" 6.5.4-1-default analyzing CPU 15: driver: amd-pstate-epp ``` Note that the behavior happens both under load and when idle, directly after rebooting. Happy to test any other constellations or provide more information as needed. I entered this in the Kernel component as there seem to have been other kernel issues with this machine in the past, however feel free to route elsewhere should this not apply here. Would appreciate any help, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 2