September 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[kernel-bugs] [Bug 1176026] New: bond interface should not invent mac address by default
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1176026 Bug ID: 1176026 Summary: bond interface should not invent mac address by default 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: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since 5.8.4 (unsure about last digit): when setting up a bond if kernel chooses a random mac removing and readding the slave gets back to the used behaviour: obs-arm-1:~ # modprobe bonding 3: enP2p1s0v1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo -enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are the assignee for the bug.

1 2

[kernel-bugs] [Bug 1173891] New: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook
by bugzilla_noreply＠suse.com 20 Jan '23

20 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1173891 Bug ID: 1173891 Summary: BUG: kernel NULL pointer dereference, address: 0000000d during install on i686 notebook Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While installing Tumbleweed (openSUSE-Tumbleweed-NET-i586-Snapshot20200701-Media.iso) on my old notbook I got the following crash: ---cut--- [ 3448.675690] BUG: kernel NULL pointer dereference, address: 0000000d [ 3448.675713] #PF: supervisor read access in kernel mode [ 3448.675723] #PF: error_code(0x0000) - not-present page [ 3448.675733] *pde = 00000000 [ 3448.675746] Oops: 0000 [#1] SMP [ 3448.675759] CPU: 1 PID: 13684 Comm: rpm Not tainted 5.7.5-1-default #1 openSUSE Tumbleweed (unreleased) [ 3448.675771] Hardware name: Dell Inc. Latitude 2100 /0W785N, BIOS A01 06/02/2009 [ 3448.675792] EIP: __vfs_write+0x83/0x200 [ 3448.675805] Code: 00 00 8b 73 24 89 55 b0 89 4d b4 89 f0 89 75 ac c1 e8 09 83 e0 02 81 e6 00 40 00 00 0f 85 fd 00 00 00 8b b3 a4 00 00 00 8b 36 <f6> 46 0d 20 0f 85 eb 00 00 00 f7 45 ac 00 10 00 00 75 15 8b b3 a4 [ 3448.675825] EAX: 00000000 EBX: ddb3a180 ECX: 00005e44 EDX: bfd3af6c [ 3448.675836] ESI: 00000000 EDI: c28fdf7c EBP: c28fdf4c ESP: c28fdef4 [ 3448.675848] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010246 [ 3448.675859] CR0: 80050033 CR2: 0000000d CR3: 32744000 CR4: 000006d0 [ 3448.675868] Call Trace: [ 3448.675885] ? apparmor_file_permission+0x56/0x160 [ 3448.675902] ? security_file_permission+0x2c/0x150 [ 3448.675916] ? rw_verify_area+0x44/0x90 [ 3448.675928] vfs_write+0x9b/0x1c0 [ 3448.675942] ? ktime_get_real_ts64+0x4f/0x150 [ 3448.675955] ksys_write+0x58/0xd0 [ 3448.675968] __ia32_sys_write+0x15/0x20 [ 3448.675982] do_int80_syscall_32+0x41/0x120 [ 3448.675996] entry_INT80_32+0xfc/0xfc [ 3448.676007] EIP: 0xb7d71522 [ 3448.676018] Code: 90 66 90 66 90 66 90 90 56 53 83 ec 14 8b 5c 24 20 8b 4c 24 24 8b 54 24 28 65 a1 0c 00 00 00 85 c0 75 1d b8 04 00 00 00 cd 80 <89> c3 3d 00 f0 ff ff 77 4d 83 c4 14 89 d8 5b 5e c3 8d 74 26 00 90 [ 3448.676039] EAX: ffffffda EBX: 00000009 ECX: bfd3af6c EDX: 00005e44 [ 3448.676050] ESI: 02486bf0 EDI: b7e5ba90 EBP: 02481c50 ESP: bfd3aea0 [ 3448.676061] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000246 [ 3448.676077] ? nmi+0xc5/0x2b0 [ 3448.676085] Modules linked in: nls_utf8 isofs usbhid parport_pc parport btrfs xor raid6_pq libcrc32c dm_multipath dm_mod 8021q garp mrp stp llc arc4 fan nfs lockd grace fscache nls_iso8859_1 nls_cp437 af_packet sg st sr_mod cdrom iscsi_ibft iscsi_boot_sysfs sunrpc b43 cordic bcma mac80211 cfg80211 i915 ums_realtek uas usb_storage libarc4 dell_laptop gpio_ich ledtrig_audio dell_wmi rfkill sparse_keymap wmi_bmof dell_smbios dell_wmi_descriptor dcdbas i2c_algo_bit ahci drm_kms_helper libahci syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 cec joydev libata rc_core pcspkr serio_raw i2c_i801 libphy lpc_ich drm uhci_hcd ssb ehci_pci ehci_hcd mmc_core usbcore ptp pps_core hwmon pcmcia pcmcia_core thermal wmi tiny_power_button battery button ac video acpi_cpufreq scsi_dh_rdac scsi_dh_emc scsi_dh_alua edd squashfs loop [ 3448.676246] CR2: 000000000000000d [ 3448.676258] ---[ end trace 2e9b3e59a1582583 ]--- ---cut--- Filesystem is btrfs. Thanks, //richard -- You are receiving this mail because: You are the assignee for the bug.

