Description of problem: On my laptop Lenovo W541, I'm able to connect to AP, but the connection is very unreliable, e.g. package installation/upgrade fails, connection to VPN fails etc. Connection to AP is not dropped, but there's bit packet loss. Version-Release number of selected component (if applicable): iwl firmware: iwlwifi-7260-12.ucode (iwl7260-firmware-25.17.12.0-53) network controller: Intel Corporation Wireless 7260 (rev bb) kernel: 4.0.7-300 How reproducible: Always Steps to Reproduce: 1. Connect to AP, after a while, connection is very unreliable and packets are dropped Actual results: Packets are dropped, wifi is almost unusable (e.g. cannot connect to VPN) Expected results: Wifi works without any issue Additional info: When trying to ping some machine, packet loss is from 20% to 100%, while on another machine connected to the same AP is 0%. Part of dmesg output: Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> Auto-activating connection Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: starting connection Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) scheduled... Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) started... Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> NetworkManager state is now CONNECTING Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) scheduled... Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) complete. Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) starting... Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0] Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: (wifi) access point 'pavouk' has security, but secrets are required. Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0] Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) complete. Jul 11 20:10:29 dhcp-10-40-4-225 NetworkManager[1204]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Jul 11 20:10:29 dhcp-10-40-4-225 org.kde.kwalletd5: Application ' "kded5" ' using kwallet without parent window! Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) scheduled... Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) started... Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) scheduled... Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 1 of 5 (Device Prepare) complete. Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) starting... Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0] Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: (wifi) connection has security, and secrets exist. No new secrets needed. Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: added 'ssid' value Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: added 'scan_ssid' value '1' Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: added 'key_mgmt' value 'WPA-PSK' Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: added 'psk' value '<omitted>' Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: added 'proto' value 'WPA RSN' Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): Activation: Stage 2 of 5 (Device Configure) complete. Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <warn> Couldn't disconnect supplicant interface: This interface is not connected. Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> Config: set interface ap_scan to 1 Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: authenticate with 00:22:b0:ab:16:00 Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: send auth to 00:22:b0:ab:16:00 (try 1/3) Jul 11 20:10:34 dhcp-10-40-4-225 NetworkManager[1204]: <info> (wlp3s0): supplicant interface state: scanning -> associating Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: authenticated Jul 11 20:10:34 dhcp-10-40-4-225 kernel: iwlwifi 0000:03:00.0 wlp3s0: disabling HT as WMM/QoS is not supported by the AP Jul 11 20:10:34 dhcp-10-40-4-225 kernel: iwlwifi 0000:03:00.0 wlp3s0: disabling VHT as WMM/QoS is not supported by the AP Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: associate with 00:22:b0:ab:16:00 (try 1/3) Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: RX AssocResp from 00:22:b0:ab:16:00 (capab=0x431 status=0 aid=2) Jul 11 20:10:34 dhcp-10-40-4-225 kernel: wlp3s0: associated
Some more info about the driver from ethtool: driver: iwlwifi version: 4.0.7-300.fc22.x86_64 firmware-version: 25.17.12.0 bus-info: 0000:03:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no
After few discussions with colleagues which have same HW, it seems that this issue happens only on some APs while on some others works fine.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.