Linux wireless drivers development
 help / color / mirror / Atom feed
From: Michael Leun <lkml20120218@newton.leun.net>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ath9k_htc: Every 2nd packet 1000ms delayed in recent kernels
Date: Wed, 20 Jun 2012 00:33:15 +0200	[thread overview]
Message-ID: <20120620003315.2eaf6460@xenia.leun.net> (raw)
In-Reply-To: <CAD2nsn1b6in_yA1b+o=SoXD3iJPddoF4PeCQ3qhFNWqfZxq8pQ@mail.gmail.com>

On Tue, 19 Jun 2012 15:11:38 +0530
Mohammed Shafi <shafi.wireless@gmail.com> wrote:

> Hi,
> 
> On Tue, Jun 19, 2012 at 12:21 PM, Michael Leun
> <lkml20120218@newton.leun.net> wrote:
> > Hi,
> >
> > ne-wlan1@elektra:/home/ml4> ping 192.168.2.1
> > PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
> > 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=2010 ms
> > 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1011 ms
> > 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=11.5 ms
> > 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=1.12 ms
> > 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=1002 ms
> > 64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=3.83 ms
> > 64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=1003 ms
> > 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=4.10 ms
> > 64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=1003 ms
> > 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.95 ms
> > 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=1003 ms
> > 64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=3.78 ms
> >
> >
> > Please note the additional delay of ~1000ms every 2nd packet. This
> > is Kernel 3.4.3, have seen it in 3.4.2 also. Does NOT happen in
> > 3.3.1.
> >
> > Is this Issue already known? If so, I can save the work bisecting...
> 
> looks like some one reported this bug in kernel bugzilla. would be
> saving us lot of time
> if you can bisect it!
> 

0775f9f90cdaf40fbf69b3192b3dddb2b3436f45 is the first bad commit
commit 0775f9f90cdaf40fbf69b3192b3dddb2b3436f45
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Thu Mar 8 15:02:06 2012 +0100

    mac80211: remove spurious BSSID change flag

    The BSSID has been set a lot earlier already and
    didn't change again in ieee80211_set_associated().

    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

:040000 040000 67a19a39e4b04c16921a3758ddd2362e02e81dd3 4a7cbd327b59345b83fa613f893770fbf44220bb M      net

Reverting 0775f9f90cdaf40fbf69b3192b3dddb2b3436f45 from 3.4.3 fixes the issue.


-- 
MfG,

Michael Leun


  reply	other threads:[~2012-06-19 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  6:51 ath9k_htc: Every 2nd packet 1000ms delayed in recent kernels Michael Leun
2012-06-19  9:41 ` Mohammed Shafi
2012-06-19 22:33   ` Michael Leun [this message]
2012-06-20  6:13     ` Rajkumar Manoharan
2012-06-20  6:15       ` Michael Leun
2012-06-20  6:20         ` Rajkumar Manoharan
2012-06-20  6:55       ` Michael Leun
2012-06-20  7:12         ` Rajkumar Manoharan

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=20120620003315.2eaf6460@xenia.leun.net \
    --to=lkml20120218@newton.leun.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shafi.wireless@gmail.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