1 6

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

22 Jul '22

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

1 27

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

20 Jul '22

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

1 20

[kernel-bugs] [Bug 1176646] New: Latest Kernel has i915 GPU Hang
by bugzilla_noreply＠suse.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176646 Bug ID: 1176646 Summary: Latest Kernel has i915 GPU Hang 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: erecio(a)polywog.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 841741 --> http://bugzilla.opensuse.org/attachment.cgi?id=841741&action=edit dmesg output The following kernel works fine with my i915 GPU (5.6.14-1). However, the latest kernel 5.7+ (kernel-default-5.8.7-1.2.x86_64) causes my GPU to hang and it flickers and can never login. Switch back to 5.6 and it works fine. There have been other reports on Fedora with the same thing. https://bugzilla.redhat.com/show_bug.cgi?id=1843274 I have attached my dmesg output. I use the zap option to kill the xorg server and kdm comes up just fine most of the time. Trying to login is no good though. Also I can ctrl-alt-f2 to go on command line just fine. So it seems to be xorg with the new kernel. [ 163.236358] ------------[ cut here ]------------ [ 163.236365] WARNING: CPU: 0 PID: 0 at kernel/sched/core.c:4576 default_wake_function+0x16/0x30 [ 163.236366] Modules linked in: xt_MASQUERADE xt_addrtype iptable_nat nf_nat nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_state xt_LOG xt_multiport xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c af_packet iscsi_ibft iscsi_boot_sysfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables bpfilter rfkill tun binfmt_misc dmi_sysfs msr crypto_simd glue_helper dm_crypt intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio kvm_intel snd_hda_codec_hdmi snd_hda_intel kvm snd_intel_dspcfg irqbypass snd_hda_codec at24 mei_hdcp iTCO_wdt snd_hda_core intel_pmc_bxt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iTCO_vendor_support cryptd snd_hwdep pcspkr snd_pcm snd_timer fan thermal snd e1000e soundcore i2c_i801 tiny_power_button i2c_smbus button mei_me lpc_ich mei hid_generic usbhid i915 i2c_algo_bit drm_kms_helper xhci_pci xhci_pci_renesas syscopyarea sysfillrect [ 163.236389] sysimgblt fb_sys_fops cec xhci_hcd rc_core ehci_pci ehci_hcd drm crc32c_intel usbcore video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 163.236396] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.8.7-1-default #1 openSUSE Tumbleweed [ 163.236397] Hardware name: Gigabyte Technology Co., Ltd. B85M-Gaming 3/B85M-Gaming 3, BIOS F1 09/05/2014 [ 163.236399] RIP: 0010:default_wake_function+0x16/0x30 [ 163.236401] Code: e8 df 53 45 00 eb 99 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 f7 c2 fe ff ff ff 75 09 48 8b 7f 08 e9 da f9 ff ff <0f> 0b 48 8b 7f 08 e9 cf f9 ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 [ 163.236401] RSP: 0018:ffffa51080003eb8 EFLAGS: 00010086 [ 163.236402] RAX: ffffffffb0cf0e30 RBX: ffffa51080203db0 RCX: ffffa51080003ed0 [ 163.236403] RDX: 00000000fffffffb RSI: 0000000000000003 RDI: ffffa51080203db0 [ 163.236404] RBP: ffff980009218568 R08: 0000000000000000 R09: ffffffffc0321600 [ 163.236404] R10: ffff97ffdbd86280 R11: 0000000000000001 R12: 0000000000000046 [ 163.236405] R13: ffff980009218560 R14: ffffa51080003ed0 R15: ffffa51080003f60 [ 163.236406] FS: 0000000000000000(0000) GS:ffff980017200000(0000) knlGS:0000000000000000 [ 163.236406] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 163.236407] CR2: 00007f8ff0b07000 CR3: 000000003f80a001 CR4: 00000000000606f0 [ 163.236408] Call Trace: [ 163.236409] <IRQ> [ 163.236414] autoremove_wake_function+0xe/0x30 [ 163.236460] __i915_sw_fence_complete+0x160/0x1c0 [i915] [ 163.236483] dma_i915_sw_fence_wake_timer+0x2c/0x50 [i915] [ 163.236506] signal_irq_work+0x21c/0x310 [i915] [ 163.236510] irq_work_single+0x2c/0x40 [ 163.236511] irq_work_run_list+0x2d/0x40 [ 163.236512] irq_work_run+0x14/0x30 [ 163.236514] __sysvec_irq_work+0x2d/0xb0 [ 163.236517] asm_call_on_stack+0x12/0x20 [ 163.236518] </IRQ> [ 163.236520] sysvec_irq_work+0x6f/0x90 [ 163.236522] asm_sysvec_irq_work+0x12/0x20 [ 163.236524] RIP: 0010:cpuidle_enter_state+0xb6/0x3f0 [ 163.236525] Code: 10 ee c0 4e e8 eb 52 8d ff 49 89 c7 0f 1f 44 00 00 31 ff e8 cc 69 8d ff 80 7c 24 0f 00 0f 85 d4 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 e0 01 00 00 49 63 d4 4c 2b 7c 24 10 48 8d 04 52 48 [ 163.236526] RSP: 0018:ffffffffb2403e58 EFLAGS: 00000246 [ 163.236527] RAX: ffff98001722e680 RBX: ffff980017239600 RCX: 000000000000001f [ 163.236527] RDX: 0000000000000000 RSI: 000000002817b731 RDI: 0000000000000000 [ 163.236528] RBP: ffffffffb24f6260 R08: 0000002601a4c721 R09: 00000000000002ee [ 163.236528] R10: ffff98001722d444 R11: 00000000000005f4 R12: 0000000000000004 [ 163.236529] R13: 0000000000000004 R14: 0000000000000004 R15: 0000002601a4c721 [ 163.236531] ? cpuidle_enter_state+0xa4/0x3f0 [ 163.236533] cpuidle_enter+0x29/0x40 [ 163.236535] cpuidle_idle_call+0x13f/0x210 [ 163.236536] do_idle+0x73/0xd0 [ 163.236538] cpu_startup_entry+0x19/0x20 [ 163.236541] start_kernel+0x485/0x4a4 [ 163.236544] secondary_startup_64+0xb6/0xc0 [ 163.236546] ---[ end trace 5ea2057b70f281c8 ]--- [ 163.236548] ------------[ cut here ]------------ [ 574.899156] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 574.899728] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 575.003261] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 580.786335] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc79, in ksplashqml [3389] [ 580.786882] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 580.890229] i915 0000:00:02.0: [drm] ksplashqml[3389] context reset due to GPU hang [ 583.858065] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in plasmashell [3461] [ 583.858294] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 583.961652] i915 0000:00:02.0: [drm] plasmashell[3461] context reset due to GPU hang [ 586.929534] i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:8edcfc7b, in kwin_x11 [3427] [ 586.929859] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 [ 587.033116] i915 0000:00:02.0: [drm] kwin_x11[3427] context reset due to GPU hang -- You are receiving this mail because: You are the assignee for the bug.

