From owner-freebsd-current Thu Sep 21 22:07:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA15348 for current-outgoing; Thu, 21 Sep 1995 22:07:51 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA15343 for ; Thu, 21 Sep 1995 22:07:47 -0700 Received: from corbin.Root.COM (corbin [198.145.90.34]) by Root.COM (8.6.12/8.6.5) with ESMTP id WAA01210; Thu, 21 Sep 1995 22:06:29 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id WAA00368; Thu, 21 Sep 1995 22:08:55 -0700 Message-Id: <199509220508.WAA00368@corbin.Root.COM> To: asami@cs.berkeley.edu (Satoshi Asami) cc: current@freebsd.org Subject: Re: sig 10/11 problems In-reply-to: Your message of "Thu, 21 Sep 95 20:11:03 PDT." <199509220311.UAA00641@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 21 Sep 1995 22:08:55 -0700 Sender: owner-current@freebsd.org Precedence: bulk > * I just committed to CVS a work-around for the sig 10/11 problems that > * people have been having for the past 3 weeks. It should be available to SUP > * in about 4 hours (9pm PDT). > >I grabbed it off the cvs tree and recompiled the -current kernel but >the symptoms (sig 10/11 for X programs) are still the same for >me.... ;< Is the problem you're having with specific binaries, and does it always fail? I think you might have a corrupt binary and/or shared library. Except for a shell bug reported by Stephen Hocking, all of the reports I've gotten back have indicated that the patch has gotten rid off all of the sig 10/11 flakiness they were experiancing. Also, can you verify that the revision you're using of ffs_vnops.c is indeed 1.13, please? ...oh, and there were other bugs that have been fixed recently, I assume that you're running -current from within the past day or so? -DG