linux-kernel - Re: ath9k_htc: Every 2nd packet 1000ms delayed in recent kernels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Jun 2012 00:33:15 +0200
From:	Michael Leun <lkml20120218@...ton.leun.net>
To:	Mohammed Shafi <shafi.wireless@...il.com>
Cc:	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ath9k_htc: Every 2nd packet 1000ms delayed in recent kernels

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

> Hi,
> 
> On Tue, Jun 19, 2012 at 12:21 PM, Michael Leun
> <lkml20120218@...ton.leun.net> wrote:
> > Hi,
> >
> > ne-wlan1@...ktra:/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@...el.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@...el.com>
    Signed-off-by: John W. Linville <linville@...driver.com>

:040000 040000 67a19a39e4b04c16921a3758ddd2362e02e81dd3 4a7cbd327b59345b83fa613f893770fbf44220bb M      net

Reverting 0775f9f90cdaf40fbf69b3192b3dddb2b3436f45 from 3.4.3 fixes the issue.


-- 
MfG,

Michael Leun

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/