Date: Mon, 1 Apr 2013 15:47:45 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Joshua Isom <jrisom@gmail.com> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: ath not working after a motherboard and ram upgrade Message-ID: <CAJ-Vmok-A%2BBPTZrwWM4PT692B9qTCHzoOCAioah%2BGopL8n4JbQ@mail.gmail.com> In-Reply-To: <5159FF12.8030702@gmail.com> References: <515892C4.1060002@gmail.com> <5158b7db.897aec0a.42d0.ffffaac4@mx.google.com> <CAJ-VmomxTm3RN6XDyRwX9SuSaiK3tqOQAJHK0rHM=j_T-vXDnA@mail.gmail.com> <5159F66B.2040600@gmail.com> <CAJ-Vmonv3GfwVKGyHruF%2BnADtKnZQpvOJH-cB4uCmK0TmbMypg@mail.gmail.com> <5159FF12.8030702@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
... 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 <jrisom@gmail.com> 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 >> > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok-A%2BBPTZrwWM4PT692B9qTCHzoOCAioah%2BGopL8n4JbQ>