Date: Tue, 15 Aug 2006 17:04:24 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: John Baldwin <jhb@freebsd.org> Cc: amd64@freebsd.org Subject: Re: linux32 breakage in current.. Message-ID: <20060816000424.GA905@troutmask.apl.washington.edu> In-Reply-To: <20060815212415.GA1393@troutmask.apl.washington.edu> References: <200608151701.46724.jhb@freebsd.org> <20060815212415.GA1393@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 15, 2006 at 02:24:15PM -0700, Steve Kargl wrote: > On Tue, Aug 15, 2006 at 05:01:46PM -0400, John Baldwin wrote: > > So this went cold. IIRC, someone had tracked the linux32 breakage down to the > > linux_semctl() changes to use kern_semctl(), but then someone else noticed > > via printf that linux_semctl() is never called. So, can someone sit down and > > do a binary date exercise on -CURRENT to figure out when linux32 broke? > > > > It will take a few minutes. I know that linux32 works with 01 Aug 06 > sources and doesn't work with 11 Aug 06 sources. > Oh crap, this is more complicated than I thought With a kernel built from 2006.08.06.12.00.00 sources, I'm seeing the classic race condition for locking troutmask:kargl[201] acroread church.pdf Segmentation fault (core dumped) troutmask:kargl[202] acroread church.pdf <-- This one worked. troutmask:kargl[203] acroread church.pdf Segmentation fault (core dumped) troutmask:kargl[204] acroread church.pdf Segmentation fault (core dumped) troutmask:kargl[205] acroread church.pdf <-- This one worked. troutmask:kargl[206] I'll see if I can dig deeper. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060816000424.GA905>