All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Jim Rees <rees@umich.edu>
Cc: linux-wireless@vger.kernel.org, emmanuel.grumbach@intel.com
Subject: Re: iwlwifi 35% loss rate after v3.16-rc5
Date: Tue, 26 Aug 2014 08:52:40 +0300	[thread overview]
Message-ID: <1409032360.32368.2.camel@dubbel> (raw)
In-Reply-To: <20140826020721.GA1490@umich.edu>

Hi Jim,

On Mon, 2014-08-25 at 22:07 -0400, Jim Rees wrote:
> I've got a Thinkpad x220 with iwlwifi Ultimate-N 6300 AGN. After v3.16-rc5
> it became unusable due to 35% packet loss rate. If I revert these commits,
> it works again:
> 
> dc271ee iwlwifi: mvm: disable CTS to Self
> 43d826c iwlwifi: dvm: don't enable CTS to self
> e48393e iwlwifi: mvm: Fix broadcast filtering
> a42c9fc Revert "iwlwifi: remove IWL_UCODE_TLV_FLAGS_UAPSD_SUPPORT flag"
> b3c063a iwlwifi: update the 7265 series HW IDs
> 8987941 iwlwifi: mvm: rework sched scan channel configuration
> 
> I can bisect further if that would be useful. Dmesg is here:
> http://pastebin.com/wD3UMxUL
> 
> It's still broken in 3.17.0-rc2. Any suggestions?

This is probably the commit that is to blame:

43d826c iwlwifi: dvm: don't enable CTS to self

Could you try again without just that one? If it's confirmed we can
revert that patch.

Also, any chance you can get sniffer logs of the problem?

--
Cheers,
Luca.


  reply	other threads:[~2014-08-26  5:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  2:07 iwlwifi 35% loss rate after v3.16-rc5 Jim Rees
2014-08-26  5:52 ` Luca Coelho [this message]
2014-08-26 11:41   ` Jim Rees
2014-08-26 16:49     ` Luca Coelho
2014-08-26 23:37   ` Jim Rees

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=1409032360.32368.2.camel@dubbel \
    --to=luca@coelho.fi \
    --cc=emmanuel.grumbach@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rees@umich.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.