From owner-freebsd-current  Tue Sep 10 08:13:45 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA21572
          for current-outgoing; Tue, 10 Sep 1996 08:13:45 -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 IAA21562
          for <current@freebsd.org>; Tue, 10 Sep 1996 08:13:40 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id KAA00535; Tue, 10 Sep 1996 10:13:15 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199609101513.KAA00535@dyson.iquest.net>
Subject: Re: VM/kernel problems?
To: peter@spinner.DIALix.COM (Peter Wemm)
Date: Tue, 10 Sep 1996 10:13:14 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199609101427.WAA08070@spinner.DIALix.COM> from "Peter Wemm" at Sep 10, 96 10:27:52 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

> 
> Is this just me?  I started getting these on three different machines with 
> a
> vanilla -current kernel from within the last 24 hours.
> 
> pid 659 (FvwmPager), uid 433: exited on signal 11 (core dumped)            
>     
> pid 762 (xterm), uid 0: exited on signal 11                                
>     
> pid 144 (named), uid 0: exited on signal 11 (core dumped)                  
>     
> pid 4601 (tcsh), uid 0: exited on signal 10 (core dumped)                  
>     
> 
> The machines were not under any load at the time (load-av 0.00).
> 
> A build that is failing:
> @(#)FreeBSD 2.2-CURRENT #0: Mon Sep  9 20:36:30 WST 1996
> 
> A build that is thought to be good:
> @(#)FreeBSD 2.2-CURRENT #0: Fri Sep  6 03:40:12 WST 1996
> I do not know that this one was built from up-to-date source though.
> 
> (WST = 8 hours ahead of GMT, about 15 hours ahead of freefall time)
> 
> Anybody else seen this, or is it something local?
> 
Please, if anyone is seeing such a problem with -current, pipe-up!!!  The
new pmap changes look simple, but their ramifications can be complex,
and the simplest error is difficult to track down.  I am prepared to work
all of tonight on the problem (and I think that I have a few ideas for
potential problems.)

Thanks!!!
John