Date: Wed, 1 Feb 2006 11:44:27 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_malloc.c src/share/man/man9 Makefile redzone.9 src/sys/vm redzone.c redzone.h src/sys/conf NOTES files options Message-ID: <17376.58731.618704.264566@grasshopper.cs.duke.edu> In-Reply-To: <20060201160923.GA67621@troutmask.apl.washington.edu> References: <200601311109.k0VB9MRq025366@repoman.freebsd.org> <20060201104752.A68774@grasshopper.cs.duke.edu> <20060201160923.GA67621@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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. My original question still stands: Does redzone work in combination with INVARIANTS on other platforms? Amd64 is the only -current platform I'm running... Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17376.58731.618704.264566>