Bug 1372993

Summary: [abrt] WARNING: CPU: 0 PID: 1247 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1584 iwl_mvm_report_scan_aborted+0x1c6/0x1d0 [iwlmvm]
Product: [Fedora] Fedora Reporter: Jeremy Harris <jeharris>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: gansalmon, ichavero, itamar, jeharris, jonathan, kernel-maint, madhu.chinakonda, mchehab, stephenfin
Target Milestone: ---Keywords: Reopened
Target Release: ---Flags: labbott: needinfo? (jeharris)
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/82c160d369dd517493fc0a32d929f917a2af520b
Whiteboard: abrt_hash:1e256dc09c390563ecae10fb4138b9806409f01d;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-23 16:44:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Jeremy Harris 2016-09-04 14:01:52 UTC 
Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 1247 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1584 iwl_mvm_report_scan_aborted+0x1c6/0x1d0 [iwlmvm]
iwlwifi 0000:03:00.0:        CSR_GIO_CHICKEN_BITS: 0X07800200
UMAC scan UID 0 status was not cleaned
Modules linked in: tun fuse ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security ebtable_filter ebtables ip6table_filter ip6_tables bnep arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel snd_hda_codec_hdmi mac80211 kvm snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt irqbypass iTCO_vendor_support intel_cstate mei_wdt intel_uncore intel_rapl_perf snd_hda_intel snd_hda_codec uvcvideo snd_hda_core iwlwifi videobuf2_vmalloc snd_hwdep videobuf2_memops snd_seq videobuf2_v4l2 videobuf2_core
 snd_seq_device btusb videodev btrtl btbcm btintel snd_pcm cfg80211 media bluetooth joydev snd_timer rtsx_pci_ms i2c_i801 memstick mei_me thinkpad_acpi mei shpchp snd soundcore rfkill tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt mmc_block nouveau i915 rtsx_pci_sdmmc mmc_core mxm_wmi ttm e1000e crct10dif_pclmul i2c_algo_bit crc32_pclmul drm_kms_helper crc32c_intel ghash_clmulni_intel drm ptp serio_raw rtsx_pci pps_core wmi video fjes
CPU: 0 PID: 1247 Comm: wpa_supplicant Not tainted 4.7.2-201.fc24.x86_64 #1
Hardware name: LENOVO 20FXS0BB14/20FXS0BB14, BIOS R07ET63W (2.03 ) 03/15/2016
 0000000000000286 00000000ae18af37 ffff880421af77b0
iwlwifi 0000:03:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5
 ffffffff813d941f
 ffff880421af7800 0000000000000000 ffff880421af77f0 ffffffff8109facb
 0000063000000000 ffff88042316e058 0000000000000000 ffff88042316d568
Call Trace:
 [<ffffffff813d941f>] dump_stack+0x63/0x84

Potential duplicate: bug 1364714
Comment 1 Jeremy Harris 2016-09-04 14:02:06 UTC 
Created attachment 1197641 [details]
File: dmesg
Comment 2 Justin M. Forbes 2017-04-11 14:46:02 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2017-04-28 17:19:12 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.
Comment 4 Stephen Finucane 2017-12-01 09:35:54 UTC 
I'm seeing this issue on Fedora 27 with the 4.13.15-300.fc27.x86_64 kernel. Output from abrt-cli below.

---

$ abrt-cli list --since 1512057294
id 89b3222582155f1b42fc6a86983b37b12dc3e45e
reason:         WARNING: CPU: 1 PID: 1390 at drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1240 __iwl_mvm_mac_stop+0x137/0x140 [iwlmvm]
time:           Fri 01 Dec 2017 09:20:00 AM GMT
cmdline:        BOOT_IMAGE=/vmlinuz-4.13.15-300.fc27.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.luks.uuid=luks-fbaa0693-081f-44de-ab8d-00d787e7d188 rd.lvm.lv=fedora/swap rhgb quiet LANG=en_IE.UTF-8
package:        kernel-core-4.13.15-300.fc27
count:          1
Directory:      /var/spool/abrt/oops-2017-12-01-09:20:00-1833-0
Reported:       cannot be reported
Comment 5 Laura Abbott 2018-02-20 19:57:46 UTC 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.
Comment 6 Laura Abbott 2018-03-23 16:44:32 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you did actually update, we apologize for the inconvenience (there are a lot of bugs). If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.