From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 14 02:40:33 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 5194EAD7; Sat, 14 Feb 2015 02:40:33 +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 13D27E36; Sat, 14 Feb 2015 02:40:33 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id b16so14398198igk.1; Fri, 13 Feb 2015 18:40:32 -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=4w7RcwvdnBC4bDbQMG1zCpfCdXo45z8ClCzXrfm77GM=; b=BxgZkBdxLKvjIWfStAy6o1uVOGO9vFVnwXAZjpJdCkKLruUfiV4ry0tIyLADBv2wPC OpyEirrtkDDD4BBY1Rdl/tLR/TikXTNBmu0u6KfNUr97kDWXT5or/VxdW8zX4Dqe7p3G Eia0WxYVzvJH9zz/7oVi0T4/vR79rdJuXmK9rSUFxJO6qI3RA1rQ9Z826wzAZ6qSCx3X KeOREUPoJX70CleEWFrNIyhKnX1x/wszJwI0gTZezIqubvSnzG/8ckyveRb6i7lUbSo0 l7NDRkHXwoQ6YgrU8HvdYltuQj8ba/it1j0KS0I6WfmCSYqrkaGslTqNxtDFM/+hmu2u /RRg== X-Received: by 10.107.160.72 with SMTP id j69mr16324818ioe.0.1423881632429; Fri, 13 Feb 2015 18:40:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.120.35 with HTTP; Fri, 13 Feb 2015 18:40:12 -0800 (PST) In-Reply-To: References: From: Miguel Clara Date: Sat, 14 Feb 2015 02:40:12 +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: Sat, 14 Feb 2015 02:40:33 -0000 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? > 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" >