From owner-freebsd-current Wed Sep 18 01:11:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26286 for current-outgoing; Wed, 18 Sep 1996 01:11:29 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA26251 for ; Wed, 18 Sep 1996 01:11:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA11564; Wed, 18 Sep 1996 01:11:42 -0700 (PDT) Message-Id: <199609180811.BAA11564@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: current@FreeBSD.org Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 17:15:02 +0930." <199609180745.RAA04741@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 01:11:42 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Hmm. I've been trying to build the world on this (other) machine for days >now, and have been plagued with no end of problems. I am _not_ convinced >that the machine is 100% hardware reliable. Although earlier this year >(march-april) it was worlding every couple of weeks OK, it has (I believe) >had a memory swap since then. (P120, Soyo Triton, NCR & 2G seagate). > >Initially the build was failing _consistently_ when compiling >libncurses/lib_options -> lib_options.so; the machine would >spontaneously reboot. I've been supping as close as I could, watching for >changes filtering through from JD; the kernel it's currently running's >/sys/vm Id strings are at the bottom of this message. Are you sure that you're not using some old LKMs? This is definately filesystem related and appears to be caused by a 'sync' to a out of date loadable kernel module. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project