On Sun, 15 Jul 2012 09:39:03 -0700
m...@freebsd.org wrote:
> On Sat, Jul 14, 2012 at 8:39 AM, Justin Hibbits
> wrote:
> > On Jul 13, 2012, at 12:20 AM, m...@freebsd.org wrote:
> >
> >> On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits
> >> wrote:
> >>>
> >>> On Jul 12, 2012, at 9:11 PM, m...@freeb
On Sat, Jul 14, 2012 at 8:39 AM, Justin Hibbits wrote:
> On Jul 13, 2012, at 12:20 AM, m...@freebsd.org wrote:
>
>> On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits
>> wrote:
>>>
>>> On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
>>>
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
On Sat, Jul 14, 2012 at 8:39 AM, Justin Hibbits wrote:
> On Jul 13, 2012, at 12:20 AM, m...@freebsd.org wrote:
>
>> On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits
>> wrote:
>>>
>>> On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
>>>
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
On Jul 13, 2012, at 12:20 AM, m...@freebsd.org wrote:
On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits
wrote:
On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits >
wrote:
When tracking down a panic exposed by INVARIANTS, I tried setting
DEBU
On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits wrote:
> On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
>
>> On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
>> wrote:
>>>
>>> When tracking down a panic exposed by INVARIANTS, I tried setting
>>> DEBUG_MEMGUARD, so I could find the culprit th
On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
wrote:
When tracking down a panic exposed by INVARIANTS, I tried setting
DEBUG_MEMGUARD, so I could find the culprit that's trashing freed
memory.
However, this causes a panic at bootup. It
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits wrote:
> When tracking down a panic exposed by INVARIANTS, I tried setting
> DEBUG_MEMGUARD, so I could find the culprit that's trashing freed memory.
> However, this causes a panic at bootup. It shows up right after the first
> WARNING: WITNESS mes
When tracking down a panic exposed by INVARIANTS, I tried setting
DEBUG_MEMGUARD, so I could find the culprit that's trashing freed
memory. However, this causes a panic at bootup. It shows up right
after the first WARNING: WITNESS message, with the following:
panic: kmem_suballoc: bad sta