From: Michael Kaminsky <kaminsky@csail.mit.edu>
To: linux-wireless@vger.kernel.org
Cc: Jouni Malinen <jouni.malinen@atheros.com>
Subject: phy0: release an RX reorder frame due to timeout on earlier frames
Date: Tue, 01 Sep 2009 16:05:13 -0400 [thread overview]
Message-ID: <4A9D7E79.6090000@csail.mit.edu> (raw)
I'm running a git checkout of iwlwifi-2.6.git from around Aug. 10
(d229b68..). I filed a bug report at
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2076
and I was asked to post my situation to this list.
I'm seeing regular "outages" when using 11n where no packets seem to go
through (card is an Intel 5300). When this happens, I see the following
in my dmesg output:
phy0: release an RX reorder frame due to timeout on earlier frames
(To see this message, you need to compile with CONFIG_MAC80211_HT_DEBUG.
The message comes from net/mac80211/rx.c.)
There's dmesg log attached to the above bug report which gives a
high-level picture (no extra debugging) of what happens. I associate
(with HT), things work for a little while, and then this message is
printed out (at which point the network stops working). If I manually
re-associate, things work again. If I do nothing, eventually the driver
re-associates by itself, and things also work again. Letting the driver
re-associate automatically, though, can take a while (e.g, sometimes
close to a minute). Note that in my environment, there are multiple APs
serving the same ESSID. This error seems to happen quite regularly.
Thanks,
Michael
next reply other threads:[~2009-09-01 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 20:05 Michael Kaminsky [this message]
2009-09-01 21:41 ` phy0: release an RX reorder frame due to timeout on earlier frames Gábor Stefanik
2009-09-02 14:32 ` Michael Kaminsky
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=4A9D7E79.6090000@csail.mit.edu \
--to=kaminsky@csail.mit.edu \
--cc=jouni.malinen@atheros.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).