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 not working well
Date: Tue, 27 Mar 2012 18:50:20 +0200 [thread overview]
Message-ID: <4F71EFCC.5030300@broadcom.com> (raw)
On 03/27/2012 04:53 PM, Naveen Goswamy wrote:
> 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?
Starting a new thread (I hope)
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 reply other threads:[~2012-03-27 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 16:50 Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-27 13:55 [PATCH 0/3] trivial changes preparing mac80211 for multi-channel Michal Kazior
2012-03-27 13:55 ` [PATCH 3/3] mac80211: prepare ieee80211_*_duration to per-vif Michal Kazior
2012-03-27 14:53 ` brcmsmac not working well Naveen Goswamy
2012-03-27 15:08 ` Johannes Berg
2012-02-29 18:21 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=4F71EFCC.5030300@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).