Date: Wed, 30 Aug 2006 12:48:14 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: John Baldwin <jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: FINALLY! Re: linux32 breakage in current.. Message-ID: <20060830194814.GA32136@troutmask.apl.washington.edu> In-Reply-To: <200608301524.55149.jhb@freebsd.org> References: <200608151701.46724.jhb@freebsd.org> <200608301404.53834.jhb@freebsd.org> <20060830190944.GA2146@troutmask.apl.washington.edu> <200608301524.55149.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 30, 2006 at 03:24:54PM -0400, John Baldwin wrote: > > You have to use ktrace -i because bash forks children and the last one gets a > SIG11 from a child process that dies and kills the parent. Still, I've > stared at these before and been none the wiser. However, it doesn't make > _any_ sense that the cvsup changes you mentioned fix it and the patch > doesn't, because the patch does the _same_ thing. > The cvsup timestamps are 5 minutes apart for the good and bad kernels. If this is a memory alignment issue, then your patch would need to replicate the old alignment. That is, this is similar to the old Fortran issue that a simple debugging print statement can suddenly make code work because an array in memory has moved and stepping off the end of the array doesn't touch already used memory. I wonder if memguard might help. I'll go read up of this. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060830194814.GA32136>