linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, "Guy,
	Wey-Yi" <wey-yi.w.guy@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: iwlagn is getting even worse with 3.3-rc1
Date: Wed, 25 Jan 2012 21:49:04 -0800	[thread overview]
Message-ID: <CANUX_P0H_WaWwnpjoBcMpZQY4xH=cbVhAKxWKXmz-HwFMcWS6w@mail.gmail.com> (raw)
In-Reply-To: <20120126003735.GA2346@gamma.logic.tuwien.ac.at>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi Norbert,

>
> syslog output is at http://www.logic.at/people/preining/syslog.log
> this is after a suspend and resume.
>
> first connection after resume succeeded at around kernel time 378.859794
> then it worked for say 20sec or so, hard to say when exactely it dropped,
> but defeinitely at kernel time 451 it was finished.
>
> After that nothing went out or in again.
>
> Hope you can make something out of that.
>

Unfortunately, not really. I can see you are hitting PASSIVE_NO_RX,
meaning that the uCode complains that you are trying to Tx on a
passive channel on which it hasn't heard any beacon yet. But then we
finally get a beacon there, and open the queue again.

Anyway, can you try the attached patch ?
Note that I have no real way to test it (I have to admit I haven't
even compiled... I am not in my office).
I hope it might help.

[-- Attachment #2: tid.patch --]
[-- Type: application/octet-stream, Size: 1998 bytes --]

diff --git a/drivers/net/wireless/iwlwifi/iwl-agn-tx.c b/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
index d9d758e..1b70048 100644
--- a/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
+++ b/drivers/net/wireless/iwlwifi/iwl-agn-tx.c
@@ -95,6 +95,7 @@ static void iwlagn_tx_cmd_build_basic(struct iwl_priv *priv,
 			tx_flags |= TX_CMD_FLG_SEQ_CTL_MSK;
 		else
 			tx_flags &= ~TX_CMD_FLG_SEQ_CTL_MSK;
+		tx_cmd->tid_tspec = IWL_MAX_TID_COUNT;
 	}
 
 	iwlagn_tx_cmd_protection(priv, info, fc, &tx_flags);
@@ -808,6 +809,8 @@ static void iwl_rx_reply_tx_agg(struct iwl_priv *priv,
 	u32 status = le16_to_cpu(tx_resp->status.status);
 	int i;
 
+        WARN_ON(tid == IWL_MAX_TID_COUNT);
+
 	if (agg->wait_for_ba)
 		IWL_DEBUG_TX_REPLY(priv,
 			"got tx response w/o block-ack\n");
@@ -1035,10 +1038,12 @@ int iwlagn_rx_reply_tx(struct iwl_priv *priv, struct iwl_rx_mem_buffer *rxb,
 		}
 
 		__skb_queue_head_init(&skbs);
-		priv->tid_data[sta_id][tid].next_reclaimed = next_reclaimed;
 
-		IWL_DEBUG_TX_REPLY(priv, "Next reclaimed packet:%d",
-					  next_reclaimed);
+		if (tid != IWL_MAX_TID_COUNT) {
+			priv->tid_data[sta_id][tid].next_reclaimed = next_reclaimed;
+			IWL_DEBUG_TX_REPLY(priv, "Next reclaimed packet:%d",
+						  next_reclaimed);
+		}
 
 		/*we can free until ssn % q.n_bd not inclusive */
 		WARN_ON(iwl_trans_reclaim(trans(priv), sta_id, tid, txq_id,
diff --git a/drivers/net/wireless/iwlwifi/iwl-trans-pcie.c b/drivers/net/wireless/iwlwifi/iwl-trans-pcie.c
index aa87994..fa1b369 100644
--- a/drivers/net/wireless/iwlwifi/iwl-trans-pcie.c
+++ b/drivers/net/wireless/iwlwifi/iwl-trans-pcie.c
@@ -1551,7 +1551,7 @@ static int iwl_trans_pcie_reclaim(struct iwl_trans *trans, int sta_id, int tid,
 
 	txq->time_stamp = jiffies;
 
-	if (unlikely(txq_id >= IWLAGN_FIRST_AMPDU_QUEUE &&
+	if (unlikely(tid != IWL_MAX_TID_COUNT && txq_id >= IWLAGN_FIRST_AMPDU_QUEUE &&
 		     txq_id != trans_pcie->agg_txq[sta_id][tid])) {
 		/*
 		 * FIXME: this is a uCode bug which need to be addressed,

  reply	other threads:[~2012-01-26  5:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24  1:36 iwlagn is getting even worse with 3.3-rc1 Norbert Preining
2012-01-24  4:47 ` Emmanuel Grumbach
2012-01-25  0:22   ` Norbert Preining
2012-01-25  5:32     ` Emmanuel Grumbach
2012-01-26  0:37       ` Norbert Preining
2012-01-26  5:49         ` Emmanuel Grumbach [this message]
2012-01-26 21:13           ` Emmanuel Grumbach
2012-01-26 23:25             ` Norbert Preining
2012-01-27  0:06               ` Emmanuel Grumbach
2012-01-31  2:41                 ` Dave Jones
2012-02-01 15:43                   ` Dave Jones
2012-02-01 14:45                     ` Guy, Wey-Yi
2012-01-27  1:50               ` Norbert Preining
2012-01-27  3:11                 ` Emmanuel Grumbach
2012-02-22  0:37                   ` Norbert Preining
2012-02-22  6:58                     ` Emmanuel Grumbach
2012-02-22  8:40                     ` Pekka Enberg
2012-02-22  8:54                       ` Emmanuel Grumbach
2012-02-23  7:06                         ` Pekka Enberg
2012-02-27  8:36                           ` Norbert Preining
2012-02-27 18:01                             ` Emmanuel Grumbach
2012-02-27 22:42                               ` Norbert Preining
2012-03-13 23:39                               ` Norbert Preining
2012-02-22  8:37 ` Pekka Enberg
2012-02-27 10:00 ` Matthew Turnbull

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANUX_P0H_WaWwnpjoBcMpZQY4xH=cbVhAKxWKXmz-HwFMcWS6w@mail.gmail.com' \
    --to=egrumbach@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=preining@logic.at \
    --cc=wey-yi.w.guy@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).