Hide Forgot
Description of problem: I un-suspended my laptop and connected it to our wireless network. Additional info: reporter: libreport-2.7.2 WARNING: CPU: 0 PID: 2019 at net/mac80211/driver-ops.c:175 drv_conf_tx+0x1ce/0x1e0 [mac80211] wls3: invalid CW_min/CW_max: 0/3 Modules linked in: fuse cmac rmd160 ip_vti ip_tunnel af_key ah6 ah4 esp6 esp4 xfrm4_mode_beet xfrm4_tunnel tunnel4 xfrm4_mode_tunnel xfrm4_mode_transport xfrm6_mode_transport xfrm6_mode_ro xfrm6_mode_beet xfrm6_mode_tunnel ipcomp ipcomp6 xfrm6_tunnel tunnel6 xfrm_ipcomp camellia_generic cast6_generic cast5_generic cast_common deflate cts gcm ccm serpent_sse2_i586 serpent_generic glue_helper blowfish_generic blowfish_common twofish_generic twofish_i586 twofish_common xcbc sha512_generic des_generic geode_aes xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_security ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle iptable_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables arc4 coretemp iwl3945 iwlegacy iTCO_wdt kvm iTCO_vendor_support mac80211 ppdev snd_hda_codec_analog snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core snd_hwdep cfg80211 snd_seq joydev acpi_cpufreq snd_seq_device i2c_i801 snd_pcm lpc_ich thinkpad_acpi snd_timer nsc_ircc snd irda soundcore rfkill tpm_tis parport_pc tpm parport crc_ccitt nfsd auth_rpcgss nfs_acl lockd grace sunrpc i915 e1000e yenta_socket ata_generic i2c_algo_bit drm_kms_helper serio_raw syscopyarea sysfillrect sysimgblt pata_acpi fb_sys_fops ptp drm pps_core fjes video CPU: 0 PID: 2019 Comm: kworker/u4:6 Not tainted 4.7.9-200.fc24.i686 #1 Hardware name: LENOVO 1955A14/1955A14, BIOS 79ETE1WW (2.21 ) 02/05/2008 Workqueue: phy0 ieee80211_iface_work [mac80211] da1cb967 93e4bf73 00200286 e9a07b68 d9b3fd87 e9a07bac f946c0ea e9a07b98 d985a87a f9469350 e9a07bcc 000007e3 f946c0ea 000000af f940023e 000000af 00000002 f6c61540 e9a07c34 e9a07bb8 d985a8e6 00000009 00000000 e9a07bac Call Trace: [<d9b3fd87>] dump_stack+0x58/0x81 [<d985a87a>] __warn+0xea/0x110 [<f940023e>] ? drv_conf_tx+0x1ce/0x1e0 [mac80211] [<d985a8e6>] warn_slowpath_fmt+0x46/0x60 [<f940023e>] drv_conf_tx+0x1ce/0x1e0 [mac80211] [<f9445a4f>] ieee80211_sta_wmm_params+0x2af/0x340 [mac80211] [<f9448e86>] ieee80211_rx_mgmt_beacon+0xa96/0x13a0 [mac80211] [<d98d68ad>] ? clockevents_program_event+0x9d/0x1a0 [<d988a6a1>] ? update_curr+0x161/0x210 [<f944a6f6>] ieee80211_sta_rx_queued_mgmt+0x386/0x8a0 [mac80211] [<d988c317>] ? dequeue_entity+0x287/0xfa0 [<d9b3fb0b>] ? cpumask_next_and+0x2b/0x40 [<d988d4d1>] ? dequeue_task_fair+0x4a1/0xd00 [<d988ffb1>] ? put_prev_entity+0x31/0xce0 [<d9de6cd5>] ? skb_free_head+0x25/0x30 [<d9de6acc>] ? kfree_skbmem+0x5c/0x60 [<d9de6acc>] ? kfree_skbmem+0x5c/0x60 [<f9412c82>] ieee80211_iface_work+0x292/0x430 [mac80211] [<d9811652>] ? __switch_to+0x1a2/0x310 [<d987181f>] process_one_work+0x13f/0x3a0 [<d9871ab9>] worker_thread+0x39/0x460 [<d9871a80>] ? process_one_work+0x3a0/0x3a0 [<d9876e06>] kthread+0xa6/0xc0 [<d9f07662>] ret_from_kernel_thread+0xe/0x24 [<d9876d60>] ? kthread_worker_fn+0x140/0x140
Created attachment 1214008 [details] File: dmesg
*********** 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.
*********** 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.