From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 31 18:38:46 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 C17F7509 for ; Sun, 31 Mar 2013 18:38:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by mx1.freebsd.org (Postfix) with ESMTP id 5BE2B9D3 for ; Sun, 31 Mar 2013 18:38:46 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id hm14so1058634wib.4 for ; Sun, 31 Mar 2013 11:38:45 -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=vRmQY4iwjmPazXERGCzANRtYp+/82tBkbsJSOavb9sI=; b=sXnnnBNyRGy8AG4x7to0anXzNTdwOmFCxL2nPIrhGyhjiyVT+7Rk0E7SalBqQLNzr+ OidI4Oh+NATD5HOHYdwHDtRw6QlzZVK2v4jAuVIGQb6fuWGk0ZnxpO6qRzAphKGjJMsj waGkl0NNZpNzkXt2jzajVl7pzHvWiYAMUtKhXbVo3eNlD/SyA4zsVLmmGZ1+//QaT8pE jCYGheNHxtVBft9Lc/i6BtsRlZZZVgp6FBILdLO7T/iQoOFjJ0epgrK3TnlQWXCCOax9 vembOYaWeuXT1zOX/3rWXwmpkjijaQwZTQf6YJmFjY4WKyI0hDpIIvqooMVdF7hueaVb twZQ== MIME-Version: 1.0 X-Received: by 10.194.120.169 with SMTP id ld9mr12340471wjb.24.1364755125563; Sun, 31 Mar 2013 11:38:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Sun, 31 Mar 2013 11:38:45 -0700 (PDT) In-Reply-To: <5158773C.4080201@gmail.com> References: <51578BAC.4090608@gmail.com> <515826B9.6070509@gmail.com> <51585558.8040202@gmail.com> <5158773C.4080201@gmail.com> Date: Sun, 31 Mar 2013 11:38:45 -0700 X-Google-Sender-Auth: 18T4oWmfksSuci58-gweYvL0FIs 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 18:38:46 -0000 On 31 March 2013 10:49, Joshua Isom wrote: > I seems someone working on the kernel's already figured out how to deal with > this. The hw.physmem sysctl can be set at boot time, with 2Gb it seems to > be working fine. I reinstalled all the sticks, and it's working fine with > the sysctl set to 2Gb. Ooooooo Yay! I mean, damn, that's busted. But yay, now we can narrow down what the problem is! Try bumping it to 4GB. It should be fine at that. If it is, please create a PR with all the above information and I'll start re-reviewing the DMA / buffer code to see what's going on. Thanks! Adrian