Re: mbuf trash panic turned into a printf for now

On 6/26/05, Mike Silbersack <silby_at_silby.com> wrote:
> 
> Since the mbuf trash panic is being reported more often now, and we
> haven't tracked down why yet, I've turned it into a printf for now.  This
> means that it's safe to upgrade to -current even if you might be affected.
> :)
> 
> And the more reports, the better, keep them coming if you see the "Memory
> modified after free" message.

Well .. i just updated my system to today's CURRENT and now (for the
first time) see a whole host of "Memory modified after free" messages
... i tried breaking into the debugger .. but apparently KDB doesn't
exactly like USB keyboards .. as the second i entered the debugger my
keyboard no longer worked and i had to push the reset button.

Below is part of the list of messages i have been seeing:
------
Memory modified after free 0xffffff003d640800(256) val=2cc0de _at_
0xffffff003d64088c
Memory modified after free 0xffffff003d45fc00(256) val=2cc0de _at_
0xffffff003d45fc8c
Memory modified after free 0xffffff003d640200(256) val=2cc0de _at_
0xffffff003d6402b8
Memory modified after free 0xffffff003caa3000(256) val=2cc0de _at_
0xffffff003caa30c0
Memory modified after free 0xffffff003d45f400(256) val=2cc0de _at_
0xffffff003d45f48c
Memory modified after free 0xffffff003d640400(256) val=2cc0de _at_
0xffffff003d640474
Memory modified after free 0xffffff003d640700(256) val=2cc0de _at_
0xffffff003d64078c
Memory modified after free 0xffffff003d640a00(256) val=2cc0de _at_
0xffffff003d640a84
Memory modified after free 0xffffff003d761100(256) val=2cc0de _at_
0xffffff003d761174
Memory modified after free 0xffffff003d761500(256) val=2cc0de _at_
0xffffff003d761584
Memory modified after free 0xffffff003d761d00(256) val=2cc0de _at_
0xffffff003d761d94
Memory modified after free 0xffffff003ca22200(256) val=2cc0de _at_
0xffffff003ca22294
Memory modified after free 0xffffff003ca22600(256) val=2cc0de _at_
0xffffff003ca2268c
Memory modified after free 0xffffff003ca22a00(256) val=2cc0de _at_
0xffffff003ca22a8c
------

and the list goes on and on .. though apparently the "value" is Always
2cc0de in my case.

To clarify i have never been plagued by the actual mbuf-panic ... just
now after updating to todays CURRENT i am seeing these INVARIANT
messages

If you have suggestions on how i can provide additional details please
let me know :)

-- 
  Pascal Hofstee