December 2020 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1180316] New: [Build 20201222] openQA test fails in kdump_and_crash

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1180316 Bug ID: 1180316 Summary: [Build 20201222] openQA test fails in kdump_and_crash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1523048/modules/kdum p_and_crash/steps/58 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [kdump_and_crash](https://openqa.opensuse.org/tests/1523048/modules/kdump_an… After the update to kernel 5.10, kdump_and_crash fails crash: cannot determine length of symbol: log_end ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20190311](https://openqa.opensuse.org/tests/877894) ## 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.

2 months, 1 week

1
2
0 0

[kernel-bugs] [Bug 1177624] New: watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [qemu-system-aar:4554]

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1177624 Bug ID: 1177624 Summary: watchdog: BUG: soft lockup - CPU#16 stuck for 23s! [qemu-system-aar:4554] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major 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: afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- Created attachment 842562 --> http://bugzilla.opensuse.org/attachment.cgi?id=842562&action=edit dmesg.log The D05 machine used as a worker for openqa.opensuse.org have been upgraded from Leap 15.1 to Leap 15.2 and shows lots of performance problems. Lots of mistyping in qemu, few screen corruptions. Checking the kernel log (in attachment), we can see some traces related to the watchdog. -- You are receiving this mail because: You are the assignee for the bug.

2 months, 2 weeks

1
5
0 0

[Bug 1180380] New: Blank external monitor after resume from suspend

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1180380 Bug ID: 1180380 Summary: Blank external monitor after resume from suspend 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: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844706 --> https://bugzilla.suse.com/attachment.cgi?id=844706&action=edit dmesg from the system After resuming from suspend to RAM the external display connected through DVI port on the docking station remains blank. Internal display is fine. I can use xrandr to make the monitor work like: xrandr --output DP1-1 --mode some-other-mode xrandr --output DP1-1 --mode original-mode -- You are receiving this mail because: You are the assignee for the bug.

2 months, 4 weeks

1
12
0 0

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1179894 Bug ID: 1179894 Summary: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps" 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: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com, okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com Depends on: 1178401 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1178401 +++ ## Observation https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o… shows repeated warnings about: ``` [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00… shows the same ## Expected result Only errors and warnings in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are the assignee for the bug.

3 months, 3 weeks

1
5
0 0

[kernel-bugs] [Bug 1174622] New: System not reconnecting to WLAN after suspend/resume

by bugzilla_noreply＠suse.com

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.

3 months, 3 weeks

1
25
0 0

[kernel-bugs] [Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1178463 Bug ID: 1178463 Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages 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: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843325 --> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit lsusb -vv With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of: ... [ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? ... The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell, except for these messages, all USB connected peripherals (keyboard, mouse, webcam) are working. Attaching lsusb -vv and dmesg output. -- You are receiving this mail because: You are the assignee for the bug.

3 months, 3 weeks

1
6
0 0

[Bug 1180260] New: [RPi4] Switch to vc4 for display/sound (was rooted through efifb)

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1180260 Bug ID: 1180260 Summary: [RPi4] Switch to vc4 for display/sound (was rooted through efifb) 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: nsaenzjulienne(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With v5.10 vc4, the driver enabling RPi's display controller, now supports RPi4. Let's switch the board's kernel configuration and firmware config to use this instead of efifb, which is extremely limited (no sound, no resolution changes). Among other things, some clocks have to be set-up as builtin, a fix is needed in u-boot so as to cater to DT changes involved in enabling vc4 and some overlays have to be selected in config.txt -- You are receiving this mail because: You are the assignee for the bug.

4 months

1
4
0 0

[kernel-bugs] [Bug 1179226] New: System hang related to power saving

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1179226 Bug ID: 1179226 Summary: System hang related to power saving 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: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # Issue : Screen and input devices would stop responding (black screen, no TTY), as soon as the computer goes into some low power mode. It can be triggered by locking the screen in Gnome (through gdm), and can also be reproduced in XFCE / LightDM by just leaving the computer for a while. # Impact : - black screen, no TTY access - unresponsive system (impossible to launch new processes, reboot, no way to switch init3 & init 5, etc.) - SSH/network access still available, existing process seem to run Moreover, no related log entry, no error (journalctl, dmesg...). # Notes : Hardware is very likely to be fine : - no issue with a Fedora LiveUSB ; - memtest tests passed. # Hardware : Asus PN40 Intel(R) Celeron(R) J4005 CPU @ 2.00GHz Intel Corporation UHD Graphics 605 (rev 03) # System Tumbleweed 20201123 I have no idea on how to debug it further. My huntch is that it is power saving related with Intel chipset. -- You are receiving this mail because: You are the assignee for the bug.

4 months

1
6
0 0

[kernel-bugs] [Bug 1176646] New: Latest Kernel has i915 GPU Hang

by bugzilla_noreply＠suse.com

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.

4 months

1
4
0 0

[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

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.

4 months

1
10
0 0

2022

2021

2020

openSUSE Kernel Bugs December 2020