From: Lars Schotte <gusto@guttok.net>
To: wwguy <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlagn 3.0.9 aggreggation messages
Date: Mon, 14 Nov 2011 22:18:47 +0100 [thread overview]
Message-ID: <20111114221847.2ca32e6a@hana.gusto> (raw)
In-Reply-To: <1321303101.1796.8.camel@wwguy-ubuntu>
of course he deactivates the aggregation soon after, because the AP
sees no reason why there should be one.
triggering the aggreggation is that problem and it exists only since
3.0.9. 3.0.8 is OK, but 3.1.1 seems to be affected as well. 3.1.0 was
OK.
so someting broke it recently.
unfortunately i can not remember if 3.2 kernel had that problem, i
already removed it because it was too unstable for me, so i can not
test it any more (w/o compiling it again).
On Mon, 14 Nov 2011 12:38:21 -0800
wwguy <wey-yi.w.guy@intel.com> wrote:
> Hi Schotte,
>
> looks like driver has problem activate the aggregation, you can see in
> the log, the aggregation queue being activate then deactivate soon
> after. that is why you are seeing the messages showing up in dmesg
> log.
>
> what AP you are using? is similar thing happen if you connect to
> different AP?
>
> Thanks
> Wey
--
Lars Schotte
@ Hana (F16)
next prev parent reply other threads:[~2011-11-14 21:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 12:16 iwlagn 3.0.9 aggreggation messages Lars Schotte
2011-11-14 15:10 ` wwguy
2011-11-14 19:19 ` Lars Schotte
2011-11-14 20:38 ` wwguy
2011-11-14 21:13 ` Lars Schotte
2011-11-14 21:18 ` Lars Schotte [this message]
2011-11-14 21:22 ` wwguy
2011-11-14 21:47 ` Lars Schotte
2011-11-14 21:44 ` wwguy
2011-11-14 22:05 ` Lars Schotte
2011-11-14 22:28 ` Lars Schotte
2011-11-14 22:41 ` wwguy
2011-11-14 22:56 ` Lars Schotte
2011-11-14 22:59 ` wwguy
2011-11-14 23:16 ` Lars Schotte
2011-11-14 23:17 ` wwguy
2011-11-14 23:30 ` Lars Schotte
2011-11-14 23:31 ` wwguy
2011-11-14 23:58 ` Lars Schotte
2011-11-14 22:29 ` Lars Schotte
2011-11-14 21:27 ` wwguy
2011-11-14 21:50 ` Lars Schotte
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=20111114221847.2ca32e6a@hana.gusto \
--to=gusto@guttok.net \
--cc=linux-wireless@vger.kernel.org \
--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