From owner-freebsd-current Sun Mar 26 14:38:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA06292 for current-outgoing; Sun, 26 Mar 1995 14:38:01 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA06284 for ; Sun, 26 Mar 1995 14:37:57 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id OAA05928; Sun, 26 Mar 1995 14:37:45 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id OAA00314; Sun, 26 Mar 1995 14:37:45 -0800 Message-Id: <199503262237.OAA00314@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Scott Mace cc: mw@pandora.sax.de, current@freefall.cdrom.com Subject: Re: FreeBSD problems - VM bug? In-reply-to: Your message of "Sun, 26 Mar 95 15:22:24 MST." <199503262222.PAA04563@metal.ops.neosoft.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 26 Mar 1995 14:37:43 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >I experienced the random singal 11's back then when my -current was about >equal to the SNAP. I no longer get those problems with the latest -current. >The problem seemed to hinge around -O2 optimization instead of -O. > >The solution for me was to recompile the world with -O instead of -O2. >I think the best solution for anyone running the 02 SNAP is that they >should upgrade to the latest SNAP (its a pain but probably more feasable >than recompiling everything). > >Like I said, -O2 does not seem to cause these problems anymore. I havn't >seen a singal 11 for quite some time. I don't think the problem is in any way related to -O2 optimization. There were a whole slew of VM bugs that were fixed in post-0210 SNAP that were causing problems. As far as I know, the entire source tree except the kernel is still built -O2. -DG