December 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[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 the assignee for the bug.

1 1

[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 the assignee 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 the assignee for the bug.

1 3

[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 the assignee 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 the assignee 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 the assignee for the bug.

1 2

[kernel-bugs] Account verification
by noreply＠suse.de 18 Nov '24

18 Nov '24

Dear user opensuse-kernelbugs, we have received your email verification request. To verify your email address, please follow this link: https://idp-portal.suse.com/univention/self-service/#page=verifyaccount&tok… If the link does not work, you can go to https://idp-portal.suse.com/univention/self-service/#page=verifyaccount and enter the following token manually: vNjCDHqnMwqYa48z3RokLQTpZdp3sYBxddU7iGJR9UhboG8guN3hssVvHHxVARWo -- To unsubscribe, e-mail: kernel-bugs+unsubscribe(a)opensuse.org To contact the owner, e-mail: kernel-bugs+owner(a)opensuse.org

2 1

[kernel-bugs] [Bug 1172181] test bug for assignee change
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

http://bugzilla.suse.com/show_bug.cgi?id=1172181 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jeffm(a)suse.com |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

[Bug 1211985] New: kernel: RTNL: assertion failed at net/core/dev.c (2879)
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211985 Bug ID: 1211985 Summary: kernel: RTNL: assertion failed at net/core/dev.c (2879) 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867393 --> https://bugzilla.suse.com/attachment.cgi?id=867393&action=edit stack trace openSUSE Tumbleweed 20230601 Linux 6.3.4-1-default kernel stack trace: kernel: RTNL: assertion failed at net/core/dev.c (2879) see log There was nothing special going on, when this happened. The akonadiserver message 3 minutes before was the latest, before the crash occurred. Afterwards the igb net device was gone. After a reboot everything seems to work again. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1213139] New: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213139 Bug ID: 1213139 Summary: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3412937/modules/cons oletest_setup/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Randomly (currently every ~4th run), the test fails because systemd-vconsole-setup fails to complete. The kernel spits out an allocation failure: [ 519.853569] systemd-vconsol: vmalloc error: size 0, page order 9, failed to allocate pages, mode:0xcc2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null),cpuset=/,mems_allowed=0 [ 519.854619] CPU: 0 PID: 11361 Comm: systemd-vconsol Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 [ 519.855385] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 519.855860] Call Trace: [ 519.856047] <TASK> [ 519.856208] dump_stack_lvl+0x47/0x60 [ 519.856455] warn_alloc+0x13a/0x1b0 [ 519.856693] ? __alloc_pages+0x32d/0x350 [ 519.857009] __vmalloc_node_range+0x631/0x8b0 [ 519.857343] ? con_font_op+0x193/0x430 [ 519.857593] kvmalloc_node+0xa6/0xd0 [ 519.857857] ? con_font_op+0x193/0x430 [ 519.858105] con_font_op+0x193/0x430 [ 519.858346] ? __pfx_bpf_lsm_capable+0x10/0x10 [ 519.858631] ? security_capable+0x44/0x70 [ 519.858891] vt_ioctl+0x834/0x1380 [ 519.859126] tty_ioctl+0x4b1/0x870 [ 519.859355] __x64_sys_ioctl+0x94/0xd0 [ 519.859601] do_syscall_64+0x60/0x90 [ 519.859871] ? exc_page_fault+0x6e/0x150 [ 519.860129] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 519.860447] RIP: 0033:0x7f1144d0c2cf [ 519.860710] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 519.861757] RSP: 002b:00007ffe520b5af0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 519.862201] RAX: ffffffffffffffda RBX: 00007ffe520b5c10 RCX: 00007f1144d0c2cf [ 519.862843] RDX: 00007ffe520b5bf0 RSI: 0000000000004b72 RDI: 0000000000000003 [ 519.863463] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001 [ 519.864093] R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000008 [ 519.864705] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 519.865317] </TASK> [ 519.865681] Mem-Info: [ 519.866038] active_anon:34752 inactive_anon:94983 isolated_anon:0 active_file:120769 inactive_file:114642 isolated_file:0 unevictable:3088 dirty:1160 writeback:0 slab_reclaimable:23978 slab_unreclaimable:21653 mapped:30383 shmem:4200 pagetables:3497 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:66953 free_pcp:198 free_cma:0 [ 519.881932] Node 0 active_anon:139008kB inactive_anon:379932kB active_file:483076kB inactive_file:458568kB unevictable:12352kB isolated(anon):0kB isolated(file):0kB mapped:121532kB dirty:4640kB writeback:0kB shmem:16800kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 61440kB writeback_tmp:0kB kernel_stack:8040kB pagetables:13988kB sec_pagetables:0kB all_unreclaimable? no [ 519.893364] Node 0 DMA free:8220kB boost:0kB min:328kB low:408kB high:488kB reserved_highatomic:0KB active_anon:32kB inactive_anon:1908kB active_file:1564kB inactive_file:2136kB unevictable:0kB writepending:0kB present:15000kB managed:14364kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 519.903019] lowmem_reserve[]: 0 1889 1889 1889 1889 [ 519.905153] Node 0 DMA32 free:259592kB boost:0kB min:44724kB low:55904kB high:67084kB reserved_highatomic:16384KB active_anon:138976kB inactive_anon:378024kB active_file:481512kB inactive_file:456432kB unevictable:12352kB writepending:4640kB present:2076960kB managed:1966804kB mlocked:16kB bounce:0kB free_pcp:792kB local_pcp:792kB free_cma:0kB [ 519.915738] lowmem_reserve[]: 0 0 0 0 0 [ 519.917815] Node 0 DMA: 31*4kB (UME) 13*8kB (UME) 10*16kB (UM) 21*32kB (UME) 20*64kB (UM) 10*128kB (UME) 2*256kB (UE) 2*512kB (UE) 1*1024kB (E) 1*2048kB (E) 0*4096kB = 8228kB [ 519.920264] Node 0 DMA32: 20402*4kB (UMEH) 7366*8kB (UMEH) 2957*16kB (UMEH) 1109*32kB (UMEH) 359*64kB (UMEH) 66*128kB (UMEH) 11*256kB (MH) 4*512kB (MH) 0*1024kB 0*2048kB 0*4096kB = 259624kB [ 519.922145] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 519.923229] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 519.924415] 262294 total pagecache pages [ 519.925139] 22685 pages in swap cache [ 519.925777] Free swap = 1663652kB [ 519.926439] Total swap = 2097148kB [ 519.927082] 522990 pages RAM [ 519.927676] 0 pages HighMem/MovableOnly [ 519.928332] 27698 pages reserved [ 519.929181] 0 pages cma reserved [ 519.929828] 0 pages hwpoisoned If the system was actually out of RAM, I'd expect it to fail earlier in random places already. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_cryptlvm@uefi fails in [consoletest_setup](https://openqa.opensuse.org/tests/3412937/modules/consol… ## Test suite description Upgrade scenario with cryptlvm for Leap 15.2 Set QEMUVGA=virtio due to bsc#1210555 ## Reproducible Fails since (at least) Build [20230401](https://openqa.opensuse.org/tests/3205451) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212937] New: Kernel panic when booting up tumbleweed 20230629
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1212937 Bug ID: 1212937 Summary: Kernel panic when booting up tumbleweed 20230629 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867932 --> https://bugzilla.suse.com/attachment.cgi?id=867932&action=edit screenshot When I booted my tw system today, I ran into a kernel panic. Kernel: Linux 6.3.9-1-default Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad T14s Gen 2a The issue happened once and after a reboot I was able to boot up fine. The standby issue with the laptop hanging up on resume and eventually rebooting automatically is back again and sadly reproducible always. Not sure if that could be related. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1211380] New: Keyboard not working on laptop ASUS TUF FA507NU
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211380 Bug ID: 1211380 Summary: Keyboard not working on laptop ASUS TUF FA507NU 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: julien.colinet(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867003 --> https://bugzilla.suse.com/attachment.cgi?id=867003&action=edit lsmod output Hello, I have an issue with my laptop keyboard. The keyboard is not working, only a few keys are working, the mic mute, keyboard backlight and screen brightness. I have to use an USB keyboard for the moment. ASUS TUF A15 FA507NU AMD 7735HS nVidia RTX 4050 Keyboard vas working on Xubuntu with kernel 5.19. With kernel 6.2 it doesn't work with Xubuntu, Endeavour and Leap/Tumbleweed. I installed a newer snapshot of Tumbleweed with 6.3 kernel but it doesn't change anything. The bug is similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=217336 The keyboard is working fine under Windows 11, so for now I use my laptop on Windows but it would be great if this bug can be solved so I can use Tumbleweed -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1211352] New: ThinkPad T14s Gen 2a hangs up on s2ram resume
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1211352 Bug ID: 1211352 Summary: ThinkPad T14s Gen 2a hangs up on s2ram resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 866978 --> https://bugzilla.suse.com/attachment.cgi?id=866978&action=edit hwinfo.txt The suspend mode selector that can be set to windows or linux is set to linux via UEFI/BIOS setup. The suspend seems to work fine. The system suspends and the power led begins to flash. On resume the screen stays dark - the backlight does light up, though. It it not possible to switch to a tty. ``` cat /etc/systemd/logind.conf | grep -v '^#' [Login] HandlePowerKey=suspend HandleLidSwitch=ignore ``` -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1216851] New: kernel BUG at ../mm/slub.c:379!
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1216851 Bug ID: 1216851 Summary: kernel BUG at ../mm/slub.c:379! Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Observed today first time when doing day-to-day work with firefox on a laptop logged in as plain user. Potential dupe #1190482 [226385.604827] kernel BUG at ../mm/slub.c:379! [226385.604844] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [226385.604853] CPU: 4 PID: 765 Comm: irq/176-iwlwifi Kdump: loaded Tainted: G N 5.14.21-150400.24.88-default #1 SLE15-SP4 bd2f624c6b628ccd74aec14e859f7b291002e62d [226385.604866] Hardware name: LENOVO 20W000ATGE/20W000ATGE, BIOS N34ET53W (1.53 ) 08/31/2022 [226385.604872] RIP: 0010:__slab_free+0x2ba/0x4b0 [226385.604884] Code: 85 8e 00 00 00 45 85 c9 0f 84 b6 00 00 00 48 81 c4 88 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 49 8d 65 f0 41 5d c3 cc cc cc cc <0f> 0b 65 ff 05 fd 17 31 79 f0 49 0f ba 2c 24 00 0f 83 31 ff ff ff [226385.604894] RSP: 0018:ffffb92c80234aa0 EFLAGS: 00010246 [226385.604902] RAX: ffff9ad50daf4070 RBX: 000000008020001a RCX: ffff9ad50daf4000 [226385.604908] RDX: ffff9ad50daf4000 RSI: fffffaff0736bd00 RDI: ffff9ad49b881c00 [226385.604914] RBP: ffffb92c80234b50 R08: 0000000000000001 R09: ffffffff872564b3 [226385.604919] R10: ffff9ad4821d0840 R11: ffff9ad50daf4000 R12: fffffaff0736bd00 [226385.604924] R13: ffff9ad50daf4000 R14: ffff9ad49b881c00 R15: ffff9ad50daf4000 [226385.604930] FS: 0000000000000000(0000) GS:ffff9ad79f500000(0000) knlGS:0000000000000000 [226385.604937] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [226385.604942] CR2: 00007f4cc3e6c000 CR3: 0000000159c10006 CR4: 0000000000770ee0 [226385.604949] PKRU: 55555554 [226385.604953] Call Trace: [226385.604958] <IRQ> [226385.604966] ? iwl_mvm_tx_mpdu+0x204/0x580 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605002] ? kmem_cache_free+0x3c0/0x410 [226385.605011] ? kfree_skb_list+0x13/0x30 [226385.605021] ? kmem_cache_free+0x3c0/0x410 [226385.605029] kmem_cache_free+0x3c0/0x410 [226385.605037] kfree_skb_list+0x13/0x30 [226385.605045] ieee80211_report_used_skb+0xaf/0x490 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605098] ieee80211_tx_status_ext+0x510/0xb30 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605145] ieee80211_tx_status+0x7c/0xb0 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605192] iwl_mvm_tx_reclaim+0x376/0x3f0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605224] iwl_mvm_rx_ba_notif+0x187/0x360 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605251] iwl_mvm_rx_common+0xe3/0x2e0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605277] iwl_pcie_rx_handle+0x4db/0x8f0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605309] iwl_pcie_napi_poll_msix+0x29/0xc0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605335] __napi_poll+0x2a/0x180 [226385.605344] net_rx_action+0x24c/0x2a0 [226385.605352] __do_softirq+0xd2/0x2c0 [226385.605360] ? irq_forced_thread_fn+0x80/0x80 [226385.605371] do_softirq+0x71/0x80 [226385.605381] </IRQ> [226385.605385] <TASK> [226385.605389] __local_bh_enable_ip+0x64/0x70 [226385.605398] iwl_pcie_irq_rx_msix_handler+0xc2/0x120 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605425] irq_thread_fn+0x1e/0x60 [226385.605437] irq_thread+0xec/0x1a0 [226385.605446] ? wake_threads_waitq+0x30/0x30 [226385.605459] ? irq_thread_check_affinity+0xe0/0xe0 [226385.605468] kthread+0x154/0x180 [226385.605480] ? set_kthread_struct+0x50/0x50 [226385.605492] ret_from_fork+0x1f/0x30 [226385.605507] </TASK> [226385.605513] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp bridge stp llc cmac algif_hash algif_skcipher af_alg nf_nat_tftp nft_objref af_packet nf_conntrack_tftp nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle mhi_net(N) ip6table_raw mhi_wwan_ctrl(N) ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle bnep iptable_raw iptable_security ip_set btusb nfnetlink btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc ebtable_filter videobuf2_memops videobuf2_v4l2 videobuf2_common ebtables videodev mc ecdh_generic crc16 ip6table_filter ip6_tables iptable_filter bpfilter dmi_sysfs snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_soc_dmic iTCO_wdt intel_pmc_bxt [226385.605600] nls_iso8859_1 iTCO_vendor_support mei_hdcp(N) mfd_core nls_cp437 intel_rapl_msr snd_hda_codec_hdmi vfat snd_hda_codec_realtek fat snd_hda_codec_generic intel_tcc_cooling(N) xfs snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp iwlmvm kvm_intel soundwire_bus snd_soc_core mac80211 kvm libarc4 snd_compress irqbypass snd_pcm_dmaengine joydev think_lmi(N) mhi_pci_generic(N) efi_pstore(N) pcspkr snd_hda_intel wmi_bmof firmware_attributes_class(N) ucsi_acpi mhi(N) typec_ucsi snd_intel_dspcfg typec snd_intel_sdw_acpi roles thermal iwlwifi snd_hda_codec thinkpad_acpi snd_hda_core ledtrig_audio cfg80211 snd_hwdep platform_profile ac int3403_thermal snd_pcm processor_thermal_device_pci_legacy(N) processor_thermal_device snd_timer i2c_i801 [226385.605696] processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl mei_me e1000e intel_rapl_common snd intel_hid(N) int340x_thermal_zone sparse_keymap mei soundcore intel_pmc_core i2c_smbus rfkill acpi_tad(N) intel_soc_dts_iosf(N) int3400_thermal igen6_edac acpi_thermal_rel acpi_pad button fuse configfs ip_tables x_tables dm_crypt essiv authenc i915 crc32_pclmul i2c_algo_bit ttm ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect aesni_intel nvme xhci_pci xhci_pci_renesas xhci_hcd crypto_simd sysimgblt fb_sys_fops sdhci_pci cec rc_core cqhci cryptd sdhci drm mmc_core usbcore nvme_core serio_raw nvme_common t10_pi wmi battery video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq coretemp sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs [226385.605820] Supported: No, Unsupported modules are loaded -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218184] New: Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 21 Aug '24

21 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug ID: 1218184 Summary: Eliminate the need for 'OBS source links': convert to _multibuild Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: Dolomite Version: Milestone 5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fcrozat(a)suse.com CC: dimstar(a)opensuse.org, dleuenberger(a)suse.com, fcrozat(a)suse.com, jslaby(a)suse.com, kernel-bugs(a)opensuse.org, mls(a)suse.com, msuchanek(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com Depends on: 1211226 Target Milestone: --- Group: SUSE Enterprise Partner Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1211226 +++ In order to prepare for 'git based source management', we need to fix up a few technical issues. One such issue is 'source links' not being supported in git (i.e in OBS we have openSUSE:Factory/kernel-source as the main package plus a bunch of 'linked packages', each with the name of the additional spec files) The solution is, technically seem, rather simple: using _multibuild multibuild support on OBS is known in two variants, one using a single spec file and conditionals inside the spec file based on @BUILD_FLAVOR@ (probably the more known way) but OBS also supports 'just' listing the additional spec files as 'flavors' the _multibuild to be added to the kernel-source (main package) can be generated like this:  #!/bin/sh echo "<multibuild>" > _multibuild for pkg in *.spec; do test "{$pkg}" == "kernel-source.spec" && continue echo " <package>${pkg/.spec/}</package>" >> _multibuild; done echo "</multibuild>" >> _multibuild  the spec files do not need to be changed in anyway with this method -- You are receiving this mail because: You are on the CC list for the bug.

1 60

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 Bug ID: 1211428 Summary: Steam deck speaker is quiet. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi everyone, Steam deck speakers finally works in both speakers. Speaker-test works. However, I also notice the sound is quiet compared to SteamOS. Can you fix it? speaker-test -Dplughw:1,1 -c2 Linux steamdeck.lan 6.4.0-rc2-1.g679133f-default #1 SMP PREEMPT_DYNAMIC Sun May 14 21:09:47 UTC 2023 (679133f) x86_64 x86_64 x86_64 GNU/Linux LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230514 Codename: n/a -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 17 May '24

17 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1211975] New: freeze with flip_done time out when external monitor attached
by bugzilla_noreply＠suse.com 26 Mar '24

26 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1211975 Bug ID: 1211975 Summary: freeze with flip_done time out when external monitor attached 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: mattm3a(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Only when external monitor is attached, display freezes for a Lenovo T14. External monitor is connected via HDMI. Mean time between freeze ~1 hour. Output from terminal (CTRL+ALT+F1) looks something like this (from image, not copied in text form): [374.123930][ T1729] i915 0000:00:02.0: [drm] *ERROR* flip_done timed out [374.123938][ T1729] i915 0000:00:02.0: [drm] *ERROR* [PLANE:82:plane 1B] commit wait timed out lspci | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c) lsb-release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230531 Codename: n/a uname -srvp Linux 6.3.4-1-default #1 SMP PREEMPT_DYNAMIC Mon May 29 06:22:29 UTC 2023 (2c66b1f) x86_64 I think this issue first appeared for me in mid-May, but I'm unsure of exactly what Tumbleweed update that was. -- You are receiving this mail because: You are the assignee for the bug.

1 6

Leap 15.6 Alpha uses kernel 6.4.x which is buggy with Adaptec RAID controllers.
by Maxim 08 Mar '24

08 Mar '24

https://bugzilla.kernel.org/show_bug.cgi?id=217599 [ 7427.739081] aacraid: Host bus reset request. SCSI hang ? [ 7427.739101] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7427.739105] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7427.739107] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7427.739109] aacraid 0000:08:00.0: outstanding cmd: firmware-48 [ 7427.739111] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7427.765640] aacraid 0000:08:00.0: Controller reset type is 3 [ 7427.765652] aacraid 0000:08:00.0: Issuing IOP reset [ 7469.875692] aacraid 0000:08:00.0: IOP reset succeeded [ 7469.936116] aacraid: Comm Interface type2 enabled [ 7483.472661] aacraid 0000:08:00.0: Scheduling bus rescan [ 7496.491585] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7496.491764] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7553.768632] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768644] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768650] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768655] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768660] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768664] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.768669] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.818630] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835306] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835312] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835317] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835331] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835335] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835340] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835344] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835348] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835353] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7553.835357] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355616] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355631] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355637] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355642] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355647] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355652] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355657] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355661] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.355666] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7598.382419] aacraid: Host bus reset request. SCSI hang ? [ 7598.382439] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7598.382443] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7598.382445] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7598.382447] aacraid 0000:08:00.0: outstanding cmd: firmware-30 [ 7598.382449] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7598.402360] aacraid 0000:08:00.0: Controller reset type is 3 [ 7598.402371] aacraid 0000:08:00.0: Issuing IOP reset [ 7640.363459] aacraid 0000:08:00.0: IOP reset succeeded [ 7640.422724] aacraid: Comm Interface type2 enabled [ 7653.650105] aacraid 0000:08:00.0: Scheduling bus rescan [ 7666.688374] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7666.688467] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). [ 7814.462297] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462308] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462313] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462318] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462322] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462326] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462330] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462334] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.462338] aacraid: Host adapter abort request. aacraid: Outstanding commands on (0,0,1,0): [ 7814.478923] aacraid: Host bus reset request. SCSI hang ? [ 7814.478936] aacraid 0000:08:00.0: outstanding cmd: midlevel-0 [ 7814.478938] aacraid 0000:08:00.0: outstanding cmd: lowlevel-0 [ 7814.478940] aacraid 0000:08:00.0: outstanding cmd: error handler-0 [ 7814.478942] aacraid 0000:08:00.0: outstanding cmd: firmware-9 [ 7814.478943] aacraid 0000:08:00.0: outstanding cmd: kernel-0 [ 7814.495578] aacraid 0000:08:00.0: Controller reset type is 3 [ 7814.495587] aacraid 0000:08:00.0: Issuing IOP reset [ 7856.730598] aacraid 0000:08:00.0: IOP reset succeeded [ 7856.779371] aacraid: Comm Interface type2 enabled [ 7869.946607] aacraid 0000:08:00.0: Scheduling bus rescan [ 7882.985564] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 7882.985661] sd 0:0:1:0: [sdb] Very big device. Trying to use READ CAPACITY(16). P.S. I was not able to login to SUSE bugzillla. Login to SUSE portal does not work.

2 1

[Bug 1217748] New: Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 04 Mar '24

04 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217748 Bug ID: 1217748 Summary: Display corruption with spesific applications in Gnome-wayland session 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: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871111 --> https://bugzilla.suse.com/attachment.cgi?id=871111&action=edit sudo hwinfo >hwinfo.txt (macbook 5.1 with nvidia 9400/ core2 duo. 2008 old and rare) current build: 20231129 yast-snapper gui says my oldest snapshot is 2023-11-23 After a KDE/SDDM issue I installed a base gnome with gnome-wayland session and GDM. While most of the warnings on kernel log disappeared, couple of applications are causing massive display corruption in their work windows. gnome-terminal current and kde system monitor. They even corrupt the areas of desktop when they are moved. This is a kernel/nouveau hardware issue for sure as when I use gnome screen recording/snapshot all looks fine. Gnome developers suggested me to compile a new gnome git version which includes gtk4-terminal as opposed to current one which is a gtk3 version. I found a binary ( https://build.opensuse.org/package/show/home:mantarimay:GNOME:apps/gnome-te… ) and it is fine. I launched kde system monitor. I don't think it has anything to do with gtk3 and yet behaves same way. I am used to nouveau warnings but never seen this one: nouveau 0000:02:00.0: imem: OOM: 00100000 00001000 -2 I decided to post this bug report here as gnome-terminal from Fedora current official live USB works all fine. I have dmesg etc from it if needed. I can live without these applications however as this is a particularly rare configuration I thought I better report. I am OK with testing things. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1214073] New: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1214073 Bug ID: 1214073 Summary: [Build 20230807] kernel 6.4.8 complains about ACPI and stops loading 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: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868684 --> https://bugzilla.suse.com/attachment.cgi?id=868684&action=edit photo of screen when system frozen As the system frozen and I am in hurry, I could only take photo of screen. It says "ACPI: _SB_.PCIB. IXUE. IGPU: failed to evaluate _DSM" on the last line which was said to be a harmless effect of nvidia chipset. I am using nouveau drivers (built into kernel) and the system is macbook 5,1 I don't want to flood here with needless data, I can provide everything needed. -- You are receiving this mail because: You are the assignee for the bug.

1 10

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

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1211796 Bug ID: 1211796 Summary: kernel modules not usrmerged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently kernel modules are installed through compatibility symlink, and te assumed location is in /lib. Patch kmod and kernel-binary.spec.in to not rely on this symlink. -- You are receiving this mail because: You are the assignee for the bug.

1 22

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

27 Feb '24

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

1 17

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

25 Feb '24

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

1 2

[Bug 1213757] New: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi
by bugzilla_noreply＠suse.com 20 Feb '24

20 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213757 Bug ID: 1213757 Summary: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868483 --> https://bugzilla.suse.com/attachment.cgi?id=868483&action=edit strace of hanging "ip a" The issue appears a few (~5) minutes after hostapd is started. Jul 28 12:47:40 openqa-piworker systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Jul 28 12:47:40 openqa-piworker hostapd[15307]: Configuration file: /etc/hostapd.conf Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered disabled state Jul 28 12:47:40 openqa-piworker kernel: device wlan0 entered promiscuous mode Jul 28 12:47:40 openqa-piworker hostapd[15307]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=0 pid=730 comm="/usr/sbin/wickedd --systemd --foreground ") Jul 28 12:47:41 openqa-piworker systemd[1]: Starting WPA Supplicant daemon... Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jul 28 12:47:41 openqa-piworker systemd[1]: Started WPA Supplicant daemon. Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: Could not connect to kernel driver Jul 28 12:47:45 openqa-piworker hostapd[15307]: Using interface wlan0 with hwaddr e4:5f:01:bb:63:41 and ssid "openQA-worker" Jul 28 12:47:45 openqa-piworker kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered forwarding state Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: AP-ENABLED openqa-piworker:~ # cat /etc/sysconfig/network/ifcfg-br0 IPADDR='192.168.7.1/24' BOOTPROTO='static' STARTMODE='auto' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_STP='off' BRIDGE_FORWARDDELAY='15' ZONE=dmz openqa-piworker:~ # cat /etc/hostapd.conf interface=wlan0 bridge=br0 ssid=openQA-worker wpa_passphrase=0foobar12345 driver=nl80211 country_code=DE hw_mode=g channel=7 # Bit field: bit0 = WPA, bit1 = WPA2, 3=both wpa=2 # Bit field: 1=wpa, 2=wep, 3=both auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK logger_stdout=-1 logger_stdout_level=2 openqa-piworker:~ # systemctl cat hostapd.service # /usr/lib/systemd/system/hostapd.service [Unit] Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator After=network.target [Service] ExecStart=/usr/sbin/hostapd /etc/hostapd.conf ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/hostapd.service.d/override.conf # Ensure that wlan0 is up before starting hostapd (otherwise hostapd will not add wlan0 to the bridge) [Unit] BindsTo=sys-subsystem-net-devices-wlan0.device After=sys-subsystem-net-devices-wlan0.device -- You are receiving this mail because: You are the assignee for the bug.

1 32

[Bug 1218283] New: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218283 Bug ID: 1218283 Summary: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto 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: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fail: https://build.opensuse.org/package/live_build_log/filesystems/zfs/openSUSE_… [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end' [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin' Upstream tracks the issue here https://github.com/openzfs/zfs/issues/15401 and here https://github.com/openzfs/zfs/issues/14555 It could be fixed by reverting this kernel patch: https://github.com/torvalds/linux/commit/aaeca98456431a8d9382ecf48ac4843e25… -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1214049] New: USB audio dies after idle
by bugzilla_noreply＠suse.com 30 Jan '24

30 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214049 Bug ID: 1214049 Summary: USB audio dies after idle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868666 --> https://bugzilla.suse.com/attachment.cgi?id=868666&action=edit lsusb -v output After a recent kernel update within the past week or so I have been experiencing a problem where if audio is stopped for a while it will never restart when using a USB HID audio device. In the logs I see the following: usb_set_interface failed (-19) I have swapped the cable and that made no difference. Note that if audio is constantly active it will continue to work without issues. [33346.442012] usb 7-4: New USB device found, idVendor=1852, idProduct=7022, bcdDevice= 0.01 [33346.442023] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [33346.442027] usb 7-4: Product: DigiHug USB Audio [33346.442031] usb 7-4: Manufacturer: GFEC ASSP [33346.529561] input: GFEC ASSP DigiHug USB Audio as /devices/pci0000:40/0000:40:07.1/0000:45:00.3/usb7/7-4/7-4:1.0/0003:1852:7022.001B/input/input54 [33346.586066] hid-generic 0003:1852:7022.001B: input,hidraw11: USB HID v1.00 Device [GFEC ASSP DigiHug USB Audio] on usb-0000:45:00.3-4/input0 [33360.314128] usb 3-1.3.1: reset high-speed USB device number 36 using xhci_hcd Note that the audio recovers if I unplug and reconnect the audio device. It does not matter which application is generating the audio. The USB audio device is also plugged directly into a motherboard USB port and not a hub. Desktop is running KDE factory. Kernel is 5.14.21-150400.24.74-default #1 SMP PREEMPT_DYNAMIC I have a lot of USB devices connected. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218005] New: Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 19 Jan '24

19 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218005 Bug ID: 1218005 Summary: Leap 15.5 does not boot with any of the kernel-default from update repository Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: falolaf+suse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871315 --> https://bugzilla.suse.com/attachment.cgi?id=871315&action=edit rdosreport.txt from boot attempt with kernel version 5.14.21-150500.55.36.1 I have an Acer laptop that does not boot with any of the kernel-default from update repository. The boot process ends up with: " Starting Dracut Emergency Shell… Warning: /dev/disk/by-uuid/B2C3-C97D does not exist Warning: /dev/disk/by-uuid/d733130e-1ad1-4ee3-be20-8f74d7763d88 does not exist" B2C3-C97D refers to /boot/efi in a working system. d733130e-1ad1-4ee3-be20-8f74d7763d88 refers to / in a working system. With the following kernel parameters the boot succeed: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off Default kernel 5.14.21-150500.53.2 is working. E.g. kernel 5.14.21-150500.55.36.1 from update repository is NOT working. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1216799] New: Bluetooth headphones disconnect from USB bluetooth dongle
by bugzilla_noreply＠suse.com 17 Jan '24

17 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216799 Bug ID: 1216799 Summary: Bluetooth headphones disconnect from USB bluetooth dongle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: silviu_marin-caea(a)otpbank.ro QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have bluetooth headphones (Jabra Elite 65t) and bluetooth dongle (Asus USB-BT500). They work at first but when the dongle goes into USB powersave, the headphones get disconnected and don't reconnect properly unless I reinsert the dongle. When it's all good, the headphones appear as High Fidelity Playback A2DP Sink, codec AAC. hwinfo --bluetooth 05: USB 00.1: 11500 Bluetooth Device [Created at usb.122] Unique ID: XN68.bg_nBq8ya6A Parent ID: KgLP.erpEvbsFWX1 SysFS ID: /devices/pci0000:00/0000:00:13.0/usb9/9-4/9-4:1.1 SysFS BusID: 9-4:1.1 Hardware Class: bluetooth Model: "ASUSTek ASUS USB-BT500" Hotplug: USB Vendor: usb 0x0b05 "ASUSTek Computer, Inc." Device: usb 0x190e "ASUS USB-BT500" Revision: "2.00" Serial ID: "00E04C239987" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v0B05p190Ed0200dcE0dsc01dp01icE0isc01ip01in01" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #14 (Hub) dmesg | grep Bluetooth [ 6.357471] Bluetooth: Core ver 2.22 [ 6.357495] Bluetooth: HCI device and connection manager initialized [ 6.357499] Bluetooth: HCI socket layer initialized [ 6.357502] Bluetooth: L2CAP socket layer initialized [ 6.357506] Bluetooth: SCO socket layer initialized [ 6.413147] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 6.415122] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 6.415126] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 6.439520] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.444090] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 6.715122] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 6.841248] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.841252] Bluetooth: BNEP filters: protocol multicast [ 6.841257] Bluetooth: BNEP socket layer initialized [ 6.843260] Bluetooth: MGMT ver 1.22 [ 50.972325] Bluetooth: RFCOMM TTY layer initialized [ 50.972333] Bluetooth: RFCOMM socket layer initialized [ 50.972338] Bluetooth: RFCOMM ver 1.11 ... [ 54.394435] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input19 I see this in dmesg when it reconnects and it works: [ 486.890067] usb 9-4: USB disconnect, device number 2 [ 487.114036] usb 9-4: new full-speed USB device number 3 using ohci-pci [ 487.351164] usb 9-4: New USB device found, idVendor=0b05, idProduct=190e, bcdDevice= 2.00 [ 487.351171] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 487.351173] usb 9-4: Product: ASUS USB-BT500 [ 487.351175] usb 9-4: Manufacturer: Realtek [ 487.351177] usb 9-4: SerialNumber: 00E04C239987 [ 487.358124] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 [ 487.568138] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 487.570174] Bluetooth: hci1: RTL: rom_version status=0 version=1 [ 487.570177] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 487.572606] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin [ 487.572715] Bluetooth: hci1: RTL: cfg_sz 6, total sz 30210 [ 487.842193] Bluetooth: hci1: RTL: fw version 0xdfc6d922 [ 487.944392] Bluetooth: MGMT ver 1.22 [ 493.763658] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input20 And many of these when it disconnects and doesn't work anymore: [ 852.621709] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 856.465806] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 859.097858] usb 9-4: reset full-speed USB device number 3 using ohci-pci Then this: [ 923.675107] Bluetooth: hci1: command 0x0428 tx timeout [ 963.676107] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.176409] Bluetooth: hci1: link tx timeout [ 965.176429] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.692007] Bluetooth: hci1: command 0x041f tx timeout [ 967.712098] Bluetooth: hci1: command 0x0406 tx timeout [ 968.516073] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 969.698590] Bluetooth: hci1: link tx timeout [ 969.698605] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 971.512214] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 974.560260] usb 9-4: reset full-speed USB device number 3 using ohci-pci ... [ 1080.406158] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 1082.334436] Bluetooth: hci1: command 0x0408 tx timeout [ 1082.334458] Bluetooth: hci1: No gpio to reset Realtek device, ignoring [ 1084.350582] Bluetooth: hci1: command 0x0408 tx timeout [ 1084.350603] Bluetooth: hci1: No gpio to reset Realtek device, ignoring -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217787] New: Kernel 6.6 and KDE Plasma do not work together, executing programs does not work
by bugzilla_noreply＠suse.com 08 Jan '24

08 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217787 Bug ID: 1217787 Summary: Kernel 6.6 and KDE Plasma do not work together, executing programs does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rigo(a)w3.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell latitude 7490. I have tumbleweed installed since 4 years, updated monthly. After upgrade to TW 2023-12-01, I got the following behaviour: When installing, dracut took much longer as usual and did 8 times the same module compilation/installation. The system boots until the login screen (SDDM) into the Xorg session. When logging into the KDE Plasma, the system gets stuck. Only the mouse pointer is shown on a back screen. Looking at the console, it says Failed to start powerdevil and it continues to try to start and fails. Trying to execute programs in a console terminal, the computer gets stuck and does not execute the program. Suggestion was to upgrade the Kernel. I installed OBS kernel:stable 6.6.4. The behaviour slightly changes. Now if trying to log in, the plasma screen shows the background images, but nothing else, except for the mouse pointer. Kernel 6.5.9 works fine and I can boot into my KDE session. So this is NOT a KDE issue. For the moment, I will not be able to upgrade anything and I will remain with kernel 6.5.9. -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 08 Jan '24

08 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending 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 Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218163] New: debugging symbols missing in debug kernel
by bugzilla_noreply＠suse.com 04 Jan '24

04 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218163 Bug ID: 1218163 Summary: debugging symbols missing in debug kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: martin(a)dev2day.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi :) The debugging symbols are missing in the debug kernel. Steps to reproduce: ``` # update and install sudo zypper dup sudo zypper install kernel-debug # some additional information uname -a Linux opensuse-Tumbleweed-x86-64 6.6.6-1-default #1 SMP PREEMPT_DYNAMIC Mon Dec 11 09:46:39 UTC 2023 (a946a9f) x86_64 x86_64 x86_64 GNU/Linux cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20231215" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20231215" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20231215" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ``` After the installation of `kernel-debug` a new kernel appears under `/usr/lib/modules/6.6.6-1-debug/vmlinux.xz`. Decompress the kernel with `xz -d vmlinux.xz`. Show file information about the kernel with `file vmlinux` (note this is the decompressed kernel): ``` vmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=9d90cec54c25e489b986b1c3a586c994e6b4842a, not stripped ``` `not stripped` is good but `with debug_info` is missing. Also `readelf` cannot find any information: ``` readelf --debug-dump=info vmlinux <no output here...> ``` The sections look like this: ``` readelf -S vmlinux There are 48 section headers, starting at offset 0x40779d0: Section Headers: [Nr] Name Type Address Offset Size EntSize Flags Link Info Align [ 0] NULL 0000000000000000 00000000 0000000000000000 0000000000000000 0 0 0 [ 1] .text PROGBITS ffffffff81000000 00200000 0000000001000000 0000000000000000 AX 0 0 4096 [ 2] .rodata PROGBITS ffffffff82000000 01200000 00000000006f7006 0000000000000000 WA 0 0 4096 [ 3] .pci_fixup PROGBITS ffffffff826f7010 018f7010 0000000000003b70 0000000000000000 A 0 0 16 [ 4] .tracedata PROGBITS ffffffff826fab80 018fab80 0000000000000078 0000000000000000 A 0 0 1 [ 5] .printk_index PROGBITS ffffffff826fabf8 018fabf8 0000000000012f70 0000000000000000 WA 0 0 8 [ 6] __ksymtab PROGBITS ffffffff8270db68 0190db68 00000000000110d0 0000000000000000 A 0 0 4 [ 7] __ksymtab_gpl PROGBITS ffffffff8271ec38 0191ec38 000000000001206c 0000000000000000 A 0 0 4 [ 8] __kcrctab PROGBITS ffffffff82730ca4 01930ca4 0000000000005af0 0000000000000000 A 0 0 1 [ 9] __kcrctab_gpl PROGBITS ffffffff82736794 01936794 0000000000006024 0000000000000000 A 0 0 1 [10] __ksymtab_strings PROGBITS ffffffff8273c7b8 0193c7b8 000000000003a63b 0000000000000001 AMS 0 0 1 [11] __init_rodata PROGBITS ffffffff82776e00 01976e00 00000000000000b0 0000000000000000 A 0 0 32 [12] __param PROGBITS ffffffff82776eb0 01976eb0 00000000000031d8 0000000000000000 A 0 0 8 [13] __modver PROGBITS ffffffff8277a088 0197a088 0000000000000288 0000000000000000 WA 0 0 8 [14] __ex_table PROGBITS ffffffff8277a310 0197a310 0000000000001c20 0000000000000000 A 0 0 4 [15] .notes NOTE ffffffff8277bf30 0197bf30 00000000000001d8 0000000000000000 A 0 0 4 [16] .BTF PROGBITS ffffffff8277c108 0197c108 00000000004c7bec 0000000000000000 A 0 0 1 [17] .BTF_ids PROGBITS ffffffff82c43cf4 01e43cf4 0000000000000b00 0000000000000000 A 0 0 1 [18] .data PROGBITS ffffffff82e00000 02000000 00000000003092c0 0000000000000000 WA 0 0 8192 [19] __bug_table PROGBITS ffffffff831092c0 023092c0 000000000001c5f0 0000000000000000 WA 0 0 1 [20] .orc_header PROGBITS ffffffff831258b0 023258b0 0000000000000014 0000000000000000 A 0 0 4 [21] .orc_unwind_ip PROGBITS ffffffff831258c4 023258c4 00000000001a81f4 0000000000000000 A 0 0 1 [22] .orc_unwind PROGBITS ffffffff832cdab8 024cdab8 000000000027c2ee 0000000000000000 A 0 0 1 [23] .orc_lookup NOBITS ffffffff83549da8 02749da6 0000000000040004 0000000000000000 WA 0 0 1 [24] .vvar PROGBITS ffffffff8358a000 0278a000 0000000000001000 0000000000000000 WA 0 0 16 [25] .data..percpu PROGBITS 0000000000000000 02800000 000000000003d000 0000000000000000 WA 0 0 16384 [26] .init.text PROGBITS ffffffff835c8000 029c8000 00000000000a53e4 0000000000000000 AX 0 0 16 [27] .altinstr_aux PROGBITS ffffffff8366d3e4 02a6d3e4 00000000000035a6 0000000000000000 AX 0 0 1 [28] .init.data PROGBITS ffffffff83672000 02a72000 00000000001d6208 0000000000000000 WA 0 0 8192 [29] .x86_cpu_dev.init PROGBITS ffffffff83848208 02c48208 0000000000000028 0000000000000000 A 0 0 8 [30] .parainstructions PROGBITS ffffffff83848230 02c48230 0000000000010870 0000000000000000 A 0 0 8 [31] .retpoline_sites PROGBITS ffffffff83858aa0 02c58aa0 00000000000095f0 0000000000000000 A 0 0 1 [32] .return_sites PROGBITS ffffffff83862090 02c62090 00000000000391f4 0000000000000000 A 0 0 1 [33] .call_sites PROGBITS ffffffff8389b288 02c9b288 00000000000e9958 0000000000000000 A 0 0 1 [34] .ibt_endbr_seal PROGBITS ffffffff83984be0 02d84be0 000000000000b34c 0000000000000000 A 0 0 1 [35] .altinstructions PROGBITS ffffffff8398ff30 02d8ff30 00000000000110d6 0000000000000000 A 0 0 1 [36] .altinstr_re[...] PROGBITS ffffffff839a1006 02da1006 000000000000353a 0000000000000000 AX 0 0 1 [37] .apicdrivers PROGBITS ffffffff839a4540 02da4540 0000000000000030 0000000000000000 WA 0 0 8 [38] .exit.text PROGBITS ffffffff839a4570 02da4570 0000000000001ebb 0000000000000000 AX 0 0 16 [39] .smp_locks PROGBITS ffffffff839a7000 02da7000 000000000000a000 0000000000000000 A 0 0 4 [40] .data_nosave PROGBITS ffffffff839b1000 02db1000 0000000000001000 0000000000000000 WA 0 0 4 [41] .bss NOBITS ffffffff839b2000 02db2000 000000000044e000 0000000000000000 WA 0 0 4096 [42] .brk NOBITS ffffffff83e00000 02db2000 0000000000030000 0000000000000000 WA 0 0 1 [43] .init.scratch PROGBITS ffffffff84000000 03400000 0000000000400000 0000000000000000 WA 0 0 32 [44] .gnu_debuglink PROGBITS 0000000000000000 03800000 0000000000000014 0000000000000000 0 0 4 [45] .symtab SYMTAB 0000000000000000 03800018 0000000000501d38 0000000000000018 46 159778 8 [46] .strtab STRTAB 0000000000000000 03d01d50 0000000000375a61 0000000000000000 0 0 1 [47] .shstrtab STRTAB 0000000000000000 040777b1 000000000000021c 0000000000000000 0 0 1 Key to Flags: W (write), A (alloc), X (execute), M (merge), S (strings), I (info), L (link order), O (extra OS processing required), G (group), T (TLS), C (compressed), x (unknown), o (OS specific), E (exclude), D (mbind), l (large), p (processor specific) ``` Expected result: I would like to have debug symbols when installing the `kernel-debug` package. Thanks a lot! -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218461] New: Missing bluetooth support for MediaTek MT7922 (0489:e0f2)
by bugzilla_noreply＠suse.com 31 Dec '23

31 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218461 Bug ID: 1218461 Summary: Missing bluetooth support for MediaTek MT7922 (0489:e0f2) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred99(a)gmx.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a HP Envy x360 laptop with a MediaTek 7922 network chip, with integrated Foxconn bluetooth chip 0489:e0f2. BTW, the corresponding wlan chip works fine with the mt7921e driver. When booting Leap 15.5, I get "Bluetooth: hci0: Opcode 0x c03 failed: -110". I found https://patchwork.kernel.org/project/bluetooth/patch/20221215021854.1429-1-… which exactly matches my case. For completeness, here my inxi output: #> inxi -Exxxz Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 0489:e0f2 class-ID: e001 serial: <filter> Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: N/A Could this patch be backported to Leap/SLE 15.5 ? Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218400] New: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log
by bugzilla_noreply＠suse.com 26 Dec '23

26 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218400 Bug ID: 1218400 Summary: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log 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: schwab(a)linux-m68k.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_IMA_DISABLE_HTABLE is disabled except for ppc64le. I guess it should be enabled everywhere like in SLE15-SP5. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1212139] New: [amdgpu]] *ERROR* ring sdma0 timeout
by bugzilla_noreply＠suse.com 24 Dec '23

