From owner-freebsd-wireless@FreeBSD.ORG Sat Jan 31 19:00:05 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 1156E5E2 for ; Sat, 31 Jan 2015 19:00:05 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 CB5B3DFD for ; Sat, 31 Jan 2015 19:00:04 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id l13so9614092iga.1 for ; Sat, 31 Jan 2015 11:00:04 -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=tJf4ogcBSaqTYCb315Nl2iz56f2DOPd6cZFkh1pjvfg=; b=R3zSpLJ5fIgTVB7DtEiTh3Z42Tq5XMz2/gNsddlfAJXFVJ0zGScZNAIEYFymLq11rK 7J/iIb+ssgIA9PiOn4KVhe4xfZ0/JS6z71w2ArkrSPbe7CqAbVOQ5hj0mKWT1x0XESup ZY7bgmuK6x4qbAD3X8rR+WY+by8lytZBhdOdH8TBzdo+ks1R7rgJ5WSNRGYKymBGou9c WkURRbZMx7jPD5CoF8pkEJQq5gBf3z1lphJUHQOh5cia5G3kGzN00Lw7oGbXsPBZqi74 oQdsJEYr83jsxi+t0tTr89I9IL7uyW89vqlQjMcA6+kN7EFM1iNesFDqosW2FiPTJ5X7 pwAw== MIME-Version: 1.0 X-Received: by 10.50.93.70 with SMTP id cs6mr3475424igb.6.1422730804059; Sat, 31 Jan 2015 11:00:04 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Sat, 31 Jan 2015 11:00:03 -0800 (PST) In-Reply-To: References: Date: Sat, 31 Jan 2015 11:00:03 -0800 X-Google-Sender-Auth: hqUssmPwuZb4Vtkcc5cBj6czgwg 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: Sat, 31 Jan 2015 19:00:05 -0000 Hi, please try updating to -HEAD. It's possible that'll fix things. 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"