From owner-freebsd-wireless@FreeBSD.ORG Mon Apr 1 22:47:53 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 22E338AA for ; Mon, 1 Apr 2013 22:47:53 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f54.google.com (mail-wg0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id B16DE6F9 for ; Mon, 1 Apr 2013 22:47:52 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id a12so2497963wgh.33 for ; Mon, 01 Apr 2013 15:47: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=wJ7Z8Tnloc3hzxfLzhfSxyL1Z15cYkn9Sc60IzEnYbc=; b=bOLoWp9oIVgvTfnqGDWrzohVfzbWTnvssDJULwKulFsvP5RWCjlwj+XC0vJhHc+mzu eOTMl6zXU6Rq6JlrX/g+5LMlXTjksmA6tyzpNJ3NUyhNOxQeRbch2B6n7hHDgM2QOa0o AVEAB7dDGrmMsjKeP0lLwtC0y/ztLROLD6IkHIIL9GU5gDaDU04ul7MN9byZjsEvHw3P UKdUY4Kn7zdy8LqAYm+pVBykc4k7+p7E/vvLJJtsLGtc+Qf0G+pz1UUvp7v74GxYF+D+ iycALMgAH00zPJSw5DrI1heRt/1Ny2k6r70U7BlitwOlmU1/Yp96n/p3yiOok2Os+wq1 P5Lg== MIME-Version: 1.0 X-Received: by 10.194.171.74 with SMTP id as10mr18017787wjc.0.1364856465494; Mon, 01 Apr 2013 15:47:45 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.108.130 with HTTP; Mon, 1 Apr 2013 15:47:45 -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 15:47:45 -0700 X-Google-Sender-Auth: bIKKiiSr1ykfPmt-NB-9lRF_T_g 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 22:47:53 -0000 ... and that particular value means that some TX descriptor was written into free'd memory. Sigh. As I said, I'll chase this down later, but I don't think it's the root cause of your bug. I still have a lot more review of the TX path and descriptor handling but it may take some time. Thanks, 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 >> > >