... 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.
On 1 April 2013 14:41, Joshua Isom <jri...@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.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"