From owner-freebsd-wireless@FreeBSD.ORG Thu Aug 21 17:46:30 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EAEB99B3 for ; Thu, 21 Aug 2014 17:46:30 +0000 (UTC) Received: from nm46-vm10.bullet.mail.bf1.yahoo.com (nm46-vm10.bullet.mail.bf1.yahoo.com [216.109.114.203]) by mx1.freebsd.org (Postfix) with ESMTP id 913B0325D for ; Thu, 21 Aug 2014 17:46:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1408643014; bh=QygiCgvSDhJSiogf+q6AOGVPekj5+ohaIiD3APwpJfQ=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:From:Subject; b=an2vZnuXCHe9PPHsQMTAeFJJaGwLIFIUhj3jTs8xy38hd+1c2rwk1BL4pD+o3G0CK2JwsnWtgm+kz9fqJBZFsoYlsExMWxhVk8avn5N4cd0zg1koaKoO6I0uAgZJoy4N0tNNaUtveYuTJGQb6+MSta/OLxia7pKiMuKUGA6ujpaTFKGL1BtwwDGTPqB+E078FWVXXdK9dsKac/77g6SG4I8rHqSrY8KrtD5BXMm5loLhh0tLWo2zEdnKu1mN5Cr9IgRNzJAB9jRftI4TnSL9JLO2XaoJATG1VjGcNXHhHv8Jr6Vtf3Wk2pHUHTlRf7kNP0we4ha5DO8aU2/K9bwN7w== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.ca; b=rNFN0rGSWv1IxVCO2SjGZdmqQh4MABhySI7WOdR5xdPAE5j/XbJ9NGRPieDVgTgYE5lodWdHv0TaI7SKUoNj8R9UIO8Xq1/pJsqpp4T8vgM/db23qn/71ZV+eQGGyDfSXi5Z0EnPgTdDneieVNTeAp5PnsqFgvqTpSwzllmMT+gGDVRH52o9eBYXr/RfAGfw3RDrhrUo7Rz2+kycF69DvaTPlSlwBNTvuc32jc1COsbekMCPaZNWW11ggusmsbkcFARqCJ8uKsRxEBXvOM7ExtYVBTt0OKqpVAj4Nn1V9E9/NMxUp214ihAetYSnGTjzOWPPQhjbBxR5Cjy03IKqWw==; Received: from [98.139.212.151] by nm46.bullet.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 Received: from [98.139.213.9] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 Received: from [127.0.0.1] by smtp109.mail.bf1.yahoo.com with NNFMP; 21 Aug 2014 17:43:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1408643014; bh=QygiCgvSDhJSiogf+q6AOGVPekj5+ohaIiD3APwpJfQ=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=jl6ho2IlyG1VY7D559VoWf5ORWJH9l/7NTEwQd0N813TcgxIgyc6hk96FlOsDLr+XgxRS0jsINEUrxFc3nnlAjECpwJdUmDHzvNVAZxG/aLh8tUakXalG98XKL+M3jqt9TgokHUiHZzX3e6LFTLchxKKcWhJNSMUeADfufnaKyA= X-Yahoo-Newman-Id: 461933.62812.bm@smtp109.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: sOdV7DQVM1l0Ts0FQ4ZlOa8w9uvnN3dsKvsu0VAPF4Umc0T nOx42F.bzHjJ4scuTF9984Yeeu.jDcgrCvGhYJfAfpzr1qbfd_QNv3GGLk78 MNhsi3Zy4f1SJHVX2Tq8E9D8zsNzOpqglHkO7LRM5FKY29sdG59pfIBRj00B vPPEpaxKt_q82QN_FLzTymFI5DViicl2CzMtzG_iw6nJ.faWnnWf4vFXwDRE h2IW9BoADVzppGiXLuaKzNCp64Akmb8tFuyVxX5aZS8a7nEFPs_BPR0eKdJi t9FkBXPIACiTs862UzXKlZ.qOPw3X9eC1GjbZV8rQgGCvHTT2w8TB57iHEpQ oBnU5W9.Fn0qf13.Cjh7OqTas7s_vzl8iwlD7yBvSFjPfSflPOwNk9RUuTzp OnoH3fr4uXQtdUgjTlGi1s_0l5w5B_YsyZux5.UNymaUFDOK3r6Pabh5Iabn 8aPglYxW8.phWWNJUAMSLymDB5CuMA20b5pZvh7q_CT5GsJU9lLv5MFHkg8u THJ1Wvfm8LxP0i1DZcIss5VrlJiCO9ySzFWKmBA-- X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: by mail-la0-f54.google.com with SMTP id hz20so9018671lab.13 for ; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.112.4.70 with SMTP id i6mr125953lbi.54.1408643012844; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) Received: by 10.112.230.9 with HTTP; Thu, 21 Aug 2014 10:43:32 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 11:43:32 -0600 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "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, 21 Aug 2014 17:46:31 -0000 On Wed, Aug 20, 2014 at 5:55 PM, Adrian Chadd wrote: > On 20 August 2014 16:33, PseudoCylon wrote: >> On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd wrote: >>> Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? >> >> CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx >> rates usually hit mcs 12 to 14 with 2s ht20 ap) >> >>> >>> There's a handful of things we can look at to see what's causing it >>> once some more digging is done. >>> >>> (Eg, HT? could be guard interval. OFDM has similar issues, there's >>> typically ways to configure how much time between each symbol is left >>> before transmitting the next one. It may not be doing CTS-to-self, or >>> it may not be advertising the right thing via NAV, or it may be >>> ignoring CCK, or the receive gain tables are all messed up, etc.) >> >> I have looked into stuff I was able to dig out from other src codes, >> ie protection, ifs, nav, bk slot. (Because I do not have datasheet, >> every thing is based on my guesses.) One thing I could not figure out >> is if on-chip memory is properly allocated for rx pkt. (It seems >> memory can be allocated for different things, ie beacon, enc keys). >> > > So CRC errors are pretty normal with wifi. Even a tiny bit of > interference generates CRC errors. That's why there's an ACK and retry > mechanism. :P > > If you're hitting MCS 12 then you're doing pretty well. A-MPDU will > see lots of CRC errors just because of how long the transmissions are > and how easily corrupted things can get. That's again why there's a > quick retry mechanism for things. To clarify, tx on run hits mcs 12 to 14. I assume tx on run is working. But, tx on ap can hit 39mbps at the best, most likely due to high rx crc error rates on run. > > What %age errors are you seeing? Constantly 70 to 80 rx crc errors/sec during active downloads. (h/w does not count total rx, so cannot tell the %.) > > > > > -a