From: Jeffrey Baker <jwbaker@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: WARNING at mac80211_ieee80211_rx
Date: Wed, 9 Dec 2009 10:13:18 -0800 [thread overview]
Message-ID: <fd145f7d0912091013o702d1ee2ueb41a97ae43a0f27@mail.gmail.com> (raw)
In-Reply-To: <43e72e890912090918m55d2816co9b04065e91e4d4f1@mail.gmail.com>
On Wed, Dec 9, 2009 at 9:18 AM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 10:03 PM, Jeffrey Baker <jwbaker@gmail.com> wrote:
>> My access point with an AR9220 stopped passing traffic,
>
> Jeffrey, thanks for your report, can you be a little more verbose here
> and elaborate as to what you mean by this? Do you mean that you stop
> hostapd or that it hostapd is still running and that somehow you
> notice it stops sending data between its associated STAs?
Yes, hostapd was still running, however stations were unable to pass
traffic. Actually the AP also stopped sending beacons I think,
because the AP no longer appeared in scans. Restarting hostapd had no
effect. I rebooted the machine.
>
>> and these were
>> seen in dmesg. I am using compat-wireless 2009-11-06.
>>
>> also at pastebin: http://pastebin.com/m527862e9
>>
>> [505869.263259] ------------[ cut here ]----------- -
>> [505869.269520] WARNING: at
>> /root/compat-wireless-2009-11-06/net/mac80211/rx.c:2486
>
> This would be from:
>
> /*
> * The same happens when we're not even started,
> * but that's worth a warning.
> */
> if (WARN_ON(!local->started))
> goto drop
>
> So somehow the RX tasklet kicked in and ath9k RX engine was still running.
next prev parent reply other threads:[~2009-12-09 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 6:03 WARNING at mac80211_ieee80211_rx Jeffrey Baker
2009-12-09 17:18 ` Luis R. Rodriguez
2009-12-09 18:13 ` Jeffrey Baker [this message]
2009-12-09 18:22 ` Luis R. Rodriguez
[not found] ` <fd145f7d0912091036o2a38a028p686f791744de0ae3@mail.gmail.com>
2009-12-09 18:41 ` Luis R. Rodriguez
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=fd145f7d0912091013o702d1ee2ueb41a97ae43a0f27@mail.gmail.com \
--to=jwbaker@gmail.com \
--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).