From owner-freebsd-current  Thu Sep 12 07:40:02 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA08561
          for current-outgoing; Thu, 12 Sep 1996 07:40:02 -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 HAA08521;
          Thu, 12 Sep 1996 07:39:57 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA05323; Thu, 12 Sep 1996 09:39:55 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199609121439.JAA05323@dyson.iquest.net>
Subject: Re: continuing memory problems
To: dyson@freebsd.org
Date: Thu, 12 Sep 1996 09:39:54 -0500 (EST)
Cc: alk@think.com, current@freebsd.org
In-Reply-To: <199609121413.JAA05155@dyson.iquest.net> from "John S. Dyson" at Sep 12, 96 09:13:47 am
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 began experiencing signals 6, 11 and less frequently 10 in XF86_S3
> > about 4 days ago after a ctm update and kernel build.  I neglected the
> > issue as it was well reported, but now the traffic on this subject has
> > stopped, while (at cvs-cur.2458) I continue to experience (less
> > frequent) X server failures.
> > 
> > Two questions: Is the pmap problem believed to be resolved?  Is there
> > a recommended means of obtaining appropriate diagnostic information?
> > 
> I found the primary bug in pmap (I could reproduce it until last night.)
> The change was committed late last night (about 7-8 hrs ago.)  Give it
> a try again.
> 
Specifically, the fix is in pmap.c 1.118 (cvs-cur.2459).

John