Description of problem:
Randomly, when connected to wifi, the connection will drop. I'm guessing this happens more often when the network is under high load, but I'm unsure. Once the connection has dropped, nothing I have tried except for a reboot can bring it back. In talking things over on #fedora, it was suggested that this is probably the driver putting the hardware into a bad state.
Version-Release number of selected component (if applicable):
Name : iwl1000-firmware
Epoch : 1
Version : 126.96.36.199
Release : 38.fc20
(I think that's the right package...)
Always, if you wait long enough. I've never had it stay up more than 24 hours.
Steps to Reproduce:
1. Connect to the network
2. Go about business as usual, and eventually it will disconnect.
Connection disconnects, and then gets stuck in "configuring interface" when attempting to reconnect. Every few minutes in this state it will report the connection was deactivated, and try again.
Wifi stays up, or at least successfully reconnects when it goes down.
The network is using WPA2-PSK encryption. Signal strength is excellent (~97%). I've tried restarting network.service, NetworkManager.service, turning wifi on/off both in Network Manager and with the hardware switch, and reloading the iwlwifi kernel model and its dependencies... no change. Only a reboot fixes the problem.
Here's a description of my hardware: http://paste.fedoraproject.org/120140/24635140/
Do you still have this problem on 3.16 kernel ?
*********** 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 20 kernel bugs.
Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21.
If you experience different issues, please open a new bug report for those.