linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: Arend van Spriel <arend@broadcom.com>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	Brett Rudley <brudley@broadcom.com>,
	Roland Vossen <rvossen@broadcom.com>,
	Kan Yan <kanyan@broadcom.com>,
	brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH v2 00/22] brcmsmac: Tx rework and expanded debug/trace support
Date: Tue, 20 Nov 2012 23:45:06 +0100	[thread overview]
Message-ID: <50AC07F2.8000400@monom.org> (raw)
In-Reply-To: <50AC05A5.3090706@monom.org>

>> Looks like you got it right. The period you traced doesn't seem to cover
>> any of the block ack session timeouts, but I do see this:
>>
>> [  225.269777] wlan0: release an RX reorder frame due to timeout on earlier frames
>> [  243.869220] wlan0: unexpected AddBA Req from 1c:c6:3c:1f:50:68 on tid 0
>> [  243.869233] wlan0: Rx BA session stop requested for 1c:c6:3c:1f:50:68 tid 0 recipient reason: 32
>> [  243.869250] wlan0: Rx A-MPDU request on tid 0 result 0
>> [  252.254013] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppressed, illegal channel possibly 13
>> <snip repeated messages>
>> [  259.798966] wlan0: release an RX reorder frame due to timeout on earlier frames
>> <snip repeated messages>
>> [  265.193640] wlan0: unexpected AddBA Req from 1c:c6:3c:1f:50:68 on tid 0
>> [  265.193648] wlan0: Rx BA session stop requested for 1c:c6:3c:1f:50:68 tid 0 recipient reason: 32
>> [  265.193663] wlan0: Rx A-MPDU request on tid 0 result 0
>>
>> Does something in this time frame correspond to your loss in
>> connectivity? The number of packets being sent and received varies some
>> throughout the trace but generally stays pretty low. It never completely
>> stops though.
>
> I am currently not able to reproduce a complete loss of connectivity.

I fear it is a heisenbug. After turning the tracing off I was able to 
reproduce it very easily.



  reply	other threads:[~2012-11-20 22:45 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 14:07 [PATCH v2 00/22] brcmsmac: Tx rework and expanded debug/trace support Seth Forshee
2012-11-15 14:07 ` [PATCH v2 01/22] brcmsmac: Introduce AMPDU sessions for assembling AMPDUs Seth Forshee
2012-11-16  8:36   ` Arend van Spriel
2012-11-16 14:12     ` Seth Forshee
2012-11-16 15:02       ` Arend van Spriel
2012-11-16 15:18         ` Seth Forshee
2012-11-19 18:33   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 02/22] brcmsmac: Don't weight AMPDU packets in txfifo Seth Forshee
2012-11-19 18:34   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 03/22] brcmsmac: Add helper function for updating txavail count Seth Forshee
2012-11-19 18:35   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 04/22] brcmsmac: Remove unimplemented flow control functions Seth Forshee
2012-11-19 18:35   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 05/22] brcmsmac: Use IEEE 802.11 AC levels for pktq precedence levels Seth Forshee
2012-11-19 18:42   ` Arend van Spriel
2012-11-19 19:16     ` Seth Forshee
2012-11-19 20:50       ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 06/22] brcmsmac: Remove internal tx queue Seth Forshee
2012-11-19 18:47   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 07/22] brcmsmac: Use correct descriptor count when calculating next rx descriptor Seth Forshee
2012-11-15 14:07 ` [PATCH v2 08/22] brcmsmac: Reduce number of entries in tx DMA rings Seth Forshee
2012-11-19 18:47   ` Arend van Spriel
2012-11-15 14:07 ` [PATCH v2 09/22] brcm80211: Allow trace support to be enabled separately from debug Seth Forshee
2012-11-19 20:33   ` Arend van Spriel
2012-11-19 21:15     ` Seth Forshee
2012-11-19 21:19       ` Arend van Spriel
2012-11-19 21:33         ` Seth Forshee
2012-11-27 16:22           ` Seth Forshee
2012-11-15 14:08 ` [PATCH v2 10/22] brcm80211: Convert log message levels to debug levels Seth Forshee
2012-11-15 14:08 ` [PATCH v2 11/22] brcmsmac: Add module parameter for setting the debug level Seth Forshee
2012-11-19 20:35   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 12/22] brcmsmac: Add support for writing debug messages to the trace buffer Seth Forshee
2012-11-19 20:35   ` Arend van Spriel
2012-11-22 13:42     ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 13/22] brcmsmac: Use debug macros for general error and debug statements Seth Forshee
2012-11-15 14:08 ` [PATCH v2 14/22] brcmsmac: Add brcms_dbg_mac80211() debug macro Seth Forshee
2012-11-19 20:36   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 15/22] brcmsmac: Add rx and tx debug macros Seth Forshee
2012-11-19 20:37   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 16/22] brcmsmac: Add brcms_dbg_int() debug macro Seth Forshee
2012-11-19 20:37   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 17/22] brcmsmac: Add brcms_dbg_dma() " Seth Forshee
2012-11-19 20:38   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 18/22] brcmsmac: Add brcms_dbg_ht() " Seth Forshee
2012-11-19 20:39   ` Arend van Spriel
2012-11-15 14:08 ` [PATCH v2 19/22] brcmsmac: Improve tx trace and debug support Seth Forshee
2012-11-15 14:08 ` [PATCH v2 20/22] brcmsmac: Add tracepoint for macintstatus Seth Forshee
2012-11-15 14:08 ` [PATCH v2 21/22] brcmsmac: Add tracepoint for AMPDU session information Seth Forshee
2012-11-15 14:08 ` [PATCH v2 22/22] brcmsmac: Remove some noisy and uninformative debug messages Seth Forshee
2012-11-15 19:47 ` [PATCH v2 00/22] brcmsmac: Tx rework and expanded debug/trace support Arend van Spriel
2012-11-19 19:11 ` Daniel Wagner
2012-11-20  7:30   ` Daniel Wagner
2012-11-20 14:28     ` Seth Forshee
2012-11-20 17:44       ` Daniel Wagner
2012-11-20 20:54         ` Seth Forshee
2012-11-20 22:35           ` Daniel Wagner
2012-11-20 22:45             ` Daniel Wagner [this message]
2012-11-21  9:44               ` Arend van Spriel
2012-11-21  9:56                 ` Daniel Wagner
2012-11-21 14:35                   ` Seth Forshee
2012-11-21 17:56                     ` Arend van Spriel
2012-11-23  7:32                     ` Daniel Wagner
2012-11-26 19:36                     ` Seth Forshee
2012-11-26 21:20                       ` Daniel Wagner
2012-12-03  8:23                         ` Daniel Wagner
2012-12-03  8:37                           ` Arend van Spriel
2012-12-03 10:15                             ` Daniel Wagner
2012-12-03 17:40                               ` Arend van Spriel
2012-12-04  7:25                                 ` Daniel Wagner
2012-12-05  8:16                                 ` Daniel Wagner
2012-11-20 21:09         ` Arend van Spriel
2012-11-20 21:16           ` Seth Forshee
2012-11-20 21:51             ` Arend van Spriel
2012-11-20 22:36               ` Seth Forshee
2012-11-20 22:35           ` Daniel Wagner
2012-11-19 20:45 ` Arend van Spriel
2012-11-19 21:33   ` Seth Forshee

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=50AC07F2.8000400@monom.org \
    --to=wagi@monom.org \
    --cc=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=kanyan@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rvossen@broadcom.com \
    --cc=seth.forshee@canonical.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).