From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Norbert Preining <preining@logic.at>
Cc: Pekka Enberg <penberg@kernel.org>,
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: Mon, 27 Feb 2012 20:01:11 +0200 [thread overview]
Message-ID: <CANUX_P2jtrByqAJTAZDu-+5Nx-cYFKiO8Hkhepg7rDbEmNwfJQ@mail.gmail.com> (raw)
In-Reply-To: <20120227083612.GA5648@gamma.logic.tuwien.ac.at>
> sorry for the silence, I wasn't at the university for a few days so
> I couldn't test.
>
> Now I did:
> kernel 3.3-rc5
>
> On Mi, 22 Feb 2012, Emmanuel Grumbach wrote:
>> From the log, I can see that we have a lot of "passive channel
>> failures". Can you try to disable 11n (module_parameter) ?
>> Please also try with debug=0xc0000000
So this doesn't seem to be related to my rework of the AMPDU logic....
Will keep you updated if I think about something.
next prev parent reply other threads:[~2012-02-27 18:01 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
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 [this message]
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_P2jtrByqAJTAZDu-+5Nx-cYFKiO8Hkhepg7rDbEmNwfJQ@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=penberg@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).