From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 01:12:47 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 03E777FD for ; Sun, 31 Mar 2013 01:12:47 +0000 (UTC) (envelope-from jrisom@gmail.com) Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id BED062D3 for ; Sun, 31 Mar 2013 01:12:46 +0000 (UTC) Received: by mail-yh0-f51.google.com with SMTP id q1so191406yhf.10 for ; Sat, 30 Mar 2013 18:12:46 -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:subject :content-type:content-transfer-encoding; bh=kZnbDX/cn/nGdGas987LruCJJbqnn3NDUxTcUJQRLxc=; b=CzGzqREymU3++I77sGkFhh1fYXPxzUThFeFkaGQfZu7Mxd42jzwGaHx+x+WZTlz9l2 5OmBnR6e9E+ta8YRNJ+mSUKANiLLKSl65ubstF7xDfTIXCxgZntpUDUo12Lt6FjnxQGO INx9dMdPZKa1EHluA1v63yVapMlHqo5U6YTDJKsYtmnbttxkJxQ/nGbNjzAouZ2Nwgsm eezHjIqJvASnE8KTnihwY6lJF7NP4ryWU06Dg1ekdsnY4KLhkkoJj+bR9y4piqJayKqO PjRWax2SYTYg2MdUihqFJdIX6QgfvZH7p4qOvVyhkPcCb1SogEAy2yPpJrRffVmR4Edw 1b+A== X-Received: by 10.236.98.66 with SMTP id u42mr5003912yhf.157.1364691889886; Sat, 30 Mar 2013 18:04:49 -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 u80sm14146126yhj.5.2013.03.30.18.04.48 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 30 Mar 2013 18:04:49 -0700 (PDT) Message-ID: <51578BAC.4090608@gmail.com> Date: Sat, 30 Mar 2013 20:04:44 -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: "freebsd-wireless@freebsd.org" Subject: ath not working after a motherboard and ram upgrade Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 01:12:47 -0000 I've been longing to upgrade my motherboard and ram, and with a tax refund it came time. The current kernel was working well enough for me, where the only ath problems were my antenna and "harmless." After upgrading, 2Gb DDR2 to 32Gb DDR3, I've yet to get ath to be stable. The only system changes were motherboard, a cheap video card, and ram. There's periods where ath will work, then packet loss grows until it's unusable. When I scan, I can find the router, and when I'm connected I get an RSSI of 10.5 after I hung the antenna over the monitor, better than before. I'm getting a lot of kernel debug logs, but when I'm looking I can't notice anything specific. I still need to dig through the logs but I probably couldn't match up the logs with what I was doing at the time. What steps should I try to figure out why a motherboard and ram change would break the networking?