diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2012-07-04 13:20:20 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2012-07-09 15:01:02 -0400 |
| commit | c2ca7d92ed4bbd779516beb6eb226e19f7f7ab0f (patch) | |
| tree | b7d3799e7c33b8736ecf9874d11aef8b06fc4334 /net/irda/Kconfig | |
| parent | efd821182cec8c92babef6e00a95066d3252fda4 (diff) | |
iwlegacy: always monitor for stuck queues
This is iwlegacy version of:
commit 342bbf3fee2fa9a18147e74b2e3c4229a4564912
Author: Johannes Berg <johannes.berg@intel.com>
Date: Sun Mar 4 08:50:46 2012 -0800
iwlwifi: always monitor for stuck queues
If we only monitor while associated, the following
can happen:
- we're associated, and the queue stuck check
runs, setting the queue "touch" time to X
- we disassociate, stopping the monitoring,
which leaves the time set to X
- almost 2s later, we associate, and enqueue
a frame
- before the frame is transmitted, we monitor
for stuck queues, and find the time set to
X, although it is now later than X + 2000ms,
so we decide that the queue is stuck and
erroneously restart the device
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/irda/Kconfig')
0 files changed, 0 insertions, 0 deletions