From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: linux-kernel@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net, "Guy,
Wey-Yi" <wey-yi.w.guy@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
Dave Jones <davej@redhat.com>
Subject: Re: iwlagn is getting even worse with 3.3-rc1
Date: Thu, 26 Jan 2012 16:06:36 -0800 [thread overview]
Message-ID: <CANUX_P0z2800ip=yfW15zELqhDNFrHbTvDY3OF59PuxizN=XSA@mail.gmail.com> (raw)
In-Reply-To: <20120126232555.GB16330@gamma.logic.tuwien.ac.at>
On Thu, Jan 26, 2012 at 15:25, Norbert Preining <preining@logic.at> wrote:
> Hi Emmanuel,
>
> On Do, 26 Jan 2012, Emmanuel Grumbach wrote:
>> are suffering from the same issue. I am merging the mail threads here.
>
> First tests are promising, after reboot it was working immediately
> without need to rfkill block/unblock. lso after suspend and resume.
>
> Will test more the next days and report back.
>
> dmesg output without debugging still the same, but connection
> continues without any problem:
> [ 62.437916] Open BA session requested for 00:0a:79:eb:56:10 tid 0
> [ 62.456184] activated addBA response timer on tid 0
> [ 63.456042] addBA response timer expired on tid 0
> [ 63.456063] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
> [ 67.008297] switched off addBA timer for tid 0
> [ 67.008305] got addBA resp for tid 0 but we already gave up
> [ 67.008340] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
> [ 67.015503] Open BA session requested for 00:0a:79:eb:56:10 tid 0
> [ 67.031648] activated addBA response timer on tid 0
> [ 67.129907] switched off addBA timer for tid 0
> [ 67.129914] Aggregation is on for tid 0
> [ 67.130076] iwlwifi 0000:06:00.0: Tx aggregation enabled on ra = 00:0a:79:eb:56:10 tid = 0
> [ 100.288018] tx session timer expired on tid 0
> [ 100.288032] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
> [ 106.347302] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
> [ 106.374760] Open BA session requested for 00:0a:79:eb:56:10 tid 0
> [ 106.388178] activated addBA response timer on tid 0
> [ 106.390041] switched off addBA timer for tid 0
> [ 106.390044] Aggregation is on for tid 0
> [ 106.390193] iwlwifi 0000:06:00.0: Tx aggregation enabled on ra = 00:0a:79:eb:56:10 tid = 0
> [ 135.786765] Open BA session requested for 00:0a:79:eb:56:10 tid 6
> [ 135.804164] activated addBA response timer on tid 6
> [ 135.806088] switched off addBA timer for tid 6
> [ 135.806092] Aggregation is on for tid 6
> [ 135.806241] iwlwifi 0000:06:00.0: Tx aggregation enabled on ra = 00:0a:79:eb:56:10 tid = 6
> [ 146.912031] tx session timer expired on tid 6
> [ 146.912071] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 6
> [ 146.924187] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 6
> [ 256.560100] tx session timer expired on tid 0
> [ 256.560132] Tx BA session stop requested for 00:0a:79:eb:56:10 tid 0
> [ 256.584379] Stopping Tx BA session for 00:0a:79:eb:56:10 tid 0
> [ 258.477345] Open BA session requested for 00:0a:79:eb:56:10 tid 0
> [ 258.500189] activated addBA response timer on tid 0
> [ 258.502148] switched off addBA timer for tid 0
> [ 258.502151] Aggregation is on for tid 0
> [ 258.502340] iwlwifi 0000:06:00.0: Tx aggregation enabled on ra = 00:0a:79:eb:56:10 tid = 0
>
> Later on after resume I got a few hickups but the connection just
> hang for a shor ttime, then came back:
> [ 589.895086] delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
> [ 589.895095] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
> [ 589.900879] Rx A-MPDU request on tid 0 result 0
> [ 589.900950] unexpected AddBA Req from 00:0a:79:eb:56:10 on tid 0
> [ 589.900958] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
> [ 589.902649] Rx A-MPDU request on tid 0 result 0
> [ 589.902690] unexpected AddBA Req from 00:0a:79:eb:56:10 on tid 0
> [ 589.902698] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
> [ 589.903732] Rx A-MPDU request on tid 0 result 0
> [ 589.903810] unexpected AddBA Req from 00:0a:79:eb:56:10 on tid 0
> [ 589.903817] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
> [ 589.904965] Rx A-MPDU request on tid 0 result 0
> [ 589.905045] unexpected AddBA Req from 00:0a:79:eb:56:10 on tid 0
> [ 589.905053] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 recipient reason: 32
> [ 589.906510] Rx A-MPDU request on tid 0 result 0
> [ 590.456062] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
> [ 590.456075] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
> [ 590.456083] ieee80211 phy0: release an RX reorder frame due to timeout on earlier frames
> [ 594.413810] delba from 00:0a:79:eb:56:10 (initiator) tid 0 reason code 39
> [ 594.413822] Rx BA session stop requested for 00:0a:79:eb:56:10 tid 0 inititator reason: 0
> [ 594.428073] Rx A-MPDU request on tid 0 result 0
>
>
> Generally fine.
>
> Thanks, more reports later.
>
Dave ?
next prev parent reply other threads:[~2012-01-27 0:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 1:36 iwlagn is getting even worse with 3.3-rc1 Norbert Preining
2012-01-24 4:47 ` Emmanuel Grumbach
2012-01-25 0:22 ` Norbert Preining
2012-01-25 5:32 ` Emmanuel Grumbach
2012-01-26 0:37 ` Norbert Preining
2012-01-26 5:49 ` Emmanuel Grumbach
2012-01-26 21:13 ` Emmanuel Grumbach
2012-01-26 23:25 ` Norbert Preining
2012-01-27 0:06 ` Emmanuel Grumbach [this message]
2012-01-31 2:41 ` Dave Jones
2012-02-01 15:43 ` Dave Jones
2012-02-01 14:45 ` Guy, Wey-Yi
2012-01-27 1:50 ` Norbert Preining
2012-01-27 3:11 ` Emmanuel Grumbach
2012-02-22 0:37 ` Norbert Preining
2012-02-22 6:58 ` Emmanuel Grumbach
2012-02-22 8:40 ` Pekka Enberg
2012-02-22 8:54 ` Emmanuel Grumbach
2012-02-23 7:06 ` Pekka Enberg
2012-02-27 8:36 ` Norbert Preining
2012-02-27 18:01 ` Emmanuel Grumbach
2012-02-27 22:42 ` Norbert Preining
2012-03-13 23:39 ` Norbert Preining
2012-02-22 8:37 ` Pekka Enberg
2012-02-27 10:00 ` Matthew Turnbull
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='CANUX_P0z2800ip=yfW15zELqhDNFrHbTvDY3OF59PuxizN=XSA@mail.gmail.com' \
--to=egrumbach@gmail.com \
--cc=davej@redhat.com \
--cc=ilw@linux.intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=preining@logic.at \
--cc=wey-yi.w.guy@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).