24 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 Bug ID: 1212139 Summary: [amdgpu]] *ERROR* ring sdma0 timeout Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867453 --> https://bugzilla.suse.com/attachment.cgi?id=867453&action=edit dmesg-mohamed-mehany-steps-reproduce Linux steamdeck.lan 6.4.0-rc5-1.g2cab33e-default #1 SMP PREEMPT_DYNAMIC Sun Jun 4 20:15:10 UTC 2023 (2cab33e) x86_64 x86_64 x86_64 GNU/Linux Step to reproduce. ``` sudo -i echo "low" > /sys/class/drm/card1/device/power_dpm_force_performance_level exit sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover ``` LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230605 Codename: n/a Information for package plasma5-mobile: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : plasma5-mobile Version : 5.27.5-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 2.3 MiB Installed : Yes Status : out-of-date (version 5.27.4-1.1 installed) Source package : plasma5-mobile-5.27.5-1.1.src Upstream URL : http://www.kde.org/ Summary : Plasma Mobile Description : Plasma shell and components targeted for phones. https://gitlab.freedesktop.org/drm/amd/-/issues/2220#note_1948249 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c13 --- Comment #13 from ted chang <monkeyboyted(a)yahoo.com> --- The commit is a workaround. Not a fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212139] [amdgpu]] *ERROR* ring sdma0 timeout 0 - Steam deck
by bugzilla_noreply＠suse.com 22 Dec '23

