Bug 1378520

Summary: [abrt] WARNING: at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1428 iwl_mvm_rx_umac_scan_complete_notif+0x116/0x120 [iwlmvm]()
Product: Red Hat Enterprise Linux 7 Reporter: Ondrej Hudlicky <ohudlick>
Component: kernelAssignee: Stanislaw Gruszka <sgruszka>
Status: CLOSED WORKSFORME QA Contact: Ken Benoit <kbenoit>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: kbenoit, linuxwifi, luca, ohudlick
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:efb71aa31819b7a1cdaf32037b0cb801d27b92ae
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-11 12:03:27 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 Ondrej Hudlicky 2016-09-22 15:46:36 UTC 
Additional info:
reporter:       libreport-2.1.11.1
WARNING: at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1428 iwl_mvm_rx_umac_scan_complete_notif+0x116/0x120 [iwlmvm]()
Modules linked in: ccm tcp_lp cmac rfcomm fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ipt_REJECT nf_reject_ipv4 ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bnep arc4 ext4 mbcache jbd2 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp mac80211 snd_hda_ext_core snd_soc_sst_match snd_soc_core snd_compress iTCO_wdt intel_powerclamp iTCO_vendor_support
coretemp snd_hda_intel snd_hda_codec intel_rapl snd_hda_core iosf_mbi snd_hwdep snd_seq kvm_intel snd_seq_device kvm snd_pcm uvcvideo irqbypass btusb videobuf2_vmalloc rtsx_pci_ms videobuf2_memops btrtl videobuf2_core iwlwifi sg videodev btbcm btintel memstick cfg80211 bluetooth pcspkr snd_timer i2c_i801 shpchp thinkpad_acpi wmi snd soundcore rfkill mei_me mei nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs libcrc32c dm_crypt drbg ansi_cprng sd_mod crc_t10dif crct10dif_generic rtsx_pci_sdmmc mmc_core crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel i915 aesni_intel glue_helper lrw gf128mul ablk_helper i2c_algo_bit cryptd ahci e1000e drm_kms_helper libahci syscopyarea sysfillrect sysimgblt ptp fb_sys_fops serio_raw pps_core drm libata rtsx_pci
i2c_core video fjes dm_mirror dm_region_hash dm_log dm_mod
CPU: 3 PID: 13417 Comm: kworker/3:1 Not tainted 3.10.0-493.el7.x86_64 #1
Hardware name: LENOVO 20FAS2BM04/20FAS2BM04, BIOS N1CET40W (1.08 ) 03/09/2016
Workqueue: events iwl_mvm_async_handlers_wk [iwlmvm]
0000000000000000 00000000b3d0f48e ffff8801f0aafd50 ffffffff81683c5a
ffff8801f0aafd88 ffffffff810857c0 ffff88030f2ed528 ffff88009705a1c0
ffff88030f2ed528 ffff88030f2ed528 ffff8802b5652fc0 ffff8801f0aafd98
Call Trace:
[<ffffffff81683c5a>] dump_stack+0x19/0x1b
[<ffffffff810857c0>] warn_slowpath_common+0x70/0xb0
[<ffffffff8108590a>] warn_slowpath_null+0x1a/0x20
[<ffffffffa0a373f6>] iwl_mvm_rx_umac_scan_complete_notif+0x116/0x120 [iwlmvm]
[<ffffffffa0a25ce3>] iwl_mvm_async_handlers_wk+0xa3/0x130 [iwlmvm]
[<ffffffff810a7e7b>] process_one_work+0x17b/0x470
[<ffffffff810a8cb6>] worker_thread+0x126/0x410
[<ffffffff810a8b90>] ? rescuer_thread+0x460/0x460
[<ffffffff810b046f>] kthread+0xcf/0xe0
[<ffffffff810b03a0>] ? kthread_create_on_node+0x140/0x140
[<ffffffff81694118>] ret_from_fork+0x58/0x90
[<ffffffff810b03a0>] ? kthread_create_on_node+0x140/0x140
Comment 1 Ondrej Hudlicky 2016-09-22 15:46:43 UTC 
Created attachment 1203824 [details]
File: dmesg
Comment 3 Stanislaw Gruszka 2017-06-30 09:20:39 UTC 
Is the problem still reproducible on kernel-3.10.0-679.el7 or newer ?
Comment 4 Stanislaw Gruszka 2017-10-11 12:03:27 UTC 
This bz should be fixed now - closing.