From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 18:47:52 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E60C7E53; Sun, 15 Feb 2015 18:47:52 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B11B790C; Sun, 15 Feb 2015 18:47:52 +0000 (UTC) Received: by iecrl12 with SMTP id rl12so27390504iec.4; Sun, 15 Feb 2015 10:47:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=AMdqN7qBYqbyOZ7EY6xklvpQwAco1U0Mtxo91Ptr+UM=; b=rdLwKNaSnIWtc7bakEXsGjqdYb7jPw6tomtXdYdYLFfXFNAhLnVI92lFZS39jqeqAW mLyxOKwkXPzX5RnYyW1X8LqbpD5wOEjjK/TRXlOpsyG/XNrAXFS7JsXRXXpWrCYKIVxe NVSJkDD/ftTcCjdDwgh8t+gb6OQ3Jw7yxiVeOLFEmd79xl4T8QTy0WE/HmcTuatHxd4v qoudtZC+Fp10oh1W5QdB/LgzJsdewVw2VAWJTGXnNmpvU/BQgJIrj1rKHJyK8ZN7kwip GkMfoQxctdqHj17jfj96GJ/FwVW+UrP1wVoMYFMIgTnB62d5HbXYovPhiDk8wqrZsQMo Z9zg== X-Received: by 10.50.142.99 with SMTP id rv3mr17402341igb.11.1424026066124; Sun, 15 Feb 2015 10:47:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Sun, 15 Feb 2015 10:47:25 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sun, 15 Feb 2015 18:47:25 +0000 Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 18:47:53 -0000 On Sat, Feb 14, 2015 at 2:40 AM, Miguel Clara wrote: > > On Sat, Jan 31, 2015 at 7:00 PM, Adrian Chadd wrote: > >> Hi, >> >> please try updating to -HEAD. It's possible that'll fix things. >> > > Hi, > > I've update to head and still see the messages in dmesg. > > And the same slowness... rebooting seems to fix the issue, but it was the > same in 10 and randomly (surely there's a reason only I'm not noticing > what) it goes back to this state. > > Is there any debugging I can try to figure whats going on when this > happens? > Also just now I lost network and saw this in dmesg: ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR ath0: ath_intr: TSFOOR It was just during a few seconds. > >> On 31 January 2015 at 09:19, Miguel Clara wrote: >> > I've just upgrade to the latest 10/stable. >> > >> > trying to git clone a repo was giving me horrible speed, and I honestly >> > tough it was at their side, until I noticed issues while browsing and >> this >> > in dmesg: >> > >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetCTSTimeout: called >> > ar9300_Stub_GetAntennaSwitch: called >> > ar9300_Stub_GetAntennaSwitch: called >> > >> > Speedtest either gives me and ok result or very poor, and pings also >> prove >> > that something is not quite right: >> > 64 bytes from 216.58.210.110: icmp_seq=7 ttl=59 time=18.096 ms >> > 64 bytes from 216.58.210.110: icmp_seq=8 ttl=59 time=149.083 ms >> > 64 bytes from 216.58.210.110: icmp_seq=9 ttl=59 time=18.376 ms >> > 64 bytes from 216.58.210.110: icmp_seq=10 ttl=59 time=19.084 ms >> > 64 bytes from 216.58.210.110: icmp_seq=11 ttl=59 time=18.305 ms >> > 64 bytes from 216.58.210.110: icmp_seq=12 ttl=59 time=18.140 ms >> > 64 bytes from 216.58.210.110: icmp_seq=13 ttl=59 time=16.700 ms >> > 64 bytes from 216.58.210.110: icmp_seq=14 ttl=59 time=105.554 ms >> > 64 bytes from 216.58.210.110: icmp_seq=15 ttl=59 time=34.336 ms >> > 64 bytes from 216.58.210.110: icmp_seq=16 ttl=59 time=76.410 ms >> > 64 bytes from 216.58.210.110: icmp_seq=17 ttl=59 time=34.400 ms >> > 64 bytes from 216.58.210.110: icmp_seq=18 ttl=59 time=73.521 ms >> > 64 bytes from 216.58.210.110: icmp_seq=19 ttl=59 time=154.728 ms >> > 64 bytes from 216.58.210.110: icmp_seq=20 ttl=59 time=126.120 ms >> > 64 bytes from 216.58.210.110: icmp_seq=21 ttl=59 time=170.920 ms >> > 64 bytes from 216.58.210.110: icmp_seq=22 ttl=59 time=137.330 ms >> > 64 bytes from 216.58.210.110: icmp_seq=23 ttl=59 time=17.424 ms >> > >> > (tried other host with similar results) >> > >> > It seems to settle for a while but randomly comes back.. >> > >> > uname -a >> > FreeBSD r2d2 10.1-STABLE FreeBSD 10.1-STABLE #7 r277979M: Sat Jan 31 >> > 16:05:30 WET 2015 root@r2d2:/usr/obj/usr/src/sys/GENERIC amd64 >> > _______________________________________________ >> > freebsd-wireless@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> > To unsubscribe, send any mail to " >> freebsd-wireless-unsubscribe@freebsd.org" >> > > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 18:49:45 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3889DE75 for ; Sun, 15 Feb 2015 18:49:45 +0000 (UTC) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE738913 for ; Sun, 15 Feb 2015 18:49:44 +0000 (UTC) Received: by mail-ig0-f180.google.com with SMTP id b16so19893577igk.1 for ; Sun, 15 Feb 2015 10:49:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wA4uV4g4Hsa8lZMvslXRVr6c/7uNTCAEqCCg12VIplg=; b=qulGvYM44U+rLUFVOxxsmxxFHUzsmo/syBKYN0QjUXrpCDVNaFGdSZ4y04tprVvgeB CpMDaKjE1HsSrmFIl9v9qoTU04iy+J2QRraTsNQQLaaCK4O4JrS+NU84fa/8OzupT7Hf IFaoqFjqkfnIXWfuXS8lRVEC9l0faQ2IGP8d647MgWUM0g0zidDtOT1qH3EL2jcXgOZ1 +vVrcxFZEI7tyF8gtri9rNd0t6oAg77PbYhp8fsDQLDF4HpF7iC3MX/Tjf2bb1mRQEuN wkRC6aygKlc2X6cc0rvKsH1sHgxNSLLEKemyj8DjGoVKLhj3gqHZVBGnibvf2OBbuJgQ DG/w== MIME-Version: 1.0 X-Received: by 10.42.188.133 with SMTP id da5mr25570631icb.37.1424026184408; Sun, 15 Feb 2015 10:49:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Sun, 15 Feb 2015 10:49:44 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Feb 2015 10:49:44 -0800 X-Google-Sender-Auth: NbGdftWW-GauUWHmww6YcZpdCOA Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout From: Adrian Chadd To: Miguel Clara Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 18:49:45 -0000 On 15 February 2015 at 10:47, Miguel Clara wrote: > > On Sat, Feb 14, 2015 at 2:40 AM, Miguel Clara > wrote: >> >> >> On Sat, Jan 31, 2015 at 7:00 PM, Adrian Chadd wrote: >>> >>> Hi, >>> >>> please try updating to -HEAD. It's possible that'll fix things. >> >> >> Hi, >> >> I've update to head and still see the messages in dmesg. >> >> And the same slowness... rebooting seems to fix the issue, but it was the >> same in 10 and randomly (surely there's a reason only I'm not noticing what) >> it goes back to this state. >> >> Is there any debugging I can try to figure whats going on when this >> happens? > > > Also just now I lost network and saw this in dmesg: > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > ath0: ath_intr: TSFOOR > > > It was just during a few seconds. Ok, so that happens because you haven't heard a beacon for a while, and the "TSF out of range" interrupt has fired. Try creating the VAP again, but this time do it with -bgscan -powersave . -adrian >> >>> >>> On 31 January 2015 at 09:19, Miguel Clara wrote: >>> > I've just upgrade to the latest 10/stable. >>> > >>> > trying to git clone a repo was giving me horrible speed, and I honestly >>> > tough it was at their side, until I noticed issues while browsing and >>> > this >>> > in dmesg: >>> > >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetCTSTimeout: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > ar9300_Stub_GetAntennaSwitch: called >>> > >>> > Speedtest either gives me and ok result or very poor, and pings also >>> > prove >>> > that something is not quite right: >>> > 64 bytes from 216.58.210.110: icmp_seq=7 ttl=59 time=18.096 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=8 ttl=59 time=149.083 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=9 ttl=59 time=18.376 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=10 ttl=59 time=19.084 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=11 ttl=59 time=18.305 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=12 ttl=59 time=18.140 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=13 ttl=59 time=16.700 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=14 ttl=59 time=105.554 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=15 ttl=59 time=34.336 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=16 ttl=59 time=76.410 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=17 ttl=59 time=34.400 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=18 ttl=59 time=73.521 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=19 ttl=59 time=154.728 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=20 ttl=59 time=126.120 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=21 ttl=59 time=170.920 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=22 ttl=59 time=137.330 ms >>> > 64 bytes from 216.58.210.110: icmp_seq=23 ttl=59 time=17.424 ms >>> > >>> > (tried other host with similar results) >>> > >>> > It seems to settle for a while but randomly comes back.. >>> > >>> > uname -a >>> > FreeBSD r2d2 10.1-STABLE FreeBSD 10.1-STABLE #7 r277979M: Sat Jan 31 >>> > 16:05:30 WET 2015 root@r2d2:/usr/obj/usr/src/sys/GENERIC amd64 >>> > _______________________________________________ >>> > freebsd-wireless@freebsd.org mailing list >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> > To unsubscribe, send any mail to >>> > "freebsd-wireless-unsubscribe@freebsd.org" >> >> > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 19:01:09 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19BB0330; Sun, 15 Feb 2015 19:01:09 +0000 (UTC) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D69F2A03; Sun, 15 Feb 2015 19:01:08 +0000 (UTC) Received: by ierx19 with SMTP id x19so29902025ier.3; Sun, 15 Feb 2015 11:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kYmWVWMv+KqUWtP+d70S/VovUKlkAk6v4jBolw1qmK0=; b=t0CFoYHtN/iHooeYQcVBVGxyQtlVz8wiYlTGfmqIprcQYgkLu/74X2kf+U7SEbOUmG A2Q9K+jdJWSRkXtNFCMxTvLtkUMU+RURuJq8uPvMQmlRDMdMMK3rbEZqEQT6A0yyHd0a A3WDrO0pL4r3Lsrb1iFI6tRqhx4J1ylnooUtv7CMkutCuHCF7tYcw/3F7OugkDXUIrPy cAtEqbBVwvepHE4179LGAOPPv7Oq2XUChwacE/GnL/3TaYWaQsC4otYAb+TBaQ7I7LyI cQqh7MI3YoyobmmNQyCTt8mz538eOnn5/7Cx0H8lN5WcE8rZgsItzg1bT/6PdMzwDcSp FmaQ== X-Received: by 10.50.73.99 with SMTP id k3mr17209838igv.21.1424026867530; Sun, 15 Feb 2015 11:01:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Sun, 15 Feb 2015 11:00:47 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sun, 15 Feb 2015 19:00:47 +0000 Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 19:01:09 -0000 On Sun, Feb 15, 2015 at 6:49 PM, Adrian Chadd wrote: > On 15 February 2015 at 10:47, Miguel Clara wrote: > > > > On Sat, Feb 14, 2015 at 2:40 AM, Miguel Clara > > wrote: > >> > >> > >> On Sat, Jan 31, 2015 at 7:00 PM, Adrian Chadd > wrote: > >>> > >>> Hi, > >>> > >>> please try updating to -HEAD. It's possible that'll fix things. > >> > >> > >> Hi, > >> > >> I've update to head and still see the messages in dmesg. > >> > >> And the same slowness... rebooting seems to fix the issue, but it was > the > >> same in 10 and randomly (surely there's a reason only I'm not noticing > what) > >> it goes back to this state. > >> > >> Is there any debugging I can try to figure whats going on when this > >> happens? > > > > > > Also just now I lost network and saw this in dmesg: > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > ath0: ath_intr: TSFOOR > > > > > > It was just during a few seconds. > > Ok, so that happens because you haven't heard a beacon for a while, > and the "TSF out of range" interrupt has fired. > > Try creating the VAP again, but this time do it with -bgscan -powersave . > > > I just did that manually and added "-bgscan -powersave" to rc.conf. Is there a way I can verify those changes were applied? ifconfig wlan0 doesn't show anything related. > -adrian > > >> > >>> > >>> On 31 January 2015 at 09:19, Miguel Clara > wrote: > >>> > I've just upgrade to the latest 10/stable. > >>> > > >>> > trying to git clone a repo was giving me horrible speed, and I > honestly > >>> > tough it was at their side, until I noticed issues while browsing and > >>> > this > >>> > in dmesg: > >>> > > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetCTSTimeout: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > ar9300_Stub_GetAntennaSwitch: called > >>> > > >>> > Speedtest either gives me and ok result or very poor, and pings also > >>> > prove > >>> > that something is not quite right: > >>> > 64 bytes from 216.58.210.110: icmp_seq=7 ttl=59 time=18.096 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=8 ttl=59 time=149.083 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=9 ttl=59 time=18.376 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=10 ttl=59 time=19.084 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=11 ttl=59 time=18.305 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=12 ttl=59 time=18.140 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=13 ttl=59 time=16.700 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=14 ttl=59 time=105.554 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=15 ttl=59 time=34.336 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=16 ttl=59 time=76.410 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=17 ttl=59 time=34.400 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=18 ttl=59 time=73.521 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=19 ttl=59 time=154.728 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=20 ttl=59 time=126.120 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=21 ttl=59 time=170.920 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=22 ttl=59 time=137.330 ms > >>> > 64 bytes from 216.58.210.110: icmp_seq=23 ttl=59 time=17.424 ms > >>> > > >>> > (tried other host with similar results) > >>> > > >>> > It seems to settle for a while but randomly comes back.. > >>> > > >>> > uname -a > >>> > FreeBSD r2d2 10.1-STABLE FreeBSD 10.1-STABLE #7 r277979M: Sat Jan 31 > >>> > 16:05:30 WET 2015 root@r2d2:/usr/obj/usr/src/sys/GENERIC amd64 > >>> > _______________________________________________ > >>> > freebsd-wireless@freebsd.org mailing list > >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >>> > To unsubscribe, send any mail to > >>> > "freebsd-wireless-unsubscribe@freebsd.org" > >> > >> > > > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 19:02:43 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B528A354 for ; Sun, 15 Feb 2015 19:02:43 +0000 (UTC) Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E5F4A97 for ; Sun, 15 Feb 2015 19:02:43 +0000 (UTC) Received: by iecrp18 with SMTP id rp18so14455499iec.9 for ; Sun, 15 Feb 2015 11:02:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oDQQTSdpVQaq8tI48aXI/PKPTbM1AMG6ns7KgLI5Sfk=; b=jgGX2QufPagAeXpttic5Dv2usPHv8H4INn8KtH9UBRy43BF1fmTr+WlWJvfMg7+we4 MoXE2s91qujGpym+1X1DGil+frvTspr5E0Mkuw7aR7bthsEEIv1ooYqUJvZhsqCDwQt4 8ts88MwyJHtvJgBZ0NzT1aNXp2UuZlZWH2m4YLVIRJhppg7LWSd7+Xxjx8M7B9YUt/Uy 7bdGP0G2fAExaKTvfu0jJFfg1NMuG6S2n7ze3w8mawq1COIXUicnIU8NX7qoqhqcPTPf s9qGP8/JDgDFuUSiCxWU5P7zS/zphcCikbJhhEQnEUQCqtZODstKsPIn2BXimrG6Q2yE UHGQ== MIME-Version: 1.0 X-Received: by 10.107.31.16 with SMTP id f16mr24935217iof.88.1424026956822; Sun, 15 Feb 2015 11:02:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Sun, 15 Feb 2015 11:02:36 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Feb 2015 11:02:36 -0800 X-Google-Sender-Auth: FqhHUhMBW9cRRRlnNZagGVfzzfo Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout From: Adrian Chadd To: Miguel Clara Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 19:02:43 -0000 ifconfig -v wlan0 ; if you see powersave CAM rather than powersave NONE, then it's trying to do powersave. -a On 15 February 2015 at 11:00, Miguel Clara wrote: > > On Sun, Feb 15, 2015 at 6:49 PM, Adrian Chadd wrote: >> >> On 15 February 2015 at 10:47, Miguel Clara wrote: >> > >> > On Sat, Feb 14, 2015 at 2:40 AM, Miguel Clara >> > wrote: >> >> >> >> >> >> On Sat, Jan 31, 2015 at 7:00 PM, Adrian Chadd >> >> wrote: >> >>> >> >>> Hi, >> >>> >> >>> please try updating to -HEAD. It's possible that'll fix things. >> >> >> >> >> >> Hi, >> >> >> >> I've update to head and still see the messages in dmesg. >> >> >> >> And the same slowness... rebooting seems to fix the issue, but it was >> >> the >> >> same in 10 and randomly (surely there's a reason only I'm not noticing >> >> what) >> >> it goes back to this state. >> >> >> >> Is there any debugging I can try to figure whats going on when this >> >> happens? >> > >> > >> > Also just now I lost network and saw this in dmesg: >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > ath0: ath_intr: TSFOOR >> > >> > >> > It was just during a few seconds. >> >> Ok, so that happens because you haven't heard a beacon for a while, >> and the "TSF out of range" interrupt has fired. >> >> Try creating the VAP again, but this time do it with -bgscan -powersave . >> >> > I just did that manually and added "-bgscan -powersave" to rc.conf. > > Is there a way I can verify those changes were applied? > > ifconfig wlan0 doesn't show anything related. > >> >> -adrian >> >> >> >> >>> >> >>> On 31 January 2015 at 09:19, Miguel Clara >> >>> wrote: >> >>> > I've just upgrade to the latest 10/stable. >> >>> > >> >>> > trying to git clone a repo was giving me horrible speed, and I >> >>> > honestly >> >>> > tough it was at their side, until I noticed issues while browsing >> >>> > and >> >>> > this >> >>> > in dmesg: >> >>> > >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetCTSTimeout: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > ar9300_Stub_GetAntennaSwitch: called >> >>> > >> >>> > Speedtest either gives me and ok result or very poor, and pings also >> >>> > prove >> >>> > that something is not quite right: >> >>> > 64 bytes from 216.58.210.110: icmp_seq=7 ttl=59 time=18.096 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=8 ttl=59 time=149.083 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=9 ttl=59 time=18.376 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=10 ttl=59 time=19.084 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=11 ttl=59 time=18.305 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=12 ttl=59 time=18.140 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=13 ttl=59 time=16.700 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=14 ttl=59 time=105.554 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=15 ttl=59 time=34.336 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=16 ttl=59 time=76.410 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=17 ttl=59 time=34.400 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=18 ttl=59 time=73.521 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=19 ttl=59 time=154.728 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=20 ttl=59 time=126.120 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=21 ttl=59 time=170.920 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=22 ttl=59 time=137.330 ms >> >>> > 64 bytes from 216.58.210.110: icmp_seq=23 ttl=59 time=17.424 ms >> >>> > >> >>> > (tried other host with similar results) >> >>> > >> >>> > It seems to settle for a while but randomly comes back.. >> >>> > >> >>> > uname -a >> >>> > FreeBSD r2d2 10.1-STABLE FreeBSD 10.1-STABLE #7 r277979M: Sat Jan 31 >> >>> > 16:05:30 WET 2015 root@r2d2:/usr/obj/usr/src/sys/GENERIC amd64 >> >>> > _______________________________________________ >> >>> > freebsd-wireless@freebsd.org mailing list >> >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> >>> > To unsubscribe, send any mail to >> >>> > "freebsd-wireless-unsubscribe@freebsd.org" >> >> >> >> >> > > > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 19:07:55 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 153EE51C; Sun, 15 Feb 2015 19:07:55 +0000 (UTC) Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D1E2FAB9; Sun, 15 Feb 2015 19:07:54 +0000 (UTC) Received: by iecar1 with SMTP id ar1so29859512iec.11; Sun, 15 Feb 2015 11:07:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8pxI1xgvOYsABeZZM5Ydzy3WYvVhaJwypdPtBR9cBgE=; b=MJ1zbrQ91Wkygi9U3nNcV6PwuAHfVu/vR53c5f0ldBSAENDOPPKiDub8Lj0Tuo3VCp 4Wsa63HLw0tUSf/llsLeZdqPaDrzUOBd21F8kzrERaB6C/po4x15HC3zIwVMY3gMUvjq W1SdOeUn7iJd4Tv7F15DSf3TEu+F4SCCTRlwRpOvdK2c9s8Wazbg4PZlLgqR8zcpYbvg eQKst7DT1i2EAxbHlAaVPsxsNk+0YW9QuQYl+zYK8QoNI+jw+ymMseGYmJPS29wQBoWf MunnYuPeV8GTsY+jccS4/kNpAkiBwOG2ryh5jefWA0BpK+j3ONLLC+HWKUjLOCc6D5uT t8Sw== X-Received: by 10.43.131.5 with SMTP id ho5mr25301013icc.82.1424027274184; Sun, 15 Feb 2015 11:07:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Sun, 15 Feb 2015 11:07:34 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sun, 15 Feb 2015 19:07:34 +0000 Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 19:07:55 -0000 On Sun, Feb 15, 2015 at 7:02 PM, Adrian Chadd wrote: > ifconfig -v wlan0 ; if you see powersave CAM rather than powersave > NONE, then it's trying to do powersave. > > > ifconfig -v wlan0|eg 'powersave|bgscan' AES-CCM 2:128-bit powersavemode OFF powersavesleep 100 txpower 20 scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250 this is after the "-bgscan -powersave" of course.. I see OFF so assuming its correct. > -a > > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 20:24:11 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E9B78FF; Sun, 15 Feb 2015 20:24:11 +0000 (UTC) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA811218; Sun, 15 Feb 2015 20:24:10 +0000 (UTC) Received: by iecrd18 with SMTP id rd18so30056216iec.8; Sun, 15 Feb 2015 12:24:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YD4T+7w3Qn5ptnpOG7qSL6lULoTYHVUtQFA4g6Tzhpc=; b=wxHRp0cHi2GVaHtl3mgt9H5m4cUArigB7cP2LDDX7DUURw9etu51+Kn5lEvkcpsyvq i9s8xnrRsQEQRJ13J7CkHvJ7eo2h/BCo3IOBklJ7ZCaWRa3GV6CnauOGVHE6Q7ea5YiL aY00CQQrp6yjEfQJYNDuE0oQFJ8bF7eYvMVbVm5luSEqsKqzsFmR6pQSpoVK5oiiTSya EEdAABn4Lbwn6OBASvvA05Az562oFK3NdG1Hb0S5ECpHJ4ZiJPonlk3fBCCktlJFEjr3 sXTcwj9Bb6OVHRuHWyB2TMGGRUMBOdg1nsRbdsCRYojZGk6p2DK7kNuIg7G7Ch59XpB1 Enww== X-Received: by 10.50.78.131 with SMTP id b3mr17582339igx.0.1424031844437; Sun, 15 Feb 2015 12:24:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Sun, 15 Feb 2015 12:23:44 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sun, 15 Feb 2015 20:23:44 +0000 Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 20:24:11 -0000 On Sun, Feb 15, 2015 at 7:07 PM, Miguel Clara wrote: > > On Sun, Feb 15, 2015 at 7:02 PM, Adrian Chadd wrote: > >> ifconfig -v wlan0 ; if you see powersave CAM rather than powersave >> NONE, then it's trying to do powersave. >> >> >> ifconfig -v wlan0|eg 'powersave|bgscan' > AES-CCM 2:128-bit powersavemode OFF powersavesleep 100 txpower 20 > scanvalid 60 -bgscan bgscanintvl 300 bgscanidle 250 > > this is after the "-bgscan -powersave" of course.. I see OFF so assuming > its correct. > Keeps happening Feb 15 19:08:25 r2d2 kernel: ath0: ath_intr: TSFOOR Feb 15 19:08:27 r2d2 last message repeated 4 times Feb 15 20:14:11 r2d2 kernel: ath0: ath_intr: TSFOOR uname -a FreeBSD r2d2 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r278691+b56b2f6(master) -a >> >> From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 20:25:23 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FFC9918 for ; Sun, 15 Feb 2015 20:25:23 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D188721A for ; Sun, 15 Feb 2015 20:25:22 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id b16so20166413igk.1 for ; Sun, 15 Feb 2015 12:25:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=oElrajtS8D+7YVmWswtDHK8sfcxe9iR9RicbVH3JU08=; b=NWzL6nWY5zoiuQld1uxm+XWTv+sgtx7qJI6G4oegHlmxSPEDb/S7CDYbowDlJ32Xl8 cs0CtiF7p/YUbWcM5LHNkNBA9vIoGpJPV/sModku4gs4savYPh6oUEobhxQ90v65PXuN mfb+fg5srATaZXbef366CP9xyDCC0VkPZkjc3dpt7aMmYnJy7lczbTELI7Yfu5qQCuw7 zASC+jXM8PQupaE9OIiSWNgrDJIzCI/HV9NJQXmG+I5YxAp1E+iWVw1dXggkjp7GzQZs aMNuHyTJ0F8UWrl9q+a25fAs6ANwz0pdEpbe/dT0GCVpUOe+3Qn4++E23Z6sQsdfOzuO oWSQ== MIME-Version: 1.0 X-Received: by 10.50.164.227 with SMTP id yt3mr17524508igb.32.1424031922219; Sun, 15 Feb 2015 12:25:22 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Sun, 15 Feb 2015 12:25:22 -0800 (PST) In-Reply-To: References: Date: Sun, 15 Feb 2015 12:25:22 -0800 X-Google-Sender-Auth: m50eumOWq6ubaKnknV5RISw2NBY Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout From: Adrian Chadd To: Miguel Clara Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 20:25:23 -0000 I bet your environment is quite noisy and the ar9300 HAL is just not coping well. :( -adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 20:32:35 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30A80AB4; Sun, 15 Feb 2015 20:32:35 +0000 (UTC) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA5BE31A; Sun, 15 Feb 2015 20:32:34 +0000 (UTC) Received: by iebtr6 with SMTP id tr6so19486604ieb.7; Sun, 15 Feb 2015 12:32:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=D5BYl9Qyq5uJQ356oBeYMj9eOhQm4uQOHlDSM/8KXbo=; b=wfUU3IIYogoky+etVKNaf18tmE+c37YYsxDa5NqfdTxH0mmOn8cxVfKIEEkUUKm0PU 1DerAqy8V+D53MTaZYy5U4PxXRA6MauYBsL/wTS/yhffcfQ273MIHrC2Onq6JiMIEnhN NuN6SpQxhc6fN6fKQvai50mk/z+BzlJDhXUpnDTttT9FaIwCoky8vaowLWkhT2zc61Ad UT8m56SExrkNndRXt4gy1zH5hhZrnZH/EQbyVfvwikHpKr5fQ1joy9gjtn6icYTOWamC giCFE7tQ1UaWR/WYLWNjONb2w6RHLz0FkkDZm35zVXIwbEHtbqM8k3K9V5T7qCnItUfD KtMw== X-Received: by 10.107.150.67 with SMTP id y64mr25496241iod.22.1424032354042; Sun, 15 Feb 2015 12:32:34 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Sun, 15 Feb 2015 12:32:13 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sun, 15 Feb 2015 20:32:13 +0000 Message-ID: Subject: Re: ath0 performence issues "ar9300_Stub_GetCTSTimeout" "ar9300_Stub_GetCTSTimeout To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 20:32:35 -0000 On Sun, Feb 15, 2015 at 8:25 PM, Adrian Chadd wrote: > I bet your environment is quite noisy and the ar9300 HAL is just not > coping well. :( > > > Could be, I have a laptop and a cell phone just close by and the TV is also using wireless, but those are on 2.4Ghtz... and ... Oooh I just noticed its connected to "PissnLove" and not "PissnLove5G". wpa_supplicant sometimes fails on selecting the on with higher priority. I'll force it back to the 5G and see if this goes away and if so I guess you are correct :) > -adrian > From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 15 21:00:05 2015 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25E4C19B for ; Sun, 15 Feb 2015 21:00:05 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 13B2C6E8 for ; Sun, 15 Feb 2015 21:00:05 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1FL04J5010767 for ; Sun, 15 Feb 2015 21:00:04 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201502152100.t1FL04J5010767@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Date: Sun, 15 Feb 2015 21:00:04 +0000 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Feb 2015 21:00:05 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in 5 problems total for which you should take action. From owner-freebsd-wireless@FreeBSD.ORG Tue Feb 17 21:13:40 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F1176DA2 for ; Tue, 17 Feb 2015 21:13:40 +0000 (UTC) Received: from mproxyhzb2.163.com (mproxyhzb2.163.com [123.58.178.202]) by mx1.freebsd.org (Postfix) with ESMTP id 203B93EE for ; Tue, 17 Feb 2015 21:13:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:Subject:Message-ID:From:MIME-Version; bh=SU/RS rCmXYAldzQ9fG1UrIybN9HI+PAaxL2UMXMJXb8=; b=djRVJmtNcDpvBsR3HqPA7 KGU9e2AmDeTarblwRYsie0fBRGyxeKiItnUn8gFZq0b6NrPEzSV4b4LfOurnvbSg fVe0508qMHXk1fxrae0NhsA4dcdILesGPmJ78DRAZVA4YmBpw+zfaGbPmej+/O3E Jx6f28KaPPeZUuM81ET394= Received: from [192.168.2.103] (unknown [221.225.197.49]) by smtp2 (Coremail) with SMTP id DNGowEBpW2tWq+NUew++BA--.1923S2; Wed, 18 Feb 2015 04:57:59 +0800 (CST) Date: Wed, 18 Feb 2015 04:57:57 +0800 Subject: TDMA slot Message-ID: From: bh To: freebsd-wireless@freebsd.org MIME-Version: 1.0 X-CM-TRANSID: DNGowEBpW2tWq+NUew++BA--.1923S2 X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvjxU3uyxDUUUU X-Originating-IP: [221.225.197.49] X-CM-SenderInfo: nxymmqqrwthudrp/1tbiLwajY1EARcfsPAAAsq X-Mailman-Approved-At: Tue, 17 Feb 2015 21:33:42 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2015 21:13:41 -0000 CgotLS0tLS0tLSDljp/lp4vpgq7ku7YgLS0tLS0tLS0K5Li76aKY77yaVERNQSBzbG90CuWPkeS7 tuS6uu+8muWtkOaWhyA8dThqOUAxNjMuY29tPgrmlLbku7bkurrvvJrlrZDmlocgPHU4ajlAMTYz LmNvbT4K5oqE6YCB77yaZnJlZWJzZC13aXJlbGVzc0BmcmVlYnNkLm9yZwoKCgoKCgoKCkRlYXIg YWxsCsKgwqDCoCBJIGFtIGNvbmZ1c2VkIGZvciBURE1BIHNsb3TCoCBvZiBmcmVlYnNkICwgSSBz ZWUgdGhlIGRlZmF1bHQgc2xvdGNudD0yLCBiZWFjb25pbnR2bD01LCBTbyBUaGUgYXAgc2VuZCB0 aGUgYmVhY29uIGV2ZXJ5IGZpdmUgc2xvdMKgICxkb2Vzbid0IGl0PwpUaGUgYXAncyBEQkEgZmly ZSBldmVyeSBzbG90wqAgLGRvZXNuJ3QgaXQ/IGlmIHNvICx0aGUgYXAgd2lsbCBzZW5kIGRhdGHC oCBwYWNrYWdlIGluIGV2ZXJ5IHNsb3QgYmVjYXVzZSB0aGUgYXAgZmlyZSB0aGUgREJBIHRpbWVy wqAgZXZlcnkgc2xvdCzCoCBJcyBtecKgIHVuZGVyc3RhbmRpbmcgY29ycmVjdD8KCgpCUgoKCgoK Cg== From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 18 15:48:55 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BDA2C51 for ; Wed, 18 Feb 2015 15:48:55 +0000 (UTC) Received: from mproxygzt2.163.com (mproxygzt2.163.com [113.108.225.6]) by mx1.freebsd.org (Postfix) with ESMTP id EC71CA26 for ; Wed, 18 Feb 2015 15:48:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:Subject:Message-ID:From:MIME-Version; bh=RjIxe 5WJVRsIFmAH9cz971AB4RhftX2g+jjAnSvGV/8=; b=lyVtQnNmtQTz7iZUcEn07 UTvSQn01FWi1JFz1QYGrlPFm9GG1dM1Fk7zpCVuy9j99pu3HAi8BkZrYdMpPaCmB O4PzhMncW9UXk67XEGEoSpemBOG42/sSmzGqXn93kBytiJ576dgJC9MIsG+h+a6f sdMoNZq6q2/USF/ygoL8r8= Received: from [10.70.213.24] (unknown [180.99.105.170]) by smtp11 (Coremail) with SMTP id D8CowEAJiEm6sORUDnHaBA--.637S2; Wed, 18 Feb 2015 23:33:16 +0800 (CST) X-Coremail-DSSMTP: 180.99.105.170 Date: Wed, 18 Feb 2015 23:33:11 +0800 Subject: Re: freebsd-wireless Digest, Vol 190, Issue 2 Message-ID: From: bh To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-CM-TRANSID: D8CowEAJiEm6sORUDnHaBA--.637S2 X-Coremail-Antispam: 1Uf129KBjvJXoWxJr18KF43Jw1rXFWfCF45ZFb_yoW8Zr48pr WftF43Gr1UJr18J348K3Z7Zr1UAayxtrs7XFW5Gr18tFy5A3W8JF15ZF1Fg3yDXrWYkry5 tr17Krnaqw4DJrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07jOxhdUUUUU= X-Originating-IP: [180.99.105.170] X-CM-SenderInfo: nxymmqqrwthudrp/1tbiLwCkY1EARc72rQAAsp X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 15:48:55 -0000 CgpmcmVlYnNkLXdpcmVsZXNzLXJlcXVlc3RAZnJlZWJzZC5vcmfnvJblhpnvvJoKCj5TZW5kIGZy ZWVic2Qtd2lyZWxlc3MgbWFpbGluZyBsaXN0IHN1Ym1pc3Npb25zIHRvCj4JZnJlZWJzZC13aXJl bGVzc0BmcmVlYnNkLm9yZwo+Cj5UbyBzdWJzY3JpYmUgb3IgdW5zdWJzY3JpYmUgdmlhIHRoZSBX b3JsZCBXaWRlIFdlYiwgdmlzaXQKPglodHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcvbWFpbG1hbi9s aXN0aW5mby9mcmVlYnNkLXdpcmVsZXNzCj5vciwgdmlhIGVtYWlsLCBzZW5kIGEgbWVzc2FnZSB3 aXRoIHN1YmplY3Qgb3IgYm9keSAnaGVscCcgdG8KPglmcmVlYnNkLXdpcmVsZXNzLXJlcXVlc3RA ZnJlZWJzZC5vcmcKPgo+WW91IGNhbiByZWFjaCB0aGUgcGVyc29uIG1hbmFnaW5nIHRoZSBsaXN0 IGF0Cj4JZnJlZWJzZC13aXJlbGVzcy1vd25lckBmcmVlYnNkLm9yZwo+Cj5XaGVuIHJlcGx5aW5n LCBwbGVhc2UgZWRpdCB5b3VyIFN1YmplY3QgbGluZSBzbyBpdCBpcyBtb3JlIHNwZWNpZmljCj50 aGFuICJSZTogQ29udGVudHMgb2YgZnJlZWJzZC13aXJlbGVzcyBkaWdlc3QuLi4iCj4KPgo+VG9k YXkncyBUb3BpY3M6Cj4KPiAgIDEuIFRETUEgc2xvdCAoYmgpCj4KPgo+LS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+ Cj5NZXNzYWdlOiAxCj5EYXRlOiBXZWQsIDE4IEZlYiAyMDE1IDA0OjU3OjU3ICswODAwCj5Gcm9t OiBiaCA8dThqOUAxNjMuY29tPgo+VG86IGZyZWVic2Qtd2lyZWxlc3NAZnJlZWJzZC5vcmcKPlN1 YmplY3Q6IFRETUEgc2xvdAo+TWVzc2FnZS1JRDogPHdqbmdxaGp4NzY4MTl4N2kzY2Mycmlnai4x NDI0MjA2NjA3ODM1QGVtYWlsLmFuZHJvaWQuY29tPgo+Q29udGVudC1UeXBlOiB0ZXh0L3BsYWlu OyBjaGFyc2V0PXV0Zi04Cj4KPgo+Cj4tLS0tLS0tLSA/Pz8/IC0tLS0tLS0tCj4/Pz9URE1BIHNs b3QKPj8/Pz8/PyA8dThqOUAxNjMuY29tPgo+Pz8/Pz8/IDx1OGo5QDE2My5jb20+Cj4/Pz9mcmVl YnNkLXdpcmVsZXNzQGZyZWVic2Qub3JnCj4KPgo+Cj4KPgo+Cj4KPgo+RGVhciBhbGwKPj8/PyBJ IGFtIGNvbmZ1c2VkIGZvciBURE1BIHNsb3Q/IG9mIGZyZWVic2QgLCBJIHNlZSB0aGUgZGVmYXVs dCBzbG90Y250PTIsIGJlYWNvbmludHZsPTUsIFNvIFRoZSBhcCBzZW5kIHRoZSBiZWFjb24gZXZl cnkgZml2ZSBzbG90PyAsZG9lc24ndCBpdD8KPlRoZSBhcCdzIERCQSBmaXJlIGV2ZXJ5IHNsb3Q/ ICxkb2Vzbid0IGl0PyBpZiBzbyAsdGhlIGFwIHdpbGwgc2VuZCBkYXRhPyBwYWNrYWdlIGluIGV2 ZXJ5IHNsb3QgYmVjYXVzZSB0aGUgYXAgZmlyZSB0aGUgREJBIHRpbWVyPyBldmVyeSBzbG90LD8g SXMgbXk/IHVuZGVyc3RhbmRpbmcgY29ycmVjdD8KPgo+Cj5CUgo+Cj4KPgo+Cj4KPgo+LS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCj4KPlN1YmplY3Q6IERpZ2VzdCBGb290ZXIKPgo+X19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPmZyZWVic2Qtd2ly ZWxlc3NAZnJlZWJzZC5vcmcgbWFpbGluZyBsaXN0Cj5odHRwOi8vbGlzdHMuZnJlZWJzZC5vcmcv bWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXdpcmVsZXNzCj5UbyB1bnN1YnNjcmliZSwgc2VuZCBh bnkgbWFpbCB0byAiZnJlZWJzZC13aXJlbGVzcy11bnN1YnNjcmliZUBmcmVlYnNkLm9yZyIKPgo+ LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCj4KPkVuZCBvZiBmcmVlYnNkLXdpcmVsZXNz IERpZ2VzdCwgVm9sIDE5MCwgSXNzdWUgMgo+KioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqCg== From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 18 16:11:37 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C6D1F265 for ; Wed, 18 Feb 2015 16:11:37 +0000 (UTC) Received: from m12-12.163.com (m12-12.163.com [220.181.12.12]) by mx1.freebsd.org (Postfix) with ESMTP id 01562D35 for ; Wed, 18 Feb 2015 16:11:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:Subject:Message-ID:From:MIME-Version; bh=yfeBa cxT9qh0sM057MenLcCdIDTutrx2a58NU3H2zwY=; b=ZLGheElo/MnaOc6qtCL7f GJZeSW+mU/PAFGjtYxRBrEtZmgXp2OCxcR4azWzKMsa6Hn7JspcO2rCRjRvmvfKo 5ryrMQBwg8GYYHyGbINf32dAk3k/rdbX7htAARR0GXCke+CumGVRszlo88byeB1j ed7K/81ilnuFvWgx7W9l5s= Received: from [10.70.213.24] (unknown [180.99.105.170]) by smtp8 (Coremail) with SMTP id DMCowEBJDErxteRUQNEIAQ--.754S2; Wed, 18 Feb 2015 23:55:30 +0800 (CST) X-Coremail-DSSMTP: 180.99.105.170 Date: Wed, 18 Feb 2015 23:55:26 +0800 Subject: Re: TDMA slot(bh) Message-ID: From: bh To: freebsd-wireless@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-CM-TRANSID: DMCowEBJDErxteRUQNEIAQ--.754S2 X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvjxUcvPfUUUUU X-Originating-IP: [180.99.105.170] X-CM-SenderInfo: nxymmqqrwthudrp/xtbBEQukY1D+a5Bj4AAAsL X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 16:11:37 -0000 RGVhciAKICAgIFRoZSBkZWZhdWx0IHNsb3RjbnQ9MiAsIGJlY250aXZhbD01LkZvciBhcCAgaXQg d2lsbCBnZW5lcmF0ZSBTV0JBIGV2ZXJ5ICBzbG90LGl0IHdpbGwgc2VuZCBiZWFjb24gZXZlcnkg Zml2ZSBzbG90cywgYmVhY2F1c2UgYXAgZmlyZSAgdGhlIERCQSB0aW1lciBpbiBldmVyeSBzbG90 LCBzbyBpdCB3aWxsIHNlbmQgZGF0YSBwYWNrYWdlICBpbiBldmVyeSBzbG90LiBJcyBteSBhYm92 ZSB1bmRlcnN0YW5kaW5nIGNvcnJlY3Q/ From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 18 16:30:02 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 89D73178 for ; Wed, 18 Feb 2015 16:30:02 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 50D8CFAF for ; Wed, 18 Feb 2015 16:30:02 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id b16so37942133igk.1 for ; Wed, 18 Feb 2015 08:30:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=C447JMyD+g8yIPWu97Eqe+Ihsl9bZh+HZPGpVSxpGmQ=; b=0MwK8M6UB/+sx2uEVOZtr4ln4ksFChu4r065xYG8rcbpSUFsQftsLc1e18rxHvkkBb hx0558Kz5eMlsD8nzosz/qradPmKItIH0MZhB+xxFRL7Sjd8bTpQCLt7yqe/XLCad8O8 JWoMvHJon3RTUyBuEYHfCAs5ko0wm7oaYNzUx4fw3kvDTFaITo27fjAxVTlW4NBkmUal xUmiIyAmtbPC7s9wmwIAQnR03DUrzTRV1lVl4kWOzi3uglNutM41Gaee2ZsDdN/+TMOn bFSeKhpp2v6kCv5OgP3465bjJkD3tPIt7nS1oQQA8gUc1Kjba4KTYINYyZh70Q9Annkc ayYw== MIME-Version: 1.0 X-Received: by 10.42.188.133 with SMTP id da5mr931988icb.37.1424277001611; Wed, 18 Feb 2015 08:30:01 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Wed, 18 Feb 2015 08:30:01 -0800 (PST) Date: Wed, 18 Feb 2015 08:30:01 -0800 X-Google-Sender-Auth: DicM2ftXwlbUbg5DyPNRkemBAZk Message-ID: Subject: Re: TDMA slot(bh) From: Adrian Chadd To: bh Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 16:30:02 -0000 On 18 February 2015 at 07:55, bh wrote: > Dear > The default slotcnt=2 , becntival=5.For ap it will generate SWBA every slot,it will send beacon every five slots, beacause ap fire the DBA timer in every slot, so it will send data package in every slot. Is my above understanding correct? It generates SWBA every beacon interval, which is calculated in ath_tdma_bintvalsetup(). Master stations beacon 20 times a second with the default config specified by the wiki. -adrian From owner-freebsd-wireless@FreeBSD.ORG Wed Feb 18 17:28:40 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1B63AA4 for ; Wed, 18 Feb 2015 17:28:40 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DCD2E9FD for ; Wed, 18 Feb 2015 17:28:39 +0000 (UTC) Received: by iecrp18 with SMTP id rp18so3067334iec.1 for ; Wed, 18 Feb 2015 09:28:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=sG4/7824fJRLYoH30BqWtzmN84pkD5eyHwP5oBbepI4=; b=juYpqy/oEFu2B+XJUwbul/GtZZnVF35ozHtxT5VpSpqFx5yhCDvg+/pMgyUErio5HD 0d21pwtDxz0kU4YgywUld3cdKuzgv1ojodFZDltEq07CRiH66pmSYcyMKfPE5sXEzwkL U7nOm2hUPz2VQ3zivC18Gl+7liJUjfLgYjLUnzzsw3GpBHjHKDoh7gjcjBOptR3T+eWt pft0pLPkhnOQU37HseeXBOT9k7DZ03CKsQJ2ir/D7+nPKM5zT61BUHFgRt5dGIgppfO4 L2zn6cJCIOWhaF6flib5MZAd9NbNOUsfFv2aTn1sn69fBG3NEKT8GXoYxolilVB4iuu2 Vhug== MIME-Version: 1.0 X-Received: by 10.50.164.227 with SMTP id yt3mr1628975igb.32.1424280518810; Wed, 18 Feb 2015 09:28:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Wed, 18 Feb 2015 09:28:38 -0800 (PST) In-Reply-To: References: Date: Wed, 18 Feb 2015 09:28:38 -0800 X-Google-Sender-Auth: tmSNpF9pcajyyeh_4ze-0RPCUik Message-ID: Subject: Re: TDMA slot(bh) From: Adrian Chadd To: bh , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 17:28:40 -0000 Yup. DBA gates the actual beacon transmit - if there's no beacon in the slot, then it's fine. SWBA is the software timer that fires just before DBA, so the software stack has a chance to program the hardware with a beacon and let the hardware get the packet DMA -> TX FIFO setup all correctly so that when it's DBA time (ie, time to /transmit/ the beacon), it's already ready to go. -adrian On 18 February 2015 at 09:09, bh wrote: > Dear Adrian > In ath_intr , there are a variable which decrease every swba, so wh= en the variable swbaintalval is zero, ap will send beacon .So I think the = period of swba is slot time, ap will send beacon every five slot, the beac= on interval is five slottime? > > Adrian Chadd =E7=BC=96=E5=86=99=EF=BC=9A > >>On 18 February 2015 at 07:55, bh wrote: >>> Dear >>> The default slotcnt=3D2 , becntival=3D5.For ap it will generate SW= BA every slot,it will send beacon every five slots, beacause ap fire the = DBA timer in every slot, so it will send data package in every slot. Is my= above understanding correct? >> >>It generates SWBA every beacon interval, which is calculated in >>ath_tdma_bintvalsetup(). >> >>Master stations beacon 20 times a second with the default config >>specified by the wiki. >> >> >>-adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 19 14:17:22 2015 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96AED39C for ; Thu, 19 Feb 2015 14:17:22 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C9F6BA6 for ; Thu, 19 Feb 2015 14:17:22 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t1JEHMlU066660 for ; Thu, 19 Feb 2015 14:17:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 193788] Intel WiFi Dual Band 7260 NIC not supported Date: Thu, 19 Feb 2015 14:17:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: s_bugzilla@nedprod.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 14:17:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193788 Niall Douglas changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |s_bugzilla@nedprod.com --- Comment #1 from Niall Douglas --- Note that NetBSD recently gained a brand new kernel driver for the following Intel Wifi chipsets: * 7260 * 3160 * 7265 Its man page is here: http://netbsd.gw.com/cgi-bin/man-cgi?iwm+4+NetBSD-current Its source code is here: https://github.com/jsonn/src/blob/a36ed4489eb51ed93b5bc8930d530831103f2f58/sys/dev/pci/if_iwmreg.h https://github.com/jsonn/src/blob/a36ed4489eb51ed93b5bc8930d530831103f2f58/sys/dev/pci/if_iwmvar.h https://github.com/jsonn/src/blob/a36ed4489eb51ed93b5bc8930d530831103f2f58/sys/dev/pci/if_iwm.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-wireless@FreeBSD.ORG Thu Feb 19 16:41:32 2015 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83D2E771 for ; Thu, 19 Feb 2015 16:41:32 +0000 (UTC) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4640EE13 for ; Thu, 19 Feb 2015 16:41:32 +0000 (UTC) Received: by mail-ig0-f169.google.com with SMTP id hl2so1477543igb.0 for ; Thu, 19 Feb 2015 08:41:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=WO9YM9cTCEWY8l2RHuuuzTGtlf1syQyRX5SL+/SK/aY=; b=NW5Vl+0gHxl9aq8URFJzU/1nPRt69Y6NxhkLgJZTtXh1ffUG0b54qhDt9YlfNwsjC+ cEOvIoQ6O7PvBJKi1Ru4q7KvFgSJfAeXyOjDU5MZhRE7xVawfj7Qtny6GAPtSIP+2swI NFJL/J/Wd1ES4vun72bDiswLxP7fykNG1WnxxP/7Plqu3vedeuzm2y8v6T49zIM9miWe 1LLakIrPVO8aVSJJJsvdNedbx+5rwx09VBGAyX2E5dJC97DG/9nf1g2vT/2nyJ+fawpz Ju4Bq6n5zPAL2z4nC3cvkX2Z5C2i8qhOLypq9ga6H0l9sq/frw09hZerY3zhLzvBB/c4 yLOg== MIME-Version: 1.0 X-Received: by 10.50.164.227 with SMTP id yt3mr8455582igb.32.1424364091691; Thu, 19 Feb 2015 08:41:31 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.17.66 with HTTP; Thu, 19 Feb 2015 08:41:31 -0800 (PST) In-Reply-To: <4e2942f9.fdd.14b9dd49b7e.Coremail.u8j9@163.com> References: <4e2942f9.fdd.14b9dd49b7e.Coremail.u8j9@163.com> Date: Thu, 19 Feb 2015 08:41:31 -0800 X-Google-Sender-Auth: igsV1k0XhX6qsT35QIUAwBhSeMc Message-ID: Subject: Re: TDMA slot(bh) From: Adrian Chadd To: =?UTF-8?B?5a2Q5paH?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 16:41:32 -0000 The whole point here is that DBA is used to control the start of the slot times, and SWBA is used to only send out actual beacon frames in multiples of that. normally you'd have SWBA be just before DBA, and and they'd have the same interval. Here DBA is used primarily to gate the start of the slot time for that particular device, and it only bothers sending the beacon frame every 'tdmaswba' DBA intervals. The beacons are used to announce that the device is there and to update RTT estimates; it's not doing anything like gating broadcast traffic. -adrian On 18 February 2015 at 09:55, =E5=AD=90=E6=96=87 wrote: > Dear Adrian > In HAL_INT_SWBA handler of ath_intr funtion . What means tdmaswba? I f= ound the tdmaswba default is five and when it decrease to zero ,the ap wi= ll send out the beacon package. From here I fell every SWBA is the start of= the slot? > > > > > -- > =E5=8F=91=E8=87=AA=E6=88=91=E7=9A=84=E7=BD=91=E6=98=93=E9=82=AE=E7=AE=B1= =E6=89=8B=E6=9C=BA=E6=99=BA=E8=83=BD=E7=89=88 > > > =E5=9C=A8 2015-02-19 01:28:38=EF=BC=8C"Adrian Chadd" = =E5=86=99=E9=81=93=EF=BC=9A >>Yup. >> >>DBA gates the actual beacon transmit - if there's no beacon in the >>slot, then it's fine. >> >>SWBA is the software timer that fires just before DBA, so the software >>stack has a chance to program the hardware with a beacon and let the >>hardware get the packet DMA -> TX FIFO setup all correctly so that >>when it's DBA time (ie, time to /transmit/ the beacon), it's already >>ready to go. >> >> >>-adrian >> >> >>On 18 February 2015 at 09:09, bh wrote: >>> Dear Adrian >>> In ath_intr , there are a variable which decrease every swba, so = when the variable swbaintalval is zero, ap will send beacon .So I think th= e period of swba is slot time, ap will send beacon every five slot, the be= acon interval is five slottime? >>> >>> Adrian Chadd =E7=BC=96=E5=86=99=EF=BC=9A >>> >>>>On 18 February 2015 at 07:55, bh wrote: >>>>> Dear >>>>> The default slotcnt=3D2 , becntival=3D5.For ap it will generate = SWBA every slot,it will send beacon every five slots, beacause ap fire th= e DBA timer in every slot, so it will send data package in every slot. Is = my above understanding correct? >>>> >>>>It generates SWBA every beacon interval, which is calculated in >>>>ath_tdma_bintvalsetup(). >>>> >>>>Master stations beacon 20 times a second with the default config >>>>specified by the wiki. >>>> >>>> >>>>-adrian