From owner-freebsd-current  Thu Sep 12 07:15:11 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA07065
          for current-outgoing; Thu, 12 Sep 1996 07:15:11 -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 HAA07039
          for <current@freebsd.org>; Thu, 12 Sep 1996 07:15:06 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA05155; Thu, 12 Sep 1996 09:13:47 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199609121413.JAA05155@dyson.iquest.net>
Subject: Re: continuing memory problems
To: alk@think.com (Tony Kimball)
Date: Thu, 12 Sep 1996 09:13:47 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199609120756.CAA00657@compound.Think.COM> from "Tony Kimball" at Sep 12, 96 02:56:55 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.

John