linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath9k-devel <ath9k-devel@lists.ath9k.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH] mac80211: debugfs var for the default aggregation timeout.
Date: Fri, 08 Apr 2016 09:15:46 +0200	[thread overview]
Message-ID: <1460099746.30678.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1460098909.30678.2.camel@sipsolutions.net> (sfid-20160408_090156_026758_0B5986D0)

On Fri, 2016-04-08 at 09:01 +0200, Johannes Berg wrote:
> On Fri, 2016-04-08 at 08:56 +0200, Johannes Berg wrote:
> > 
> > On Thu, 2016-04-07 at 21:32 -0400, Avery Pennarun wrote:
> > 
> > > 
> > > 
> > > Yes.  Here it is:
> > > http://apenwarr.ca/tmp/mac80211-agg-status-crash.ko
> > > 
> > Unfortunately there are no debug symbols in this file, so it
> > doesn't
> > help me much. I can't even seem to get objdump to disassemble it
> > correctly: looks like the file is in thumb, going from things
> > like R_ARM_THM_CALL relocations, but even -Mforce-thumb doesn't
> > seem
> > to DRT; sta_agg_status_read+0xeb isn't even a valid instruction
> > offset in regular ARM mode.
> > 
> It *seems* that it most likely crashes on the first access to tid_tx,
> which is consistent with the story of disabling TX aggregation
> timeouts
> reducing the chances.
> 
> So I guess we have to look for some TX aggregation teardown RCU
> pointer problem?
> 

Can't find anything. The only other thing I saw now is that the TID
appears to be 7 (in r7), might be worth looking for whether that's a
common thing or not?

johannes

  reply	other threads:[~2016-04-08  7:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04  5:03 ath9k(?): AP stops sending traffic to iPhone 4S until another 802.11n-capable STA joins Avery Pennarun
2016-02-16 21:28 ` Avery Pennarun
2016-02-16 21:28   ` [PATCH] mac80211: debugfs var for the default aggregation timeout Avery Pennarun
2016-02-16 21:44     ` Johannes Berg
2016-02-17  2:05     ` Sujith Manoharan
2016-02-23 10:14     ` Johannes Berg
2016-02-23 18:43       ` Avery Pennarun
2016-02-23 20:05         ` Johannes Berg
2016-04-05 23:46           ` Avery Pennarun
2016-04-06  7:40             ` Johannes Berg
2016-04-08  1:32               ` Avery Pennarun
2016-04-08  6:56                 ` Johannes Berg
2016-04-08  7:01                   ` Johannes Berg
2016-04-08  7:15                     ` Johannes Berg [this message]
2016-04-08  8:31                       ` Avery Pennarun
2016-04-09  1:27                         ` Avery Pennarun
2016-04-09  4:56                           ` Johannes Berg
2016-04-10  0:31                             ` Adrian Chadd
2016-04-10  1:59                               ` bruce m beach
2016-04-19  1:29                                 ` Avery Pennarun
2016-02-16 22:05   ` ath9k(?): AP stops sending traffic to iPhone 4S until another 802.11n-capable STA joins Johannes Berg
2016-02-17  4:32     ` Avery Pennarun
2016-02-17  6:23       ` Krishna Chaitanya
2016-02-17  7:05         ` Avery Pennarun

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=1460099746.30678.3.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=apenwarr@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    /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).