All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Jack Lau <jackelectronics@hotmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: kernel panic ieee80211_agg_splice_packets+0x3d/0xc0 [mac80211]
Date: Sun, 26 Jul 2009 16:40:16 -0400	[thread overview]
Message-ID: <1248640816.32168.42.camel@mj> (raw)
In-Reply-To: <BAY0-DP2-2945C3011C834624418944BD170@phx.gbl>

On Sun, 2009-07-26 at 17:35 +0000, Jack Lau wrote:
>  
> This is my very first post on a public mailing list where I am not
> into programming.  I just set up and configure Linux but have very
> little experience with programing except BASIC and shell scripting.
>  
> I have recently assembled a Linux server and router (no GUI) where I
> am using an Atheros AR9160 controller (Sparklan WMIA-268N) as an
> access point.  I am using Ubuntu 9.04 jaunty release but using hostapd
> 0.69 from the upcoming 9.10 karmic release because the one that comes
> with jaunty does not support nl80211.
>  
> The problem is that I am constantly getting kernel panics, each time
> of the same error kernel panic ieee80211_agg_splice_packets+0x3d/0xc0
> [mac80211]

You can find where it happens if you kernel is compiled with the debug
information (CONFIG_DEBUG_INFO in .config).  Load the mac80211 module in
gdb:

gdb /lib/modules/`uname -r`/kernel/net/mac80211/mac80211.ko

On the gdb prompt, run:

l *(ieee80211_agg_splice_packets+0x3d)

Actually, ieee80211_agg_splice_packets is a short function.  Perhaps you
could add debug print statements to find possible errors.  For instance,
local->hw is used.  It would crash if local is NULL.  So you add before
that place:

printk("local = %p\n", local);

Likewise, check sta, sta->ampdu_mlme.tid_tx[tid] and local->pending.  Or
just print the line numbers.  You will see which printk is run last
before the crash.

> I enclose screenshots of 3 occurrences, the last occurrence with the
> options nosmp noacpi acpi=off noapic just to see if it solves the
> problem but it didn't.  Most frustratingly, I hate it when I am the
> only person experiencing it because searching Google yields nothing
> with this error.

Chances are it's because 802.11n is not used much with ath9k in AP mode.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2009-07-26 20:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-26 17:35 kernel panic ieee80211_agg_splice_packets+0x3d/0xc0 [mac80211] Jack Lau
2009-07-26 20:40 ` Pavel Roskin [this message]
2009-07-28 21:21   ` Jack Lau
2009-07-28 22:48     ` Pavel Roskin
2009-07-30 22:48       ` Jack Lau
2009-07-31 14:26       ` Jack Lau
     [not found]       ` <SNT102-W3823D5AFC70CB052684837BD110@phx.gbl>
2009-08-02  4:18         ` Pavel Roskin
2009-08-02 12:55       ` Jack Lau
2009-08-02 12:57       ` Jack Lau
2009-08-05 19:23       ` Jack Lau
2009-08-02 17:26   ` Jack Lau

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=1248640816.32168.42.camel@mj \
    --to=proski@gnu.org \
    --cc=jackelectronics@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.