1 4

[kernel-bugs] [Bug 1173294] New: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150
by bugzilla_noreply＠suse.com 17 Jan '22

17 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1173294 Bug ID: 1173294 Summary: iwlwifi: TX on unused queue 5 WARNING: tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ddiss(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This looks similar to: https://bugzilla.kernel.org/show_bug.cgi?id=204643 I hit the following WARNING while playing with network manager's new activate hotspot UI functionality and then disabling all radio (nmcli radio wifi off): [ 1157.323257] wlan1: deauthenticating from 34:31:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) [ 1157.323301] ------------[ cut here ]------------ [ 1157.323302] TX on unused queue 5 [ 1157.323343] WARNING: CPU: 3 PID: 6784 at ../drivers/net/wireless/intel/iwlwifi/pcie/tx.c:2346 iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323344] Modules linked in: tun ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptablet [ 1157.323376] snd_hda_core dell_smm_hwmon fat kvm snd_hwdep dell_wmi dell_smbios irqbypass iwlwifi dcdbas joydev snd_pcm snd_timer sparse_keymap mei_me cfg80211 dell_wmi_d] [ 1157.323412] CPU: 3 PID: 6784 Comm: kworker/3:1 Not tainted 5.3.18-lp152.19-default #1 openSUSE Leap 15.2 (unreleased) [ 1157.323413] Hardware name: Dell Inc. Latitude E7450/0YGN55, BIOS A21 05/16/2019 [ 1157.323434] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 1157.323444] RIP: 0010:iwl_trans_pcie_tx+0xa1e/0x1150 [iwlwifi] [ 1157.323447] Code: 80 3d 2b 65 03 00 00 b8 ea ff ff ff 0f 85 25 f8 ff ff 89 ce 48 c7 c7 49 6e d8 c0 89 04 24 c6 05 0d 65 03 00 01 e8 42 94 33 e1 <0f> 0b 8b 04 24 e9 03 f8 c [ 1157.323448] RSP: 0018:ffff9f66404bf7f0 EFLAGS: 00010282 [ 1157.323449] RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000000006 [ 1157.323450] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff93915e399a10 [ 1157.323451] RBP: ffff939155e59e28 R08: 000000000000065e R09: 0000000000000001 [ 1157.323452] R10: 0000000000000005 R11: 0000000000000001 R12: ffff9390f1cc4b00 [ 1157.323453] R13: 0000000000000005 R14: 0000000000000037 R15: ffff9391566683e8 [ 1157.323454] FS: 0000000000000000(0000) GS:ffff93915e380000(0000) knlGS:0000000000000000 [ 1157.323455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1157.323456] CR2: 00007f8e2af0a000 CR3: 00000002ba00a005 CR4: 00000000003606e0 [ 1157.323457] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1157.323458] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1157.323459] Call Trace: [ 1157.323473] ? iwl_mvm_set_tx_cmd+0x1a2/0x480 [iwlmvm] [ 1157.323483] ? iwl_mvm_get_tx_rate.isra.21+0x44/0xe0 [iwlmvm] [ 1157.323491] ? iwl_mvm_get_tx_ant+0x43/0x80 [iwlmvm] [ 1157.323499] ? iwl_mvm_set_tx_params+0x11f/0x4e0 [iwlmvm] [ 1157.323507] iwl_mvm_tx_mpdu+0x207/0x600 [iwlmvm] [ 1157.323516] iwl_mvm_tx_skb_sta+0x1ed/0x480 [iwlmvm] [ 1157.323524] iwl_mvm_tx_skb+0x17/0x40 [iwlmvm] [ 1157.323532] iwl_mvm_mac_itxq_xmit+0x7a/0xf0 [iwlmvm] [ 1157.323559] ieee80211_queue_skb+0x2da/0x420 [mac80211] [ 1157.323582] ieee80211_tx+0xd9/0x130 [mac80211] [ 1157.323604] __ieee80211_tx_skb_tid_band+0x58/0x70 [mac80211] [ 1157.323627] ieee80211_send_deauth_disassoc+0xfd/0x130 [mac80211] [ 1157.323649] ieee80211_set_disassoc+0x3a0/0x5e0 [mac80211] [ 1157.323679] ieee80211_mgd_deauth+0x113/0x230 [mac80211] [ 1157.323701] cfg80211_mlme_deauth+0xaf/0x1c0 [cfg80211] [ 1157.323720] cfg80211_mlme_down+0x7b/0x90 [cfg80211] [ 1157.323739] cfg80211_disconnect+0x11f/0x1d0 [cfg80211] [ 1157.323754] cfg80211_leave+0x26/0x40 [cfg80211] [ 1157.323767] cfg80211_netdev_notifier_call+0x258/0x5b0 [cfg80211] [ 1157.323774] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323794] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323800] ? iwl_mvm_set_tim+0x50/0x50 [iwlmvm] [ 1157.323817] ? __iterate_interfaces+0x78/0x110 [mac80211] [ 1157.323831] ? ieee80211_iterate_active_interfaces_atomic+0xd/0x10 [mac80211] [ 1157.323838] ? iwl_mvm_recalc_multicast+0x45/0x70 [iwlmvm] [ 1157.323841] ? rtnl_is_locked+0x11/0x20 [ 1157.323843] ? inetdev_event+0x46/0x5c0 [ 1157.323850] ? iwl_mvm_configure_filter+0x61/0x80 [iwlmvm] [ 1157.323853] notifier_call_chain+0x47/0x70 [ 1157.323855] __dev_close_many+0x5f/0x110 [ 1157.323857] dev_close_many+0x7c/0x120 [ 1157.323859] dev_close.part.104+0x3e/0x70 [ 1157.323874] cfg80211_shutdown_all_interfaces+0x6d/0xc0 [cfg80211] [ 1157.323886] cfg80211_rfkill_sync_work+0x29/0x30 [cfg80211] [ 1157.323889] process_one_work+0x1f4/0x3e0 [ 1157.323892] worker_thread+0x2d/0x3e0 [ 1157.323894] ? process_one_work+0x3e0/0x3e0 [ 1157.323895] kthread+0x10d/0x130 [ 1157.323897] ? kthread_park+0xa0/0xa0 [ 1157.323899] ret_from_fork+0x35/0x40 [ 1157.323902] ---[ end trace 3217541a75ee82c3 ]--- I've not been able to reproduce it so far, but will update when/if I get a clear procedure. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[kernel-bugs] [Bug 1173819] New: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS
by bugzilla_noreply＠suse.com 22 Oct '21

22 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1173819 Bug ID: 1173819 Summary: 'BUG: workqueue lockup' on ThunderX2 machines with kernel 4.12.14 in OBS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 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: adrian.schroeter(a)suse.com, afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- obs-arm-7, -8 and -9 are often down in OBS these days due to kernel issues. One issue is a workqueue lockup: BUG: workqueue lockup - pool cpus=59 node=0 flags=0x0 nice=0 stuck for 92265s! -- You are receiving this mail because: You are the assignee for the bug.

1 7

[kernel-bugs] [Bug 1175105] New: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table
by bugzilla_noreply＠suse.com 03 Aug '21

03 Aug '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1175105 Bug ID: 1175105 Summary: mdadm doesn't except partition for --add because of "dirt" in that partition of a fresh gpt table Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf(a)czekalla.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm about to migrate an important central private nextcloud server to 15.2. I'm use RAID1 for all my partitions and benefit from that with easy made clones with the help of mdadm by growing the number of raid-devices and adding a refreshed SSD with a new gpt partition table and cloned partitions descriptions. This worked for most of the six partitions but one. (It's not the first installation I transform with this idea. Did these processes already several times) This faulty one showed weird error messages I couldn't find a real good reason for, like ... ...on console: # mdadm --verbose /dev/md2 --add /dev/sdc5 mdadm: add new device failed for /dev/sdc5 as 4: Invalid argument # mdadm -E /dev/sdc5 /dev/sdc5: Magic : a92b4efc Version : 1.0 Feature Map : 0x9 Array UUID : 94bbbcd3:ad4d1b0b:dcd4d548:1af16050 Name : any:2 Creation Time : Fri Feb 2 20:09:03 2018 Raid Level : raid1 Raid Devices : 3 Avail Dev Size : 83892192 sectors (40.00 GiB 42.95 GB) Array Size : 41945984 KiB (40.00 GiB 42.95 GB) Used Dev Size : 83891968 sectors (40.00 GiB 42.95 GB) Super Offset : 83892208 sectors Unused Space : before=0 sectors, after=224 sectors State : active Device UUID : c9e17312:0069d580:42782958:8817e0f7 Internal Bitmap : -16 sectors from superblock Update Time : Mon Aug 10 18:09:21 2020 Bad Block Log : 512 entries available at offset -8 sectors - bad blocks present. Checksum : 7b5d72a - correct Events : 0 Device Role : spare Array State : AA. ('A' == active, '.' == missing, 'R' == replacing) First I was blinded by the "bad blocks present", but all devices checked out perfectly healthy in smart and also extended device scans didn't show any problems. Took me several hours to get through all this. dmesg: md: sdc5 does not have a valid v1.0 superblock, not importing! md: md_import_device returned -22 Also tried to --zero-superblock the partition of course. No change of behavior and still the above error message in dmesg remained. At the end I found a surprising hint on serverfault.com (https://serverfault.com/questions/696392/how-to-add-disk-back-to-raid-and-r…) from Oct. 2015 with a similar behavior that suggested to clean-up of the partition first with dd writing zeros (dd if=/dev/zero of=/dev/sdc5 status=progress) and try again later to add the last seemingly faulty partition. And long story short, this really worked. Somehow mdadm - and md behind - is choking on some dirt inside of partition blocks from old content before the disk/ssd was wiped with a new gpt partition table. (Of course with SSDs you try to prevent unnecessary writes and wiping every block of a disk first) I'm using md device type 1.0 here (in contrast to the serverfault.com case), where the RAID/md setup data is stored at the end of the partition. I had to wipe exactly this area at the end of the partition to add it afterwards successfully. Of course, no effect when doing this at the beginning of the partition (mentioned in the serverfault.com case) where md type 1.2 stores the md setup data. I think after 5 years this might need a clean up in mdadm or md device management. At least the error message should suggest to clean the partition first instead of this error message in dmesg. Also the --zero-superblock should wipe out the dirt beneath the superblock and not seemingly let some stuff leak here. Thanks Ralf -- You are receiving this mail because: You are the assignee for the bug.

1 5

[kernel-bugs] [Bug 1176351] New: Audio device: Intel Corporation Device 02c8: not detected
by bugzilla_noreply＠suse.com 22 Jun '21

22 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1176351 Bug ID: 1176351 Summary: Audio device: Intel Corporation Device 02c8: not detected 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've got a new notebook, Intel chipsets only, where everythings works - except for audio. It appears the audio chip/sound card are not detected by the kernel or initialized. lspci -v has: 00:1f.3 Audio device: Intel Corporation Device 02c8 (prog-if 80) Subsystem: Lenovo Device 22be Flags: fast devsel, IRQ 16, IOMMU group 13 Memory at ea33c000 (64-bit, non-prefetchable) [size=16K] Memory at ea000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci # lsmod | grep snd snd 114688 1 thinkpad_acpi soundcore 16384 1 snd # cat /proc/asound/cards --- no soundcards --- # dmesg | grep audio [ 18.072024] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 18.072026] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 18.072036] sof-audio-pci 0000:00:1f.3: enabling device (0004 -> 0006) [ 18.072179] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 18.072267] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 18.078993] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 18.109492] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 18.109493] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 18.109497] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 18.109521] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 18.109522] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 18.109524] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 18.110449] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 [ 220.595600] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 220.595605] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 220.595786] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [ 220.595899] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 220.601386] sof-audio-pci 0000:00:1f.3: use msi interrupt mode [ 220.630638] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5 [ 220.630640] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 220.630644] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 4 [ 220.630664] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-cml.ri failed with error -2 [ 220.630666] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-cml.ri failed err: -2 [ 220.630669] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 [ 220.631004] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 -- You are receiving this mail because: You are the assignee for the bug.

1 15

[kernel-bugs] [Bug 1177009] New: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware
by bugzilla_noreply＠suse.com 16 Jun '21

16 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177009 Bug ID: 1177009 Summary: Leap 15.2 stopped working in KVM with ovmf-ia32 firmware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: I'm reporting as a kernel bug, but it might be a bug elsewhere. And yes, I know that this is not a supported configuration. Situation: I have both Leap 15.2 and Tumbleweed installed side by side in a KVM virtual machine, using 32-bit efi for booting. Both Leap and Tumbleweed are 64-bit. I originally setup this VM under Leap 15.0 (as KVM host machine). Everything had been working well. However, I recently tried to boot the Leap 15.2 system in that VM, and it failed to boot. I see the kernel and initrd being loaded. And then there is a reset and I get back to the boot screen. However, Tumbleweed continues to boot without a problem on that virtual machine. I am booting with "grub2-i386-efi", which is installed for both Tumbleweed and for Leap 15.2. This does not appear to be a grub2 problem, because the kernel and initrd are being loaded. Before today, I most recently booted Leap 15.2 on Sept 22, and I updated it at that time. I then rebooted (successfully) to check after the update. I have not been able to boot since, until my workaround today. The KVM host is also running Leap 15.2, and I did apply some updates since Sept 22. My guess is that one of those updates affected how the virtualization is working. I have a similar install of Leap 15.2 on an external USB drive, and I have that setup so that it can boot with legacy BIOS, with 64-bit efi and with 32-bit efi. Testing with that, it also fails to boot the same virtual machine with 32-bit efi, bit it successfully boots with either legacy BIOS or with 64-bit efi. So it looks as if whatever is going wrong has to do with communication between the kernel and the 32-bit efi firmware. Booting the virtual machine to Tumbleweed, then setting up for rescue/chroot, I have installed kernel 5.8.11-1.gf4bb27a-default from the stable kernels repo. And now Leap 15.2 does boot successfully with that kernel. It does not boot with any of the 5.3.x kernels for Leap 15.2 that I have tested. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 21