From: Norbert Preining <preining@logic.at>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Venkataraman, Meenakshi" <meenakshi.venkataraman@intel.com>,
"Lin, Hsien KuoX" <hsien.kuox.lin@intel.com>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Emmanuel Grumbach <egrumbach@gmail.com>
Subject: Re: [Ilw] Re: 3.4-rc2, ilwagn still most of the time completely unusable
Date: Wed, 25 Jul 2012 12:07:31 +0900 [thread overview]
Message-ID: <20120725030731.GB8504@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <1342109807.4531.38.camel@jlt3.sipsolutions.net>
Hi Johannes,
Sorry for the late reply, I was travelling around the world ...
I have now tested the =2 and =4 settings at home, with the following
outcome:
On Do, 12 Jul 2012, Johannes Berg wrote:
> With the latest, I've extended 11n_disable to have more bits.
>
> 11n_disable=1 will disable HT completely
> 11n_disable=2 will disable TX aggregation
> 11n_disable=4 will disable RX aggregation
11n_disabled=2:
lots of messages
Open BA session requested for 00:0a:79:eb:56:10 tid 0
BA request denied - HW unavailable for tid 0
and
Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
Rx A-MPDU request on tid 0 result 0
Connection is stable for quite some time, but after 1-2 hours I got
a bad hang, grinding to a halt. pings to kernel.org gives 26%
packet loss, but the rest of the packets are fast 130ms
(Isn't that a strange thing - 25+% packet loss and all others are fast?)
I assume the packaet loss is related to the above messages.
11n_disabled=4:
lots of messages
Rx A-MPDU request on tid 0 result -22
and at some point ping timeouts of 80+ secs (!) and then total hang
(as far as I remember)
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
PERRANZABULOE (n.)
One of those spray things used to wet ironing with.
--- Douglas Adams, The Meaning of Liff
next prev parent reply other threads:[~2012-07-25 3:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 1:17 iwlagn (3.3-wl), the saga continuous Norbert Preining
2012-04-11 2:37 ` 3.4-rc2, ilwagn still most of the time completely unusable Norbert Preining
2012-04-11 2:54 ` David Miller
2012-04-11 18:40 ` Ted Ts'o
2012-04-11 20:01 ` Dave Jones
2012-04-11 23:01 ` Norbert Preining
2012-04-11 23:24 ` Venkataraman, Meenakshi
2012-04-12 0:02 ` Norbert Preining
2012-04-13 1:32 ` Venkataraman, Meenakshi
2012-04-13 1:40 ` Norbert Preining
[not found] ` <59083F8344AE164EB150C0518405C0680E0F285C@FMSMSX107.amr.corp.intel.com>
2012-06-28 7:25 ` Norbert Preining
2012-06-28 7:51 ` [Ilw] " Johannes Berg
2012-06-28 8:16 ` Norbert Preining
2012-07-03 19:35 ` Alessandro Suardi
2012-07-12 8:14 ` Norbert Preining
2012-07-12 16:16 ` Johannes Berg
2012-07-25 3:07 ` Norbert Preining [this message]
2012-04-13 5:38 ` Norbert Preining
2012-04-25 1:06 ` Venkataraman, Meenakshi
2012-04-26 0:51 ` Norbert Preining
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=20120725030731.GB8504@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=egrumbach@gmail.com \
--cc=hsien.kuox.lin@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meenakshi.venkataraman@intel.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).