22 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1212139 https://bugzilla.suse.com/show_bug.cgi?id=1212139#c12 --- Comment #12 from ted chang <monkeyboyted(a)yahoo.com> --- Movement on the bug https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=… drm/amdgpu/sdma5.2: add begin/end_use ring callbacks commit ab4750332dbe535243def5dcebc24ca00c1f98ac upstream. Add begin/end_use ring callbacks to disallow GFXOFF when SDMA work is submitted and allow it again afterward. This should avoid corner cases where GFXOFF is erroneously entered when SDMA is still active. For now just allow/disallow GFXOFF in the begin and end helpers until we root cause the issue. This should not impact power as SDMA usage is pretty minimal and GFXOSS should not be active when SDMA is active anyway, this just makes it explicit. v2: move everything into sdma5.2 code. No reason for this to be generic at this point. v3: Add comments in new code Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2220 Reviewed-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Tested-by: Mario Limonciello <mario.limonciello(a)amd.com> (v1) Reviewed-by: Christian König <christian.koenig(a)amd.com> Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> Cc: stable(a)vger.kernel.org # 5.15+ Signed-off-by: Greg Kroah-Hartman <gregkh(a)linuxfoundation.org> I might close this bug since I cannot reproduce this bug myself. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c12 --- Comment #12 from Anders Stedtlund <falolaf+suse(a)gmail.com> --- Anything else I can provide to help trouble shoot this? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218187] New: tumbleweed crashes very quickly after 6.6 update
by bugzilla_noreply＠suse.com 20 Dec '23

