From owner-freebsd-current  Thu Sep 12 17:19:37 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA14943
          for current-outgoing; Thu, 12 Sep 1996 17:19:37 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA14937;
          Thu, 12 Sep 1996 17:19:33 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id TAA06054; Thu, 12 Sep 1996 19:19:30 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199609130019.TAA06054@dyson.iquest.net>
Subject: Re: VM/kernel problems?
To: jhs@FreeBSD.org
Date: Thu, 12 Sep 1996 19:19:30 -0500 (EST)
Cc: sysseh@devetir.qld.gov.au, current@FreeBSD.org
In-Reply-To: <199609112156.XAA03514@vector.jhs.no_domain> from "Julian H. Stacey" at Sep 11, 96 11:56:16 pm
Reply-To: dyson@FreeBSD.org
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> 
> I managed to zap my 2 machines here with current of a couple of days back,
> I got lots of sig 11s & 6s, & some free/malloc complaints,
> then I broke new things while fixing other things.
> I'm rebuilding now with old current binaries, then doing a make with 2.1.5 src/
> then will crawl back to current of a week or so ago, or maybe back to 
> brand new current, once John D announces an OK.
> 
> Synopsis: I'll confirm: don't use current of a few days ago folks, it bites !
> 
Maybe I have made a mistake.  For a while, I had warned the -current
mailing list before making my "commit."  I will resume that procedure.
For those who haven't already guessed, the pmap code is notoriously
difficult to work on (at least for me), and as a warning -- PLEASE
be wary of my pmap commits :-)...  I know that it does not absolve my
sin, but this stuff needs to be done, and needs to be tested (and I try
my darnedest before commiting it, believe it or not, the code is even
worse when I first write it :-)).  Soon, I hope to have a dual p6, so
watch out SMP guys :-)...  It will also be a second machine to do more
complete testing on.

John