From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 4 00:26:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5282BFFB for ; Thu, 4 Apr 2013 00:26:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by mx1.freebsd.org (Postfix) with ESMTP id 296E0B6B for ; Thu, 4 Apr 2013 00:26:05 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id q11so1123234pdj.25 for ; Wed, 03 Apr 2013 17:26:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9qzTm0ekd8E07WUeymGuuZ2SciZueGqFsEUEykO+Jlg=; b=QG6T0RJelV0N0ueFt6Fpff7lPKXmDDt9cRocfaxWPz2Jib4Z8JQYtntFkDAJgYuO/d +Vxbwbxzkvsra2w6yzaUh2I7qZyvezsd3lJ1tcAhja8IlMUIyGETTX1L9pWuKDpmBV5J oE5mc0RNvtqGJL0aFSsMbkjvTTazTMeSI9R0KKzJuMHVmE3SvxQpAyV9kgeM5vfmdMjj HA0mrTo3s+r5GAEauyMq4mIYJrpTvgY2W39RP9DsYDtB4slNIbL/TU3ofyurQCVUVTL8 k2G5XRo2f8wmJEyisxZlIVRHpSj2TMNY3JGRLAslKKI3K1s4n/clSv62UkBZX4PjgnT3 kbFw== MIME-Version: 1.0 X-Received: by 10.66.116.12 with SMTP id js12mr6385640pab.149.1365035164723; Wed, 03 Apr 2013 17:26:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.61.234 with HTTP; Wed, 3 Apr 2013 17:26:04 -0700 (PDT) In-Reply-To: <515CC7C3.3070608@gmail.com> 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> <515CC7C3.3070608@gmail.com> Date: Wed, 3 Apr 2013 17:26:04 -0700 X-Google-Sender-Auth: A_RSMKGxKvKGw1weWJ3pOCVVzDE Message-ID: Subject: Re: ath not working after a motherboard and ram upgrade From: Adrian Chadd To: Joshua Isom Content-Type: text/plain; charset=ISO-8859-1 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:26:05 -0000 On 3 April 2013 17:22, Joshua Isom wrote: > 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 Ok. So it's not kooky stuff with aggregation handling. That said, you're already running a far-away network, so a lack of aggregation means that you're not doing software retried packets. :-) > 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 CAn you please dump out the contents of hw.busdma after it's run and failed for a while? Then ifconfig wlan0 ; kldunload if_ath_pci ; kldload if_ath ; sysctl hw.busdma again. I'd like to see if it's leaking bounce buffers now. > only time I was getting those messages. I checked hw.ath before, and after, > there's no difference. So you're still seeing the FIFO allocation failures with this patch? The reason why RX FIFO allocations would fail here is because the bounce buffer allocation is failing. I doubt the mbuf allocation is failing. > 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 Yup, that's correct. Adrian