20 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218187 Bug ID: 1218187 Summary: tumbleweed crashes very quickly after 6.6 update 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: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed seems to crash very quickly after the 6.6 update for me. I have a bit suspicision it might be noveau. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1218235] New: Built in Sreen won't wake up
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218235 Bug ID: 1218235 Summary: Built in Sreen won't wake up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mail(a)bewi.at QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello all! I’ve a problem with the wake up from screen sleep and latest kernels. When the computer screen goes to sleep it won’t wake up anymore. No mouse cursor nor i can change the tty (Strg + Alt + F1 …). The journals logs are also empty and only a hard reset helps. I’ve tested it with the lastest Linux Kernel 6.6.6 and 6.6.7. Funnily if the whole computer goes to sleep (for example Sleep, Hybrid Sleep and Hibernate), and i disable Screen Sleep before, the screen wakes up. The problem exists only when the screen goes to sleep. With older kernels (i don't know the exact version) it does work. Info for my System: Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics Memory: 30,1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 21F80041GE System Version: ThinkPad T14s Gen 4 Maybe someone have an idea or an tip where i should submit a bug ticket. Thank you very much. Best regards! -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1218231] New: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218231 Bug ID: 1218231 Summary: Hw virtualization enabled in BIOS of Intel Skylake i5-6200U, but lscpu says "VMX" disabled Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I boot with these kernel options for CPU security: "mitigations=auto,nosmt mds=full,nosmt", on a laptop with Skylake i5-6200U. However, in the BIOS/UEFI options I enabled all virtualization features of this CPU. This means VT-x/VMX should be available, since Skylake supports this according to product pages. The kernel's iTLB multihit mitigation documentation does NOT suggest that any mitigation option will ever disable VT-x/VMX fully. Therefore, I would strongly expect it to be enabled on this system with this configuration. Now here comes the problem: $ lscpu | grep VMX Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabled $ cat /sys/devices/system/cpu/vulnerabilities/itlb_multihit KVM: Mitigation: VMX disabled Something seems to be wrong here. As a semi naive uninformed user, I am guessing the following possible options for what happened: Option A: VMX is actually disabled by the kernel through some mitigation option. In this case this is a documentation issue, since the kernel help explaining this "KVM: Mitigation: VMX disabled" text ( https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/multihit.html ) is written like no mitigation would actively disable it, suggesting "VMX disabled" is only meant to show when the BIOS/UEFI turned it off. So the help page should then say what may mess with VMX on a kernel level beyond BIOS/UEFI. Option B: VMX is actually enabled, and the iTLB mitigation is set to "Split huge pages" (this would as far as I can tell be the "correct" option for this system). In this case, there seems to be some mostly benign iTLB info output bug. Option C: VMS is actually enabled, and the iTLB mitigation is NOT active and the device is vulnerable. This potential outcome is why I marked this as SECURITY ISSUE until it can be ruled out, since if that is true then lscpu clearly tells me I'm safe while I'm actually not. So this outcome could trick admins into making expensive hardening missteps. Option D: Maybe I'm just not smart enough to use my BIOS/UEFI, lol, or I misunderstand VMX/VT-x fundamentally. I'm not a kernel developer, after all. Vaguely related, this server fault post suggests this may also happen on many distributions: https://serverfault.com/questions/1073247/if-kvm-is-working-why-does-vmx-sh… (Not entirely sure though if it's the same cause) First seen with Fedora's 5.13.15-200.fc34.x86_64, still present with OpenSUSE slowroll's 6.5.9-1-default. Steps to reproduce: 1. Boot an Intel Skylake computer with Fedora installed. Ensure all virtualization features are enabled in the UEFI/BIOS options. 2. Once Linux has booted, change /etc/default/grub to add in "mitigations=auto,nosmt mds=full,nosmt" and update your generated grub2 files, and reboot. 3. Once inside Linux again, check "lscpu" output and /sys/devices/system/cpu/vulnerabilities/itlb_multihit output. Expected output would be something else than "VMX disabled". -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1211226] Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 19 Dec '23

