linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Crash in agg-tx.c, with ath9k and lots of STA VIFs.
Date: Mon, 04 Oct 2010 14:38:19 -0700	[thread overview]
Message-ID: <4CAA494B.5000500@candelatech.com> (raw)
In-Reply-To: <AANLkTinGaCAEqGRt_X6hsO8sQx4kKEdNqU8pfi00_1-r@mail.gmail.com>

On 10/04/2010 02:13 PM, Luis R. Rodriguez wrote:
> On Mon, Oct 4, 2010 at 2:12 PM, Luis R. Rodriguez<mcgrof@gmail.com>  wrote:
>> On Mon, Oct 4, 2010 at 12:10 PM, Johannes Berg
>> <johannes@sipsolutions.net>  wrote:
>>> On Mon, 2010-10-04 at 12:04 -0700, Ben Greear wrote:
>>>> On 10/04/2010 12:01 PM, Johannes Berg wrote:
>>>>> On Mon, 2010-10-04 at 11:51 -0700, Ben Greear wrote:
>>>>>> Just in case this seems familiar to anyone...
>>>>>>
>>>>>> IP: [<f8ba74da>] ieee80211_stop_tx_ba_session+0x14/0x84 [mac80211]
>>>>>
>>>>> Do you have debug info that'd point to a code line?
>>>>>
>>>>> I have never heard of this.
>>>>
>>>> I don't actually know how to get a line of code out of those
>>>> hex offsets...
>>>>
>>>> Someone told me many years ago..but I lost that information :P
>>>
>>> Err, I never remember either, I think Luis knows the gdb thing ... I
>>> usually use "objdump -dS"
>>
>> gdb net/mac80211/mac80211.ko
>> l *(ieee80211_stop_tx_ba_session+0x14/0x84)
>
> Oops I meant:
>
> gdb net/mac80211/mac80211.ko
> l *(ieee80211_stop_tx_ba_session+0x14)

Thank!

I had to re-compile with debugging symbols, and added kgdb (hopefully
that won't mess anything up).

Reading symbols from /home/greearb/kernel/2.6/wireless-testing-dbg.p4s/net/mac80211/mac80211.ko...done.
(gdb) l *(ieee80211_stop_tx_ba_session+0x14)
0x54fe is in ieee80211_stop_tx_ba_session (/home/greearb/git/linux.wireless-testing/net/mac80211/agg-tx.c:595).
590	
591	int ieee80211_stop_tx_ba_session(struct ieee80211_sta *pubsta, u16 tid)
592	{
593		struct sta_info *sta = container_of(pubsta, struct sta_info, sta);
594		struct ieee80211_sub_if_data *sdata = sta->sdata;
595		struct ieee80211_local *local = sdata->local;
596		struct tid_ampdu_tx *tid_tx;
597		int ret = 0;
598	
599		trace_api_stop_tx_ba_session(pubsta, tid);


I'm not sure I quite got the hang of kgdb yet, but hoping to get that working
and reproduce with it enabled...

Thanks,
Ben

>
>     Luis


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2010-10-04 21:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 18:51 Crash in agg-tx.c, with ath9k and lots of STA VIFs Ben Greear
2010-10-04 19:01 ` Johannes Berg
2010-10-04 19:04   ` Ben Greear
2010-10-04 19:10     ` Johannes Berg
2010-10-04 21:12       ` Luis R. Rodriguez
2010-10-04 21:13         ` Luis R. Rodriguez
2010-10-04 21:38           ` Ben Greear [this message]
2010-10-04 22:42             ` Ben Greear
2010-10-05  7:56               ` Johannes Berg
2010-10-05 16:24                 ` Ben Greear
2010-10-04 23:48             ` Luis R. Rodriguez
2010-10-05  3:39               ` Ben Greear
2010-10-05  6:09                 ` Luis R. Rodriguez
2010-10-05  3:43               ` Ben Greear

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=4CAA494B.5000500@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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).