From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 17:29:13 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 2052366D for ; Sun, 31 Mar 2013 17:29:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by mx1.freebsd.org (Postfix) with ESMTP id AFF9A7AE for ; Sun, 31 Mar 2013 17:29:12 +0000 (UTC) Received: by mail-wg0-f53.google.com with SMTP id c11so1606828wgh.20 for ; Sun, 31 Mar 2013 10:29:06 -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=kxrOQ0xJGKXnUL35Rvr7NZuGV/0ZuBGCV6LyuHPmiTo=; b=KRgr0cuJdBSAQTzZbZR8Eh4NS2mrfAHrjCUQ/I2j/BkqCrWtrs3DDhtO+ZDNljA4qp RT5BkvxV/poT7ujJMJo8njwdIbTo6WSoXna6UclCH9E1PAEB8Kswgu4HF+ma0DJMf1Fs gWh2NPVGuiU5RUhnicsHzqxrc+ThCy/Jz0XqibdIrMn8qtwEbTs5qsE5aKHA1msYbrYV Sk0Hu/sLLlYpU7ne1huZMfOFHIh5nnNPSD9D7hInv9Z+xiTpOnxCMG9XjqCU72ky+HkH UNB7i/gVSyhg3AzPr2OYVVxYxQDdxG3kGqCRIygspRJp5KbitTZfoydUtSeq5Dcqysrr 45eQ== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr6588206wid.29.1364750946347; Sun, 31 Mar 2013 10:29:06 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sun, 31 Mar 2013 10:29:06 -0700 (PDT) In-Reply-To: <51585558.8040202@gmail.com> References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> Date: Sun, 31 Mar 2013 10:29:06 -0700 X-Google-Sender-Auth: mM4B3EZxIRY4ptthp2AmRTzQkhQ 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: Sun, 31 Mar 2013 17:29:13 -0000 ... that message is because it's scanning. :-) Try booting it with only 2GB of physical RAM. It may be something odd to do with how the DMA code works; the ath NIC is a 32 bit PCI device. I need to make sure it's totally 64 bit clean - not only 64 bit pointer clean, but all the mbufs need to be in the lower 32 bits of physical memory :) Adrian On 31 March 2013 08:25, Joshua Isom wrote: > I tried updating today to the new code, it seemed to make it worse and never > get decent ping times. With the code from before, it's dependent on boot, > either it will work fine on boot or fail. > > But it has to be related to the "handled npkts 0" message. When I'm getting > no messages, it's perfect. The number and speed of the messages is the > inverse of the network quality. When it's an intermittent loss, it degrades > a couple seconds before the messages start. > > > On 3/31/2013 7:06 AM, Joshua Isom wrote: >> >> If I drop down to one 8Gb stick, and I don't have other wifi devices >> near causing interference, I can get a reliable connection and low loss. >> If I have 16Gb, I can get about a minute or two of decent ping times >> before it degrades to multi-second pings of the router. Even at 8Gb, >> it's not guaranteed on boot, but rebooting does seem to fix it. At >> 16Gb, I tried two different sticks just to see if maybe it was one bad >> chip but it didn't change it. That means it's probably an address >> conflict, or cache size issue, right? >> >> On 3/31/2013 1:25 AM, Adrian Chadd wrote: >>> >>> does downgrading the motherboard/ram fix it? >>> >>> You were already running 64 bit, right? What if you just boot with 2gb >>> of ram? >>> >>> >>> >>> >>> adrian >>> >