19 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1211226 Frederic Crozat <fcrozat(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1218184 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] enable regulator modules (REGULATOR_MT6323, REGULATOR_MT6380, MFD_MT6397)
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 https://bugzilla.suse.com/show_bug.cgi?id=1218133#c1 Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|enable regulator modules |enable regulator modules |(REGULATOR_MT6323, |(REGULATOR_MT6323, |MFD_MT6397) |REGULATOR_MT6380, | |MFD_MT6397) --- Comment #1 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- And also REGULATOR_MT6380. I think it would be better to enable them all if they can be build as modules. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218153] New: reduce SERIAL_8250_RUNTIME_UARTS?
by bugzilla_noreply＠suse.com 18 Dec '23

18 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218153 Bug ID: 1218153 Summary: reduce SERIAL_8250_RUNTIME_UARTS? 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CONFIG_SERIAL_8250_RUNTIME_UARTS is currently set to 32 which leads to 32 /dev/ttyS*. The upstream default is 4. Is there a need to pre-create that many nodes? I noticed that it clutters the `systemd-analyze blame` quite a bit when looking for boot times. Maybe reduce it back to 4? Users that really need that many ports can set 8250.nr_uarts=32 on the kernel command line as documented upstream: https://github.com/torvalds/linux/blob/master/drivers/tty/serial/8250/Kconf… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218133] New: Missing modules
by bugzilla_noreply＠suse.com 17 Dec '23

17 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218133 Bug ID: 1218133 Summary: Missing modules 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: opensuse(a)1.opensuse.bgcomp.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There are quite a number of regulator modules not being built. Some of these at least depend on the multifunction device drivers. I am looking to get tumbleweed up and running on the BananaPi-R3, and perhaps the new BananaPi-R4 in the future. This needs REGULATOR_MT6323 enabled, at least as a module, and it depend on MFD_MT6397. There seems to be an awful lot of regulators not being build, mainly because the multi function devices have not been selected. As many of these can be built as modules, can these all be enables? As in all the PMICs? -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1217344] New: Linux 6.6.1 fails to boot
by bugzilla_noreply＠suse.com 16 Dec '23

