From: reinette chatre <reinette.chatre@intel.com>
To: Paul Collins <paul@burly.ondioline.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn: possible regressions from 2.6.29 in 2.6.30
Date: Tue, 30 Jun 2009 09:17:31 -0700 [thread overview]
Message-ID: <1246378651.17896.523.camel@rc-desk> (raw)
In-Reply-To: <874oty9tlf.fsf@bulky.wgtn.ondioline.org>
Hi Paul,
On Mon, 2009-06-29 at 22:30 -0700, Paul Collins wrote:
> Two things I liked about iwlagn in 2.6.29 no longer happen with 2.6.30:
>
> 1. reassociation following resume from suspend-to-ram
> 2. transmission of packets > 250 bytes following resume from suspend-to-ram
>
> I can script around the first problem just by doing "iwconfig wlan0 ap
> auto" on resume, but the second problem requires me to ifdown/ifup wlan0
> before I can usefully use my network again, so fixing the first problem
> doesn't get me very far.
For reliable reassociation you need to use a userspace application like
wpa_supplicant.
>
> When I say "packets > 250 bytes" I mean 250-byte packets as claimed by
> "ping -s 222 mygateway":
>
> PING cornelius.lan (10.2.4.1) 222(250) bytes of data.
>
> The above will work, but "ping -s 223 cornelius" yields no replies.
Are you saying this works before suspend, but not after resume? What do
you usually do to get this working again?
Could you please try this patch?
---
drivers/net/wireless/iwlwifi/iwl-tx.c | 14 +++++++++-----
1 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/net/wireless/iwlwifi/iwl-tx.c b/drivers/net/wireless/iwlwifi/iwl-tx.c
index 753fca3..3f3147e 100644
--- a/drivers/net/wireless/iwlwifi/iwl-tx.c
+++ b/drivers/net/wireless/iwlwifi/iwl-tx.c
@@ -873,7 +876,8 @@ int iwl_tx_skb(struct iwl_priv *priv, struct sk_buff *skb)
iwl_print_hex_dump(priv, IWL_DL_TX, (u8 *)tx_cmd->hdr, hdr_len);
/* Set up entry for this TFD in Tx byte-count array */
- priv->cfg->ops->lib->txq_update_byte_cnt_tbl(priv, txq,
+ if (info->flags & IEEE80211_TX_CTL_AMPDU)
+ priv->cfg->ops->lib->txq_update_byte_cnt_tbl(priv, txq,
le16_to_cpu(tx_cmd->len));
pci_dma_sync_single_for_device(priv->pci_dev, txcmd_phys,
--
1.5.6.3
next prev parent reply other threads:[~2009-06-30 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 5:30 iwlagn: possible regressions from 2.6.29 in 2.6.30 Paul Collins
2009-06-30 16:17 ` reinette chatre [this message]
2009-06-30 21:53 ` Paul Collins
2009-07-04 6:39 ` Paul Collins
2009-08-03 21:08 ` reinette chatre
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=1246378651.17896.523.camel@rc-desk \
--to=reinette.chatre@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=paul@burly.ondioline.org \
/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