On Wed, Feb 01, 2006 at 11:44:27AM -0500, Andrew Gallatin wrote: > > Steve Kargl writes: > > On Wed, Feb 01, 2006 at 10:47:52AM -0500, Andrew Gallatin wrote: > > > WARNING: WITNESS option enabled, expect reduced performance. > > > Memory modified after free 0xffffff0000006d00(248) val=5 @ > 0xffffff0000006dd0 > > > kernel trap 9 with interrupts disabled > > > > You can trigger this panic without the red zone stuff. > > See my string of post from yesterday. Something went > > Your panic looks like the same panic as mine, but with memguard rather > than redzone. These systems do similar things, I suppose it is only > natural that they'd be hit by the same bug.
You get it without memguard, too. Kris suggested that I try memguard to capture the problem. Unfortunately, memguard actually made matters worse in that I did not even make it to single user mode before a panic. > > into sys/ on 2006-01-26 that is causing the problems. > > I suspect the pts code, but can't prove it, yet. > > I built a kernel without 'device pty' thus removing the pts code, and > I still see the same panic with redzone enabled. Perhaps your initial > panic is the result of the pts code, but this memguard/redzone panic > is different, and may not be related. I was doing a binary search for the offending commit when the last panic took out parts of my /usr/include and /usr/src. This led to a fun dance with __format_arg. > My original question still stands: Does redzone work in combination > with INVARIANTS on other platforms? Amd64 is the only -current > platform I'm running... Sorry, I missed your original question. I too have INVARIANTS in my amd64 kernel. -- Steve _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
