From owner-freebsd-current Sun Mar 26 14:22:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA03361 for current-outgoing; Sun, 26 Mar 1995 14:22:42 -0800 Received: from pluto.ops.NeoSoft.com (root@pluto.ops.NeoSoft.COM [198.64.212.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA03355 for ; Sun, 26 Mar 1995 14:22:40 -0800 Received: from metal.ops.neosoft.com (root@glenn-slip45.nmt.edu [129.138.5.145]) by pluto.ops.NeoSoft.com (8.6.10/8.6.10) with ESMTP id QAA23326; Sun, 26 Mar 1995 16:22:28 -0600 Received: (from smace@localhost) by metal.ops.neosoft.com (8.6.11/8.6.10) id PAA04563; Sun, 26 Mar 1995 15:22:24 -0700 From: Scott Mace Message-Id: <199503262222.PAA04563@metal.ops.neosoft.com> Subject: Re: FreeBSD problems - VM bug? To: mw@pandora.sax.de Date: Sun, 26 Mar 1995 15:22:24 -0700 (MST) Cc: current@freefall.cdrom.com In-Reply-To: <199503261913.VAA20131@sax.sax.de> from "Martin Welk" at Mar 26, 95 09:13:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1542 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. Scott > > Now I've installed FreeBSD-950210-SNAP and a newer kernel release > (dated on March, 23th) - Joerg was so friendly to build a new kernel > at his machine for me, because... > > - Building a new kernel didn't work. Using the old kernel I got a > "cc1: got fatal signal 11" message while running ``make depend'' at > /usr/src/sys/compile/THEATRE. > With the newer kernel this works fine but when compiling the kernel > I get: ../../kern/subr_prf.c: In function '*' > (where * has to be replaced by panic, uprintf, tprintf, ttyprintf, > log, addlog, printf, sprintf) > too many arguments to function `__builtin_next_arg' > > - I cannot use ``man'' - it says: > groff: troff: Resource deadlock avoided > > - So I decided to try to compile groff/troff and so on and went to > /usr/src/gnu/usr.bin/ngroff and said ``make'' - when compiling troff > it says: ``cc: Internal compiler error: program cpp got fatal signal > 11'' and exits.