1. 15 11月, 2011 25 次提交
  2. 22 9月, 2011 1 次提交
    • S
      iwlegacy: do not use interruptible waits · 65d0f19e
      Stanislaw Gruszka 提交于
      iwlegacy version of fix:
      
      commit effd4d9a
      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: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      65d0f19e
  3. 09 8月, 2011 1 次提交
  4. 14 7月, 2011 1 次提交
  5. 18 6月, 2011 1 次提交
  6. 11 6月, 2011 4 次提交
  7. 09 6月, 2011 1 次提交
  8. 30 4月, 2011 5 次提交
  9. 29 4月, 2011 1 次提交
    • S
      iwl4965: fix "TX Power requested while scanning" · f325757a
      Stanislaw Gruszka 提交于
      Fix the following:
      
      WARNING: at drivers/net/wireless/iwlegacy/iwl-4965.c:1128 \
      iwl4965_send_tx_power+0x61/0x102 [iwl4965]() Hardware name: [...]
      TX Power requested while scanning!
      
      Pid: 5723, comm: kworker/u:28 Not tainted 2.6.39-0.rc4.4.fc14.x86_64 #1
      Call Trace:
       [<ffffffff8104e27b>] warn_slowpath_common+0x85/0x9d
       [<ffffffffa02782e0>] ? iwl4965_show_temperature+0x49/0x49 [iwl4965]
       [<ffffffff8104e336>] warn_slowpath_fmt+0x46/0x48
       [<ffffffffa027712f>] iwl4965_send_tx_power+0x61/0x102 [iwl4965]
       [<ffffffff81477e05>] ? mutex_lock+0x36/0x50
       [<ffffffffa0278337>] iwl4965_bg_txpower_work+0x57/0x73 [iwl4965]
       [<ffffffff810647f3>] process_one_work+0x18d/0x286
       [<ffffffff81065a5e>] worker_thread+0xfd/0x181
       [<ffffffff81065961>] ? manage_workers.clone.16+0x172/0x172
       [<ffffffff81069036>] kthread+0x82/0x8a
       [<ffffffff81480524>] kernel_thread_helper+0x4/0x10
       [<ffffffff81068fb4>] ? kthread_worker_fn+0x14b/0x14b
       [<ffffffff81480520>] ? gs_change+0x13/0x13
      Reported-and-tested-by: NPaul Bolle <pebolle@tiscali.nl>
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      f325757a