From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:22:30 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4A6B9F54; Thu, 4 Apr 2013 00:22:30 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 029B8B28; Thu, 4 Apr 2013 00:22:29 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id wc20so2027108obb.15 for ; Wed, 03 Apr 2013 17:22:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=R7GIyRtGcR/08wCCaBqbvEuGVZyR82ypMLYfQj4HC+M=; b=QJF6xSQz7QDtvtzNOkMVQE0mah23adVRr8T7K3G3pKBUw1RRUfG1GhGdH70dRkLpzO 5xSEfaMjgmQGbzERq3FE7xE7JqsQx86WUy7qi2Kt3PFGhzAdG77okYXG+p5gmDitjJt4 nAzgsTbSLOPp0NQoYuLabIIlNL1oR7qWCnql88cO3GCWj+2SHCY5AtDJ61QHOjaxjThW cYU4gGsbzPwOce2R/ep7NdRJugny855/FPeYWlMFRdhmQW9pfoiRJ0XR7GUv11Ut8IS4 l6sQzlgtDV06LTjOzWB13tKXXzFkLe8+sQby9ZWP5Q5NdpJlgxLeIHYpyBbDmwl/5SUg ic9A== X-Received: by 10.182.169.103 with SMTP id ad7mr2588712obc.51.1365034949678; Wed, 03 Apr 2013 17:22:29 -0700 (PDT) Received: from [192.168.1.34] (c-98-212-197-211.hsd1.il.comcast.net. [98.212.197.211]) by mx.google.com with ESMTPS id a3sm4337886oee.8.2013.04.03.17.22.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 17:22:29 -0700 (PDT) Message-ID: <515CC7C3.3070608@gmail.com> Date: Wed, 03 Apr 2013 19:22:27 -0500 From: Joshua Isom User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: ath not working after a motherboard and ram upgrade References: <515892C4.1060002@gmail.com> <515B4E16.3050901@gmail.com> <515B76A6.7080804@gmail.com> <515B78C2.20609@gmail.com> <515B8233.9000603@gmail.com> <515B8914.8030303@gmail.com> <515CAA36.70002@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 04 Apr 2013 00:22:30 -0000 I added -ampdu to rc.conf and it connected to the network, but still dropped packets. I'm not getting the network to work when I try it manually after boot. It could be me though, or something else wrong or not working properly. It's the same kernel as before except the patch, and that was the only time I was getting those messages. I checked hw.ath before, and after, there's no difference. hw.ath.longcal: 30 hw.ath.shortcal: 100 hw.ath.resetcal: 1200 hw.ath.anical: 100 hw.ath.rxbuf: 512 hw.ath.txbuf: 512 hw.ath.txbuf_mgmt: 32 hw.ath.bstuck: 4 hw.ath.debug: 0 hw.ath.hal.debug: 0 On 4/3/2013 6:16 PM, Adrian Chadd wrote: > Hi, > > Please try again, but tell me what the output of : > > sysctl hw.ath > > is. LEave ampdu on for now. > > The allocation failures are a bit odd; that only happens when you've > compiled it without the 11n option enabled. > > > > Adrian >