Bug 1244018 - iwlwifi 802.11n issue [NEEDINFO]
Summary: iwlwifi 802.11n issue
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-16 21:52 UTC by Nick Byrne
Modified: 2015-11-23 17:14 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-11-23 17:14:02 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description Nick Byrne 2015-07-16 21:52:35 UTC
Description of problem:

Hardware: Lenogo S3 Yoga 14 with 7265 wifi 

Install: F22, kernel 4.0.7-300.fc22.x86_64 and latest firmware via iwl7260-firmware-25.17.12.0-53.fc22.noarch

dmesg snippet:
[ 1285.574819] iwlwifi 0000:02:00.0: loaded firmware version 25.17.12.0 op_mode iwlmvm
[ 1285.574834] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210

Wifi association cycles through connected and disconnected, with the following in dmesg

kernel: WARNING: CPU: 1 PID: 4547 at net/mac80211/util.c:1824 ieee80211_reconfig+0x1431/0x1620 [mac80211]()
kernel: Modules linked in: ccm fuse rfcomm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_n 
kernel:  industrialio_triggered_buffer kfifo_buf industrialio iTCO_wdt iTCO_vendor_support kvm iwlmvm uvcvideo 
kernel:  drm_kms_helper drm serio_raw sdhci_pci sdhci_acpi sdhci mmc_core wmi video i2c_hid
kernel: CPU: 1 PID: 4547 Comm: kworker/1:3 Tainted: G        W  OE   4.0.7-300.fc22.x86_64 #1 
kernel: Hardware name: LENOVO 20DMCTO1WW/20DMCTO1WW, BIOS JFET33WW(1.10) 12/09/2014
kernel: Workqueue: events ieee80211_restart_work [mac80211]
kernel:  0000000000000000 00000000352a9042 ffff8801da0f7d08 ffffffff81783914
kernel:  0000000000000000 0000000000000000 ffff8801da0f7d48 ffffffff8109c71a
kernel:  ffff8800843651d8 ffff880084365180 0000000000000000 ffff880091d517e0
kernel: Call Trace:
kernel:  [<ffffffff81783914>] dump_stack+0x45/0x57 
kernel:  [<ffffffff8109c71a>] warn_slowpath_common+0x8a/0xc0
kernel:  [<ffffffff8109c84a>] warn_slowpath_null+0x1a/0x20
kernel:  [<ffffffffa05e5751>] ieee80211_reconfig+0x1431/0x1620 [mac80211]
kernel:  [<ffffffff81787d76>] ? mutex_lock+0x16/0x40
kernel:  [<ffffffffa05b11c2>] ieee80211_restart_work+0x42/0x80 [mac80211]
kernel:  [<ffffffff810b5a1b>] process_one_work+0x1bb/0x410
kernel:  [<ffffffff810b5cc3>] worker_thread+0x53/0x470
kernel:  [<ffffffff810b5c70>] ? process_one_work+0x410/0x410
kernel:  [<ffffffff810b5c70>] ? process_one_work+0x410/0x410
kernel:  [<ffffffff810bb728>] kthread+0xd8/0xf0
kernel:  [<ffffffff810bb650>] ? kthread_worker_fn+0x180/0x180
kernel:  [<ffffffff81789e58>] ret_from_fork+0x58/0x90
kernel:  [<ffffffff810bb650>] ? kthread_worker_fn+0x180/0x180


How reproducible:

Happens all the time, i can stop it via /etc/modprobe.d/iwlwifi.conf 
options iwlwifi 11n_disable=1

But non-802.11N as my bandwdith is extremely limited otherwise.

Comment 1 Carwyn Edwards 2015-10-04 23:20:23 UTC
This seems similar to #1223485 ?

Comment 2 Justin M. Forbes 2015-10-20 19:25:12 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is 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 22 kernel bugs.

Fedora 22 has now been rebased to 4.2.3-200.fc22.  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 23, and are still experiencing this issue, please change the version to Fedora 23.

If you experience different issues, please open a new bug report for those.

Comment 3 Fedora Kernel Team 2015-11-23 17:14:02 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 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.


Note You need to log in before you can comment on or make changes to this bug.