From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
Norbert Preining <preining@logic.at>,
linux-kernel@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: iwlagn is getting even worse with 3.3-rc1
Date: Wed, 01 Feb 2012 06:45:55 -0800 [thread overview]
Message-ID: <1328107555.7290.13.camel@wwguy-huron> (raw)
In-Reply-To: <20120201154335.GA8494@redhat.com>
On Wed, 2012-02-01 at 10:43 -0500, Dave Jones wrote:
> On Mon, Jan 30, 2012 at 09:41:43PM -0500, Dave Jones wrote:
>
> > > > Generally fine.
> > > >
> > > > Thanks, more reports later.
> > >
> > > Dave ?
> >
> > after running with it all evening, it seems to be working fine so far.
>
> Two days later, it hasn't locked up at all, so this is definitly fixing my problem.
>
> One thing though, dmesg is flooded with these..
>
> [ 4384.849732] iwlwifi 0000:04:00.0: Tx aggregation enabled on ra = b8:c7:5d:0c:39:87 tid = 0
> [ 4434.332275] iwlwifi 0000:04:00.0: Tx aggregation enabled on ra = b8:c7:5d:0c:39:87 tid = 0
> [ 4475.309883] iwlwifi 0000:04:00.0: Tx aggregation enabled on ra = b8:c7:5d:0c:39:87 tid = 0
>
> Can it be supressed if the ra hasn't changed ?
John has a patch to fix this :-)
Wey
>
next prev parent reply other threads:[~2012-02-01 15:53 UTC|newest]
Thread overview: 24+ 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 [this message]
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
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=1328107555.7290.13.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=davej@redhat.com \
--cc=egrumbach@gmail.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 \
/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).