From owner-freebsd-current  Sun Jul 28 13:37:20 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA09166
          for current-outgoing; Sun, 28 Jul 1996 13:37:20 -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 NAA09159
          for <freebsd-current@FreeBSD.org>; Sun, 28 Jul 1996 13:37:12 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id PAA00164; Sun, 28 Jul 1996 15:36:42 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199607282036.PAA00164@dyson.iquest.net>
Subject: Re: New wierdness since latest VM kernel.
To: peter@spinner.DIALix.COM (Peter Wemm)
Date: Sun, 28 Jul 1996 15:36:42 -0500 (EST)
Cc: freebsd-current@FreeBSD.org
In-Reply-To: <4tgh9j$os4$1@haywire.DIALix.COM> from "Peter Wemm" at Jul 28, 96 08:07:15 pm
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

> 
> Ouch, I saw this too, except "#! /bin/sh" was being ignored and tcsh was
> trying to start the bourne shell script under $SHELL (tcsh)
> 
> It seems to be still happening right now.. :-(
> 
It is possible that the pmap.c commit that I just made (1.111) might
fix the problem.  pmap_update was not occuring properly all of the time for
kernel_pmap.  It could cause sporadic problems.

John