diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2011-09-20 16:49:03 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2011-09-21 15:58:24 -0400 |
| commit | 65d0f19e583e80e42b1c67c166bfc4dfdf6ab693 (patch) | |
| tree | f47c025b7471765ab36fd9e5f5510487ef435efb /Documentation/cpuidle | |
| parent | 2e2a41d6ca07d1b2aa67015c35fd80701c98e867 (diff) | |
iwlegacy: do not use interruptible waits
iwlegacy version of fix:
commit effd4d9aece9184f526e6556786a94d335e38b71
Author: Johannes Berg <johannes.berg@intel.com>
Date: Thu Sep 15 11:46:52 2011 -0700
iwlagn: do not use interruptible waits
Since the dawn of its time, iwlwifi has used
interruptible waits to wait for synchronous
commands and firmware loading.
This leads to "interesting" bugs, because it
can't actually handle the interruptions; for
example when a command sending is interrupted
it will assume the command completed fully,
and then leave it pending, which leads to all
kinds of trouble when the command finishes
later.
Since there's no easy way to gracefully deal
with interruptions, fix the driver to not use
interruptible waits.
This at least fixes the error
iwlagn 0000:02:00.0: Error: Response NULL in 'REPLY_SCAN_ABORT_CMD'
I have seen in P2P testing, but it is likely
that there are other errors caused by this.
Cc: stable@kernel.org # 2.6.39+
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'Documentation/cpuidle')
0 files changed, 0 insertions, 0 deletions