diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2012-07-04 13:20:20 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-07-19 08:58:57 -0700 |
| commit | 57cff816121720c80b39e3b3fb0ef36128fdc45b (patch) | |
| tree | 1db355b0708c0fa71462fb8c23d940fa3fb5eca0 /ipc/shm.c | |
| parent | 3cc4e0e187e4187a6ec13a79dafc1b0f72e31afa (diff) | |
| download | linux-3.10-57cff816121720c80b39e3b3fb0ef36128fdc45b.tar.gz linux-3.10-57cff816121720c80b39e3b3fb0ef36128fdc45b.tar.bz2 linux-3.10-57cff816121720c80b39e3b3fb0ef36128fdc45b.zip | |
iwlegacy: always monitor for stuck queues
commit c2ca7d92ed4bbd779516beb6eb226e19f7f7ab0f upstream.
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
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc/shm.c')
0 files changed, 0 insertions, 0 deletions