From owner-freebsd-current Mon Mar 27 12:35:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06731 for current-outgoing; Mon, 27 Mar 1995 12:35:46 -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 MAA06724 for ; Mon, 27 Mar 1995 12:35:41 -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 MAA01954; Mon, 27 Mar 1995 12:35:32 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id MAA00304; Mon, 27 Mar 1995 12:35:32 -0800 Message-Id: <199503272035.MAA00304@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de cc: smace@metal-mail.neosoft.com, mw@pandora.sax.de, current@freefall.cdrom.com Subject: Re: FreeBSD problems - VM bug? In-reply-to: Your message of "Mon, 27 Mar 95 12:42:07 +0200." <199503271042.MAA29588@bonnie.tcd-dresden.de> From: David Greenman Reply-To: davidg@Root.COM Date: Mon, 27 Mar 1995 12:35:23 -0800 Sender: current-owner@FreeBSD.org Precedence: bulk >As David Greenman wrote: >| >| >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. >... >| 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. > >But you realized that Martin's kernel is of 950221, David? (Only his >binaries are from the 950210-SNAP.) That doesn't matter. Most of the serious bugs were fixed in the last 2 weeks. -DG