From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 21:46:45 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 D602D879 for ; Mon, 1 Apr 2013 21:46:45 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id 708942CC for ; Mon, 1 Apr 2013 21:46:44 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id z12so2541351wgg.35 for ; Mon, 01 Apr 2013 14:46:44 -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=SNNdVGNigLMXEN48+KTheHUowzWgqE/jYMCwaSGZpEk=; b=g8cz66TRZk37CWCTTH/TW+Iwod7h7qexU8Q2p7UfrYJpf/dnyBNXYGhUKG6NIuvMis fMNxyBtgKKIUnRBt5y2an6u32kxtl9aPtAujydMODEj8IvGaIkRhpEHsQsrSmQReJ5U4 lus6jrls4vQy+xT+WMFD1hIXf9JkKn4bbiBPUecVP0w7wui4480VDbGu3flYvTg0lNfo CMvgcsWweLPvpnUDyp9+OeJSzuaolDdV46h2OUY4v/3Lm92GilmSeFaMjS1d/ia2vhtT 5Fywjac9HN0HUDsiF1zmQQs7XXHlDEQZoekLTSyqfSl7XgQBIvA5y14qTGlpC2f8Jvo1 pm7g== MIME-Version: 1.0 X-Received: by 10.181.11.164 with SMTP id ej4mr12115787wid.29.1364852804034; Mon, 01 Apr 2013 14:46:44 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 14:46:43 -0700 (PDT) In-Reply-To: <5159FF12.8030702@gmail.com> 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 14:46:43 -0700 X-Google-Sender-Auth: icD1rPd2qTpC6fotBFk8qF8ZCdU 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: Mon, 01 Apr 2013 21:46:45 -0000 I'm still trying to chase down the root cause of these. I doubt it's specifically bceause of your particular issue. Adrian On 1 April 2013 14:41, Joshua Isom wrote: > I was the same. I got these two messages, but I'm only assuming it's > related because the val makes me think of the pci id. These were while > using 16GB, and trying an ifconfig scan. > > Apr 1 16:32:51 jri kernel: Memory modified after free > 0xfffffe003ce3a000(4096) val=168c000c @ 0xfffffe003ce3a000 > Apr 1 16:32:58 jri kernel: Memory modified after free > 0xfffffe003ce36000(4096) val=168c000c @ 0xfffffe003ce36000 > > > > On 4/1/2013 4:11 PM, Adrian Chadd wrote: >> >> update again again; I just did some TX related changes. >> >> >> >> adrian >> > >