16 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 Bug ID: 1217344 Summary: Linux 6.6.1 fails to boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: neronio(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The default 6.6.1 kernel installed on my Tumbleweed system does not boot. Upon selecting it in GRUB, I see: "Loading Linux 6.6.1-1-default ..." "Loading initial ramdisk ..." and the system hangs on this screen forever. My workstation's diagnostic LEDs turn on in a pattern that, according to the service manual, indicates an "other type of failure". The workstation is a Dell T5600. CPU: 2x Intel Xeon E5-2680 (v1) RAM: 8x 8 GB DDR3 1600 MHz GPU: Nvidia NVS510, I'm using nouveau drivers. My kernel cmdline: root=UUID=5136bb35-acaa-4796-b463-8c9ef307025d splash=silent quiet mitigations=auto The latest default 6.5.9 kernel works fine on this machine. I'm available for all kinds of testing/debugging, including kernel recompilation with experimental patches and the like. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1213830] New: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213830 Bug ID: 1213830 Summary: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c22 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(neronio(a)outlook.c | |om) | --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- The upstream fix commit 50d7cdf7a9b1 landed to Linus tree: efi/x86: Avoid physical KASLR on older Dell systems I'm going to backport the fix. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1210335 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1217364 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216647] Missing dummy in kernel-default-base
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216647 https://bugzilla.suse.com/show_bug.cgi?id=1216647#c6 --- Comment #6 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to Fabian Vogt from comment #4) > (In reply to Fabian Vogt from comment #3) > > Submitted to TW (sr#1121191) and SP5 (sr#311823). > > s/SP5/SP6/. > > If there is a particular reason to backport this, please reopen. I would say if it's in 15-SP6, it should be also in 15-SP5. But OTOH nobody complains, to that it's actually OK not include it. FYI dummy module was also needed to test CVE-2023-1829 (bsc#1210335), but that's possible only on 15-SP6 - older versions don't have it, e.g. 15-SP5 (bsc#1217364), but this is not a reason to add the module (not a real request from Leap users). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c11 --- Comment #11 from Anders Stedtlund <falolaf+suse(a)gmail.com> --- I tested now with only pcie_aspm=off and the kernel booted up. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- It means that it's triggered by changes in other parts, e.g. PCI core. Did you test only with pcie_aspm=off boot option? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188954] black screen because dm tries to start before /dev/dri/card0 has been created during init
by bugzilla_noreply＠suse.com 14 Dec '23

14 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1188954 https://bugzilla.suse.com/show_bug.cgi?id=1188954#c31 --- Comment #31 from Felix Miata <mrmazda(a)earthlink.net> --- Created attachment 871337 --> https://bugzilla.suse.com/attachment.cgi?id=871337&action=edit Xorg.0.log from the initial post-boot X failure on KBL GT2 Slowroll host ab250 Host ab250 here is Intel Kaby Lake with Tumbleweed, Slowroll, 15.4, 15.5 and 15.5, among other distros, installed on it. Like several other openSUSE installations here on various hosts, TW, SR & Leap, X will fail to start, claiming /dev/dri/card0 does not exist, but instead of a black screen, it exhibits multi-user.target behavior. When I login and systemctl restart xdm, the greeter starts, and X is running using /dev/dri/card1, with /dev/dri/card0 non-existant. # systemd-analyze Startup finished in 13.602s (firmware) + 9.196s (loader) + 1.801s (kernel) + 2.357s (initrd) + 4.994s (userspace) = 31.953s graphical.target reached after 4.993s in userspace # systemd-analyze critical-chain ... graphical.target @4.993s └─multi-user.target @4.993s └─kbdsettings.service @2.865s +2.126s └─systemd-vconsole-setup.service @2.655s +175ms └─systemd-journald.socket └─system.slice └─-.slice # dmesg | grep aile [ 6.200638] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 6.200641] cfg80211: failed to load regulatory.db [ 6.538658] i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] failed to retrieve link info, disabling eDP # journalctl -b --no-hostname | grep aile Dec 13 21:43:06 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Dec 13 21:43:06 kernel: cfg80211: failed to load regulatory.db Dec 13 21:43:06 kernel: i915 0000:00:02.0: [drm] [ENCODER:94:DDI A/PHY A] failed to retrieve link info, disabling eDP Dec 13 21:43:06 systemd[1]: kbdsettings.service: Failed with result 'signal'. # -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c21 --- Comment #21 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4810-1: An update that solves 12 vulnerabilities, contains three features and has 26 security fixes can now be installed. Category: security (important) Bug References: 1084909, 1210447, 1214286, 1214976, 1215124, 1215292, 1215420, 1215458, 1215710, 1216058, 1216105, 1216259, 1216584, 1216693, 1216759, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217124, 1217140, 1217195, 1217200, 1217205, 1217332, 1217366, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.4 (src): kernel-obs-qa-5.14.21-150400.24.100.1, kernel-obs-build-5.14.21-150400.24.100.2, kernel-syms-5.14.21-150400.24.100.1, kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2, kernel-source-5.14.21-150400.24.100.2, kernel-livepatch-SLE15-SP4_Update_21-1-150400.9.3.2 openSUSE Leap Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 openSUSE Leap Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro for Rancher 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro 5.3 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro for Rancher 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 SUSE Linux Enterprise Micro 5.4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2 Basesystem Module 15-SP4 (src): kernel-default-base-5.14.21-150400.24.100.2.150400.24.46.2, kernel-source-5.14.21-150400.24.100.2 Development Tools Module 15-SP4 (src): kernel-source-5.14.21-150400.24.100.2, kernel-obs-build-5.14.21-150400.24.100.2, kernel-syms-5.14.21-150400.24.100.1 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4_Update_21-1-150400.9.3.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c20 --- Comment #20 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4782-1: An update that solves 12 vulnerabilities, contains three features and has 25 security fixes can now be installed. Category: security (important) Bug References: 1210447, 1214286, 1214976, 1215124, 1215292, 1215420, 1215458, 1215710, 1216058, 1216105, 1216259, 1216584, 1216693, 1216759, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217124, 1217140, 1217195, 1217200, 1217205, 1217332, 1217366, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.4 (src): kernel-source-azure-5.14.21-150400.14.75.1, kernel-syms-azure-5.14.21-150400.14.75.1 Public Cloud Module 15-SP4 (src): kernel-source-azure-5.14.21-150400.14.75.1, kernel-syms-azure-5.14.21-150400.14.75.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- OK, thanks. So the breakage appeared already at the very first 15.5 update kernel. For further narrow-down, let's try to swap the kernel modules. You can copy the kernel modules from the working kernel to the broken kernel. e.g. mkdir /lib/modules/5.14.21-150500.55.7-default/updates cp /lib/modules/5.14.21-150500.53-default/kernel/drivers/nvme/*/*.ko.zst /lib/modules/5.14.21-150500.55.7-default/updates depmod -a 5.14.21-150500.55.7-default dracut -f --kver 5.14.21-150500.55.7-default and retest. This will replace only nvme-* modules while keeping the rest. If this works, you can reduce the modules from */updates and try to figure out which module broke. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- There are tons of update kernels between *-150500.53.2 and *-150500.55.36. Apparently the update took only the latest one, and it was broken. You can install the older update kernels by installing the kernel with versions, e.g. zypper in --oldpackage kernel-default-optional-5.14.21-150500.55.31.1 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1218005] Leap 15.5 does not boot with any of the kernel-default from update repository
by bugzilla_noreply＠suse.com 13 Dec '23

13 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1218005 https://bugzilla.suse.com/show_bug.cgi?id=1218005#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- There are a few older update kernels, e.g. 5.14.21-150500.55.31.1, 5.14.21-150500.55.28.1, etc. You can see it via "zypper se -s kernel-default". Could you try them and figure out which kernel still worked and which not? i.e. narrowing down the regression range. Note that it might be safer to increase the number of installable kernels beforehand, by editing /etc/zypp/zypp.conf. Add more entries in multiversion.kernels line, e.g. multiversion.kernels = latest,latest-1,latest-2,latest-3,running This will allow 4 kernels to be kept on the system without purging. Also, please give the hwinfo and dmesg outputs from the working kernel, too. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1212839] New: LTP test cve-2021-22555 setsockopt08.c fails with ENOENT
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

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

1 11

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c19 --- Comment #19 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4730-1: An update that solves 13 vulnerabilities, contains three features and has 38 security fixes can now be installed. Category: security (important) Bug References: 1084909, 1207948, 1210447, 1214286, 1214700, 1214840, 1214976, 1215123, 1215124, 1215292, 1215420, 1215458, 1215710, 1215802, 1215931, 1216058, 1216105, 1216259, 1216527, 1216584, 1216687, 1216693, 1216759, 1216788, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217095, 1217124, 1217140, 1217147, 1217195, 1217196, 1217200, 1217205, 1217332, 1217366, 1217511, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5633, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.5 (src): kernel-syms-5.14.21-150500.55.39.1, kernel-source-5.14.21-150500.55.39.1, kernel-livepatch-SLE15-SP5_Update_8-1-150500.11.3.1, kernel-obs-build-5.14.21-150500.55.39.1, kernel-obs-qa-5.14.21-150500.55.39.1, kernel-default-base-5.14.21-150500.55.39.1.150500.6.17.1 SUSE Linux Enterprise Micro 5.5 (src): kernel-default-base-5.14.21-150500.55.39.1.150500.6.17.1 Basesystem Module 15-SP5 (src): kernel-source-5.14.21-150500.55.39.1, kernel-default-base-5.14.21-150500.55.39.1.150500.6.17.1 Development Tools Module 15-SP5 (src): kernel-source-5.14.21-150500.55.39.1, kernel-syms-5.14.21-150500.55.39.1, kernel-obs-build-5.14.21-150500.55.39.1 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5_Update_8-1-150500.11.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c18 --- Comment #18 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4734-1: An update that solves 13 vulnerabilities, contains three features and has 38 security fixes can now be installed. Category: security (important) Bug References: 1084909, 1207948, 1210447, 1214286, 1214700, 1214840, 1214976, 1215123, 1215124, 1215292, 1215420, 1215458, 1215710, 1215802, 1215931, 1216058, 1216105, 1216259, 1216527, 1216584, 1216687, 1216693, 1216759, 1216788, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217095, 1217124, 1217140, 1217147, 1217195, 1217196, 1217200, 1217205, 1217332, 1217366, 1217511, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5633, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.5 (src): kernel-syms-azure-5.14.21-150500.33.26.1, kernel-source-azure-5.14.21-150500.33.26.1 Public Cloud Module 15-SP5 (src): kernel-syms-azure-5.14.21-150500.33.26.1, kernel-source-azure-5.14.21-150500.33.26.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c17 --- Comment #17 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4731-1: An update that solves 12 vulnerabilities, contains three features and has 28 security fixes can now be installed. Category: security (important) Bug References: 1084909, 1189998, 1210447, 1214286, 1214976, 1215124, 1215292, 1215420, 1215458, 1215710, 1216058, 1216105, 1216259, 1216584, 1216693, 1216759, 1216761, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217124, 1217140, 1217195, 1217200, 1217205, 1217332, 1217366, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46862, CVE-2023-5158, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.4 (src): kernel-source-rt-5.14.21-150400.15.62.1, kernel-syms-rt-5.14.21-150400.15.62.1 SUSE Linux Enterprise Live Patching 15-SP4 (src): kernel-livepatch-SLE15-SP4-RT_Update_16-1-150400.1.3.1 SUSE Real Time Module 15-SP4 (src): kernel-source-rt-5.14.21-150400.15.62.1, kernel-syms-rt-5.14.21-150400.15.62.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216861] Request for application of patch for kernel issue with cilium and NFS shares
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216861 https://bugzilla.suse.com/show_bug.cgi?id=1216861#c16 --- Comment #16 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2023:4732-1: An update that solves 15 vulnerabilities, contains three features and has 39 security fixes can now be installed. Category: security (important) Bug References: 1207948, 1210447, 1212649, 1214286, 1214700, 1214840, 1214976, 1215095, 1215123, 1215124, 1215292, 1215420, 1215458, 1215710, 1215802, 1215931, 1216058, 1216105, 1216259, 1216527, 1216584, 1216621, 1216687, 1216693, 1216759, 1216761, 1216788, 1216844, 1216861, 1216909, 1216959, 1216965, 1216976, 1217036, 1217068, 1217086, 1217095, 1217124, 1217140, 1217147, 1217195, 1217196, 1217200, 1217205, 1217332, 1217366, 1217511, 1217515, 1217598, 1217599, 1217609, 1217687, 1217731, 1217780 CVE References: CVE-2023-2006, CVE-2023-25775, CVE-2023-3777, CVE-2023-39197, CVE-2023-39198, CVE-2023-4244, CVE-2023-45863, CVE-2023-45871, CVE-2023-46813, CVE-2023-46862, CVE-2023-5158, CVE-2023-5633, CVE-2023-5717, CVE-2023-6039, CVE-2023-6176 Jira References: PED-3184, PED-5021, PED-7237 Sources used: openSUSE Leap 15.5 (src): kernel-source-rt-5.14.21-150500.13.27.2, kernel-syms-rt-5.14.21-150500.13.27.1, kernel-livepatch-SLE15-SP5-RT_Update_8-1-150500.11.3.2 SUSE Linux Enterprise Live Patching 15-SP5 (src): kernel-livepatch-SLE15-SP5-RT_Update_8-1-150500.11.3.2 SUSE Real Time Module 15-SP5 (src): kernel-source-rt-5.14.21-150500.13.27.2, kernel-syms-rt-5.14.21-150500.13.27.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217315] [LenovoX13s] Screen remains black with live images and JeOS images
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217315 https://bugzilla.suse.com/show_bug.cgi?id=1217315#c7 --- Comment #7 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1217315) was mentioned in https://build.opensuse.org/request/show/1132698 15.6 / livecd-openSUSE -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217315] [LenovoX13s] Screen remains black with live images and JeOS images
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217315 https://bugzilla.suse.com/show_bug.cgi?id=1217315#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1217315) was mentioned in https://build.opensuse.org/request/show/1132687 15.5:Images / livecd-openSUSE -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c14 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #14 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Closing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217172] Logitech-Keyboard stops working after login
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217172 https://bugzilla.suse.com/show_bug.cgi?id=1217172#c31 Benjamin Brunner <bbrunner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED --- Comment #31 from Benjamin Brunner <bbrunner(a)suse.com> --- I just tested it with 6.6.3 and everything is working as expected. Thanks Takashi for your help! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217748] Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 12 Dec '23

