From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 2 03:40:21 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 510F3520 for ; Tue, 2 Apr 2013 03:40:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id DCEE029E for ; Tue, 2 Apr 2013 03:40:20 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so2740378wib.5 for ; Mon, 01 Apr 2013 20:40:20 -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=KYS2pNdRNNLTghfRroD/lhBooF5HGtI3UbNJ6yTB4S4=; b=HUz7l+oBKJvoDFdODZBuUCIt3QVGFnZAjmDLk3zW60IP5wrZ08cEB4mNpfa8alFBLN zPslpO2a6OsN1qcbw9anc6/JmC6yNXugKqd+DeFrXqXNVMz8JW43SZAppQtN4ygu13+i IL8wOZDKCue2kqGAV4r6jMkVVyEyFXe1KWCvrKQjyYa38kEfUn+zCJv/ue0Wazm8DQIM wgw3XpKfoG5EYcS+N7BdeQAVgPzXKjE35XIbejM+s1z3iPKsja0T+/yDlnUKnV0zR5LM pxmSWC9DvXecHsR4+E7NocN5tEDv2ZO4fpxCWV2IceQm9AXxPB+MDL7X/eDuWA7cjXw9 aCkg== MIME-Version: 1.0 X-Received: by 10.180.81.232 with SMTP id d8mr12976825wiy.25.1364874020050; Mon, 01 Apr 2013 20:40:20 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 20:40:19 -0700 (PDT) In-Reply-To: References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <5159F66B.2040600@gmail.com> <5159FF12.8030702@gmail.com> Date: Mon, 1 Apr 2013 20:40:19 -0700 X-Google-Sender-Auth: ePWf4n048kdNEhwRuke68yG8mrc 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: Tue, 02 Apr 2013 03:40:21 -0000 .. and please supply the output of 'sysctl hw.busdma' too when it's failing: sysctl hw.busdma > ~/sysctl-busdma.txt and include that too. Thanks, adrian On 1 April 2013 20:24, Adrian Chadd wrote: > Hi Joshua, > > Would you please reboot back into full RAM, let it fail for a bit, > then record dmesg: > > dmesg > ~/dmesg.txt > > and sysctl: > > sysctl dev.ath.0 > ~/sysctl.txt > > then reboot back to normal, and email me those two textfiles? > > Thanks, > > > Adrian