From owner-freebsd-current  Thu Sep 12 00:57:29 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA20571
          for current-outgoing; Thu, 12 Sep 1996 00:57:29 -0700 (PDT)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA20565
          for <current@freebsd.org>; Thu, 12 Sep 1996 00:57:26 -0700 (PDT)
Received: from Early-Bird.Think.COM (Early-Bird-1.Think.COM [131.239.146.105])
    by mail.think.com (8.7.5/m3) with ESMTP id DAA19232
    for <current@freebsd.org>; Thu, 12 Sep 1996 03:57:24 -0400 (EDT)
Received: from compound.Think.COM (fergus-27.dialup.prtel.com [206.10.99.158])
    by Early-Bird.Think.COM (8.7.5/e1) with ESMTP id DAA13458
    for <current@freebsd.org>; Thu, 12 Sep 1996 03:57:14 -0400 (EDT)
Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id CAA00657; Thu, 12 Sep 1996 02:56:55 -0500 (CDT)
Date: Thu, 12 Sep 1996 02:56:55 -0500 (CDT)
From: Tony Kimball <alk@think.com>
Message-Id: <199609120756.CAA00657@compound.Think.COM>
To: current@freebsd.org
Subject: continuing memory problems
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?