From: "Arend van Spriel" <arend@broadcom.com>
To: "Naveen Goswamy" <naveen.goswamy@polymtl.ca>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmsmac TCP problems and txop exceeded
Date: Tue, 27 Mar 2012 19:07:49 +0200 [thread overview]
Message-ID: <4F71F3E5.6030105@broadcom.com> (raw)
In-Reply-To: <1332866581.4f71ee152ce84@www.imp.polymtl.ca>
On 03/27/2012 06:43 PM, Naveen Goswamy wrote:
> Hi, this thread should be a continuation of one I started about a month ago and
> can be found here:
>
> http://comments.gmane.org/gmane.linux.kernel.wireless.general/86324
>
> (I lost the header to it and inadvertantly cross posted into another thread, my
> apologies for that)
>
>
>
> So here goes:
>
> I have the BCM4313 [14e4:4727] (rev 01)
>
> When using wireshark, I see that I am getting many {TCP Retransmission,TCP Dup
> ACK,TCP RST} with {TCP, HTTP, SSH} when using brcmsmac driver in the 3.2.1
> kernel. I've tried 3.3-rc5 kernel with similar results.
>
> I notice a lot of these popping up in /var/log/messages as well:
>
> ieee80211 phy0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 155/256 dur
> 1746/1504
> ieee80211 phy0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 130/256 dur
> 1546/1504
> ieee80211 phy0: wl0: brcms_c_d11hdrs_mac80211: txop exceeded phylen 130/256 dur
> 1546/1504
>
>
> any ideas how to solve this?
>
These messages are only indicating (possible) violation of the WMM txop
parameter. So what problem are you looking into here beside the issues
you observe in wireshark. I mean the problem that made you decide to run
wireshark.
Gr. AvS
next prev parent reply other threads:[~2012-03-27 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 16:43 brcmsmac TCP problems and txop exceeded Naveen Goswamy
2012-03-27 17:07 ` Arend van Spriel [this message]
2012-03-27 17:47 ` Naveen Goswamy
2012-03-29 12:07 ` Arend van Spriel
2012-03-29 12:27 ` Naveen Goswamy
2012-03-29 12:38 ` Naveen Goswamy
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=4F71F3E5.6030105@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=naveen.goswamy@polymtl.ca \
/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).