From: Christian Lamparter <chunkeey@googlemail.com>
To: Blaise Gassend <blaise@willowgarage.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: General protection fault in ieee80211_stop_tx_ba_sessions
Date: Sat, 16 Oct 2010 00:37:06 +0200 [thread overview]
Message-ID: <201010160037.06949.chunkeey@googlemail.com> (raw)
In-Reply-To: <AANLkTimqNvJ=93NA_s_p3Ype9pYey2+YS0zO0r9TZKd=@mail.gmail.com>
On Saturday 16 October 2010 00:20:19 Blaise Gassend wrote:
> I have been getting a general protection fault in
> ieee80211_stop_tx_ba_sessions. This mostly seems to happen within a
> few tens of seconds of bringing the interface up.
>
> I am pasting a backtrace and system information below below. What
> other information would be useful to help track this down?
>
> Kernel:
> Linux version 2.6.32-24-generic (buildd@crested) (gcc version 4.4.3
> (Ubuntu 4.4.3-4ubuntu5) ) #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010
>
> Wireless:
> compat-wireless-2010-10-04
please update, because it looks like your problem could be fixed by:
"mac80211: delete AddBA response timer" (2010-10-05)
http://www.spinics.net/lists/linux-wireless/msg56886.html
> Backtrace (Keeps spewing for a really long time, I can provide more if
> necessary):
> general protection fault: 0000 [#1] SMP
> RIP: 0010:[<xyz>] [<xyz>] ieee80211_stop_tx_ba_session+0x35/0xd0 [mac80211]
> Process swapper (pid: 0, threadinfo ffff88013392e000,
> Call Trace:
> <IRQ>
> [<81019e69>] ? sched_clock+0x9/0x10
> [<a0120a40>] ? sta_addba_resp_timer_expired+0x0/0x50 [mac80211] <<<
> [<a0120a87>] ? sta_addba_resp_timer_expired+0x47/0x50 [mac80211]
> [<8107776b>] ? run_timer_softirq+0x19b/0x340
> [<812b92bd>] ? rb_insert_color+0x9d/0x160
> [<8108f723>] ? ktime_get+0x63/0xe0
next prev parent reply other threads:[~2010-10-16 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 22:20 General protection fault in ieee80211_stop_tx_ba_sessions Blaise Gassend
2010-10-15 22:37 ` Christian Lamparter [this message]
2010-10-16 0:21 ` Blaise Gassend
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=201010160037.06949.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=blaise@willowgarage.com \
--cc=linux-wireless@vger.kernel.org \
/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).