12 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217748 https://bugzilla.suse.com/show_bug.cgi?id=1217748#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- Did you open the gitlab issue entry for nouveau already and discussed with developers there? If yes, please give the URL, so that we can note it here, too as a reference. In anyway, if the same problem is seen on i915, it's likely a different problem. You can try to report either to KDE or GNOME at first, although this can be rather a rendering problem in a lower layer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] New: [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 11 Dec '23

11 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 Bug ID: 1217512 Summary: [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3760808/modules/jour nal_check/steps/11 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: ivan.ivanov(a)suse.com Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-RPi-aarch64-jeos@RPi4 fails in [journal_check](https://openqa.opensuse.org/tests/3760808/modules/journal_ch… On Raspberry Pi 4, with latest updates, we now have the following kernel trace in journal: kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517 Related updates: raspberrypi-firmware (2023.04.25 -> 2023.11.21) raspberrypi-firmware-config (2023.04.25 -> 2023.11.21) raspberrypi-firmware-dt (2023.05.02 -> 2023.11.21) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [20231123](https://openqa.opensuse.org/tests/3754946) ## Expected result Last good: [20231122](https://openqa.opensuse.org/tests/3750512) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1217882] New: Kernel 5.14.21-150400.24.97 don't support external monitor (i915 with HDMI)
by bugzilla_noreply＠suse.com 11 Dec '23

11 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217882 Bug ID: 1217882 Summary: Kernel 5.14.21-150400.24.97 don't support external monitor (i915 with HDMI) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter-mailbox(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading to kernel 5.14.21-150400.24.97 (kernel-default) my external monitor was no longer detected or available. somewhere recommended kernel parameter i915.force_probe didn't help switching back to kernel 5.14.21-150400.24.88 helped hwinfo --gfxcard Hardware Class: graphics card Model: "Intel 2nd Generation Core Processor Family Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x0126 "2nd Generation Core Processor Family Integrated Graphics Driver Modules: "i915" Driver Status: i915 is active xrandr --listmonitors Monitors: 2 0: +*HDMI1 1920/530x1080/300+0+0 HDMI1 1: +LVDS1 1280/260x800/160+0+0 LVDS1 (with kernel 5.14.21-150400.24.97 HDMI1 was missing) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 11 Dec '23

11 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c12 --- Comment #12 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Ivan Ivanov from comment #11) > (In reply to Guillaume GARDET from comment #10) > > > Could we just revert DMA patches, maybe? > > Ok, Let me check ... I am ashamed how easy this was :-| SR#1132457 is fixing this issue for me. Thank you, Tamás! https://build.opensuse.org/request/show/1132457 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 11 Dec '23

11 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c11 --- Comment #11 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Guillaume GARDET from comment #10) > Could we just revert DMA patches, maybe? Ok, Let me check ... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 10 Dec '23

10 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=218173 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 10 Dec '23

10 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(neronio(a)outlook.c | |om) CC| |neronio(a)outlook.com --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Frank Krüger from comment #19) > Just as a guess, this might be related: > https://bugzilla.kernel.org/show_bug.cgi?id=218173#c20 Thanks, that looks suspicious, indeed. FWIW, the corresponding upstream commit is: a1b87d54f4e45ff5e0d081fb1d9db3bf1a8fb39a x86/efistub: Avoid legacy decompressor when doing EFI boot Tommaso, could you try to revert the commit? It'll lead to a conflict in arch/x86/include/asm/efi.h, but it should be trivially resolvable. Meanwhile I'm building a test kernel package with the revert in OBS home:tiwai:bsc1217344 repo. Once after we confirm it's the same problem, you can join to the upstream bugzilla entry for helping them to resolve the issue properly. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 10 Dec '23

10 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c19 Frank Krüger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #19 from Frank Krüger <fkrueger(a)mailbox.org> --- Just as a guess, this might be related: https://bugzilla.kernel.org/show_bug.cgi?id=218173#c20 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217882] Kernel 5.14.21-150400.24.97 don't support external monitor (i915 with HDMI)
by bugzilla_noreply＠suse.com 07 Dec '23

07 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217882 https://bugzilla.suse.com/show_bug.cgi?id=1217882#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter-mailbox(a)web.de, | |tiwai(a)suse.com Flags| |needinfo?(peter-mailbox@web | |.de) --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Could you boot with "drm.debug=0x1e log_buf_len=16M" boot options for both working and non-working cases, and attach the outputs of dmesg to Bugzilla? You can compress the files before uploading. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217282] kernel-default-6.6.1 fails to boot
by bugzilla_noreply＠suse.com 07 Dec '23

07 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217282 https://bugzilla.suse.com/show_bug.cgi?id=1217282#c11 --- Comment #11 from Tristan Miller <psychonaut(a)nothingisreal.com> --- Yes, everything's working fine now; thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 07 Dec '23

07 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c10 --- Comment #10 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Ivan Ivanov from comment #9) > Thank you, Tamás! Yep, this is it. > > I am afraid that vendor changes around new RPi5 makes new > device trees unusable without corresponding changes in DMA > driver, which I don't see to happen soon. > > Guillaume, I think the safest resolution for the moment is > to revert to prior device tree version. Could we just revert DMA patches, maybe? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217512] [RPi4] kernel: vc4_hdmi fef00700.hdmi: Could not register PCM component: -517
by bugzilla_noreply＠suse.com 07 Dec '23

07 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217512 https://bugzilla.suse.com/show_bug.cgi?id=1217512#c9 --- Comment #9 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Thank you, Tamás! Yep, this is it. I am afraid that vendor changes around new RPi5 makes new device trees unusable without corresponding changes in DMA driver, which I don't see to happen soon. Guillaume, I think the safest resolution for the moment is to revert to prior device tree version. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 06 Dec '23

06 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c13 --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- A possible difference is either the sample rate (44.1kHz vs 48kHz) or the period / buffer sizes. PW uses a small period / buffer sizes while PA tries as large as possible. You can observe the hardware setup in /proc/asound/card*/pcm* proc entries while playback. It might give some hint. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 06 Dec '23

06 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c12 --- Comment #12 from neobrain <deafening_trough502(a)8shield.net> --- For reference, it looks like PipeWire has problems playing back videos in Firefox properly: Videos on YouTube and other sites play around 20% too fast (causing audio to be higher-pitched than normally). Switching from pipewire to pulseaudio (zypper in pulseaudio) resolved this issue. People on other distributions have reported the same effect, though I'm not sure if that's a bug in PipeWire itself then or somewhere else. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 06 Dec '23

06 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- Yeah, even if you can't chase at the end, it'd be helpful to narrow down the regression range. I'm interested in whether you can boot your local built 6.5.x kernel properly. It might be something else, such as grub. In below you can find some info to reduce the kernel build time: https://docs.kernel.org/admin-guide/quickly-build-trimmed-linux.html This will help especially for git bisection. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217314] [LenovoX13s] Unable to boot from USB
by bugzilla_noreply＠suse.com 06 Dec '23

06 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217314 https://bugzilla.suse.com/show_bug.cgi?id=1217314#c2 --- Comment #2 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- https://build.opensuse.org/request/show/1129172 may help with this bug as it includes https://github.com/dracutdevs/dracut/pull/2531 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c11 --- Comment #11 from neobrain <deafening_trough502(a)8shield.net> --- Yup, can confirm audio is working here now with the current 6.6.3 kernel in TW. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217748] Display corruption with spesific applications in Gnome-wayland session
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217748 https://bugzilla.suse.com/show_bug.cgi?id=1217748#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- As it's a nouveau problem on TW, the best would be to report to the upstream, e.g. gitlab.freedesktop.org Issues https://gitlab.freedesktop.org/drm/nouveau/-/issues/ -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217412] [aarch64][LenovoX13s] Missing wsa883x module for audio
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217412 https://bugzilla.suse.com/show_bug.cgi?id=1217412#c10 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(deafening_trough5 | |02(a)8shield.net) CC| |deafening_trough502@8shield | |.net --- Comment #10 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- @neobrain, Could you test latest Tumbleweed please? Snapshot 20231203 [0] includes the kernel update which should solve this bug. On my side, it did fix audio with GNOME live image, but the reduced package set may be the cause. https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/2GRY… -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216841] New: [ build 28.1] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1216841 Bug ID: 1216841 Summary: [ build 28.1] openQA test fails in fanotify16 (LTP) Classification: SUSE Linux Enterprise Server Product: SUSE Linux Enterprise Server 15 SP6 Version: unspecified Hardware: x86-64 URL: https://openqa.opensuse.org/tests/2353240/modules/fano tify16/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: wegao(a)suse.com CC: guillaume.gardet(a)arm.com, kernel-bugs(a)opensuse.org, petr.vorel(a)gmail.com, qa-bugs(a)suse.de Depends on: 1199618 Target Milestone: --- Group: SUSE Enterprise Partner Found By: openQA Blocker: Yes I clone issue to 15sp6 since i found this issue not exist on Tumbleweed now, but still exist on latest result for 15sp6, see following openqa job, i suppose some fix need backport to sle15sp6. https://openqa.suse.de/tests/12752058#step/fanotify16/7 +++ This bug was initially created as a clone of Bug #1199618 +++ ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD24G fails in [fanotify16](https://openqa.opensuse.org/tests/2353240/modules/fanotify16/st… Error log: fanotify.h:336: TBROK: fanotify_mark (3, FAN_MARK_ADD, ..., AT_FDCWD, ".") failed: EXDEV (18) Test process returned unkown none zero value (2). Test took approximately 0.581575272008195 seconds Some test output could not be parsed: 9 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20220302](https://openqa.opensuse.org/tests/2224057) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1199618] [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1199618 https://bugzilla.suse.com/show_bug.cgi?id=1199618#c5 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #5 from Petr Vorel <petr.vorel(a)suse.com> --- That was a bug in the test. fanotify16 fix from Jan Kara has been merged (thanks!). It should be fixed on the next scheduled build 20231204. https://github.com/linux-test-project/ltp/commit/259464c420c3b0d79b2a84f05a… (part of more changes: https://lore.kernel.org/ltp/20231130093533.10036-1-jack@suse.cz/) Feel free to reopen if problem persists. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215285] [RPi3] dwc2 3f980000.usb: dwc2_hc_halt() Channel can't be halted
by bugzilla_noreply＠suse.com 05 Dec '23

05 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1215285 https://bugzilla.suse.com/show_bug.cgi?id=1215285#c9 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com --- Comment #9 from Miroslav Beneš <mbenes(a)suse.com> --- The patch from comment 6 is a part of 6.6.4 stable and now merged to our stable branch so it should appear in TW soon. Guillaume, please let us know the outcome. It might be the fix even though the symptoms are different. As mentioned previously. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Rigo Wenning from comment #14) > Kernel 6.6.4 installed. When booting, the system boots normally into the X > login screen. When I try to login into the KDE session, the background > images of the plasma screen appear, but the desktop remains empty with only > the mouse pointer shown. > > With kernel 6.5.9 the system starts normally. I will create another bug > report as you said its unrelated and I did not find a similar bug. Then it's a different bug. Please create another one. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c14 --- Comment #14 from Rigo Wenning <rigo(a)w3.org> --- Kernel 6.6.4 installed. When booting, the system boots normally into the X login screen. When I try to login into the KDE session, the background images of the plasma screen appear, but the desktop remains empty with only the mouse pointer shown. With kernel 6.5.9 the system starts normally. I will create another bug report as you said its unrelated and I did not find a similar bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Keks Dose from comment #18) > 38: USB 00.0: 0200 Ethernet controller > [Created at usb.122] > Unique ID: Gtr0._FrTcilDi4C > Parent ID: zPk0.xYNhIwdOaa6 > SysFS ID: /devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:2.0 > SysFS BusID: 4-1:2.0 > Hardware Class: network > Model: "ASIX Electronics AX88179 Gigabit Ethernet" > Hotplug: USB > Vendor: usb 0x0b95 "ASIX Electronics Corp." > Device: usb 0x1790 "AX88179 Gigabit Ethernet" .... > Module Alias: "usb:v0B95p1790d0200dc00dsc00dp00ic02isc0Dip00in00" > Driver Info #0: > Driver Status: cdc_ncm is active > Driver Activation Cmd: "modprobe cdc_ncm" > Driver Info #1: > Driver Status: cdc_mbim is active > Driver Activation Cmd: "modprobe cdc_mbim" The device has two interfaces, and only the first one is loaded while you need the second one. That's the problem. A workaround is like what you did: just let the latter driver module loaded. You can set up a softdep instead of always loading, but I guess it doesn't matter much in either way. As you already found out a workaround, I close the bug now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Tommaso Fonda from comment #10) > (In reply to Takashi Iwai from comment #8) > > At first, try to check whether the latest 6.7-rc still suffers from the same > > problem. If it boots, it's something specific to 6.6.x, and we need to find > > an upstream fix. > > > > If 6.7-rc still doesn't boot, it has to be reported to the upstream. But > > without a proper log, it's a bit difficult to know to whom reporting. I > > guess you'd be asked to perform git bisect in such a case. > > Thanks, I will build 6.7-rc as soon as possible and let you know. There is already a kernel package for 6.7-rc available in OBS Kernel:HEAD repo. It can be tested quickly as well as the kernel in OBS Kernel:stable repo. I suppose you've tested only the Leap standard kernels, so far, right? i.e. you didn't build kernels by yourself? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c11 --- Comment #11 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Rigo Wenning from comment #9) > I have also kernel failure with the latest tumbleweed kernel. When > installing it runs dracut for every single core. The system boots. But when > I want to log into KDE, it hangs forever. Console reports a failure to start > powerdevil (for whatever reason). So already the kernel install procedure > seems fishy. > > Again, Kernel 6.5.9 just works fine, boots, KDE runs fine. > > I have a Dell latitude 7490. > > So even if it starts, I think kernel 6.6 has trouble interacting with KDE. > There seems to be something fundamentally wrong. > > BTW, when installed for the first time, the system started and ran fine, > even after reboot. I haven't done any install since then. Now I have updated > to the latest tumbleweed 2023-12-02. That runs fine with kernel 6.5.9 but > does not work with Kernel 6.6. > > I think this is a critical bug If it boots ever, yours can be likely a different issue. There have been already a few different boot problems with 6.6.x. Make sure that your machine still has the boot problem with the latest kernel in OBS Kernel:stable repo, too. And if yes, check whether it shows the very same symptom (no relevant messages even if you boot with nomodeset boot option). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c9 Rigo Wenning <rigo(a)w3.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rigo(a)w3.org --- Comment #9 from Rigo Wenning <rigo(a)w3.org> --- I have also kernel failure with the latest tumbleweed kernel. When installing it runs dracut for every single core. The system boots. But when I want to log into KDE, it hangs forever. Console reports a failure to start powerdevil (for whatever reason). So already the kernel install procedure seems fishy. Again, Kernel 6.5.9 just works fine, boots, KDE runs fine. I have a Dell latitude 7490. So even if it starts, I think kernel 6.6 has trouble interacting with KDE. There seems to be something fundamentally wrong. BTW, when installed for the first time, the system started and ran fine, even after reboot. I haven't done any install since then. Now I have updated to the latest tumbleweed 2023-12-02. That runs fine with kernel 6.5.9 but does not work with Kernel 6.6. I think this is a critical bug -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217344] Linux 6.6.x fails to boot
by bugzilla_noreply＠suse.com 04 Dec '23

04 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217344 https://bugzilla.suse.com/show_bug.cgi?id=1217344#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- At first, try to check whether the latest 6.7-rc still suffers from the same problem. If it boots, it's something specific to 6.6.x, and we need to find an upstream fix. If 6.7-rc still doesn't boot, it has to be reported to the upstream. But without a proper log, it's a bit difficult to know to whom reporting. I guess you'd be asked to perform git bisect in such a case. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 01 Dec '23

01 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c19 --- Comment #19 from Keks Dose <cookie170(a)web.de> --- OK, tried, wrote "cdc_mbim.conf" into /etc/modules-load.d with just one line cdc_mbim, restarted, no. I'm not sure it is worth time and effort to hunt this bug while there is an easy workaround. On the other hand we'll have more and more of those adapters, because more and more notebooks come without ethernet socket and people will buy usb2ethnert adapters. Should work on linux™. Close as wontfix? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 01 Dec '23

01 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c18 --- Comment #18 from Keks Dose <cookie170(a)web.de> --- (In reply to Stefan Hundhammer from comment #17) > The one that 'hwinfo --netcard' tells you to use; see comment #6. No, doesn't work: hwinfo --netcard 14: PCI 14.3: 0282 WLAN controller [Created at pci.386] Unique ID: Dhtl.qVqUKmQ3GD6 SysFS ID: /devices/pci0000:00/0000:00:14.3 SysFS BusID: 0000:00:14.3 Hardware Class: network Model: "Intel Wi-Fi 6 AX201" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa0f0 "Wi-Fi 6 AX201" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x0070 Revision: 0x20 Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp0s20f3 Features: WLAN Memory Range: 0x603d1dc000-0x603d1dffff (rw,non-prefetchable) IRQ: 16 (321 events) HW Address: 08:6a:c5:4a:8f:99 Permanent HW Address: 08:6a:c5:4a:8f:99 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d0000A0F0sv00008086sd00000070bc02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=no, avail=yes, need=no, active=unknown 38: USB 00.0: 0200 Ethernet controller [Created at usb.122] Unique ID: Gtr0._FrTcilDi4C Parent ID: zPk0.xYNhIwdOaa6 SysFS ID: /devices/pci0000:00/0000:00:14.0/usb4/4-1/4-1:2.0 SysFS BusID: 4-1:2.0 Hardware Class: network Model: "ASIX Electronics AX88179 Gigabit Ethernet" Hotplug: USB Vendor: usb 0x0b95 "ASIX Electronics Corp." Device: usb 0x1790 "AX88179 Gigabit Ethernet" Revision: "2.00" Serial ID: "00869C05" Driver: "cdc_ncm" Driver Modules: "cdc_ncm" Device File: enp0s20f0u1c2 HW Address: f8:e4:3b:86:9c:05 Permanent HW Address: f8:e4:3b:86:9c:05 Link detected: no Module Alias: "usb:v0B95p1790d0200dc00dsc00dp00ic02isc0Dip00in00" Driver Info #0: Driver Status: cdc_ncm is active Driver Activation Cmd: "modprobe cdc_ncm" Driver Info #1: Driver Status: cdc_mbim is active Driver Activation Cmd: "modprobe cdc_mbim" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #39 (Hub) And this does not activate ethernet: localhost:/home/AW # modprobe cdc_mbim (as root) I'll write a second file to modules-load.d "cdc_mbim.config" and reboot, but I don't expect success. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1217503] Ethernet to USB ASIX AX88179A chip connects only when opening network configuration module of Yast2
by bugzilla_noreply＠suse.com 01 Dec '23

01 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1217503 https://bugzilla.suse.com/show_bug.cgi?id=1217503#c17 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org Component|Network |Kernel --- Comment #17 from Stefan Hundhammer <shundhammer(a)suse.com> --- The one that 'hwinfo --netcard' tells you to use; see comment #6. -- You are receiving this mail because: You are the assignee for the bug.

1 0