From owner-freebsd-current  Thu Mar 27 00:27:00 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id AAA12548
          for current-outgoing; Thu, 27 Mar 1997 00:27:00 -0800 (PST)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA12536
          for <freebsd-current@freebsd.org>; Thu, 27 Mar 1997 00:26:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id AAA19418; Thu, 27 Mar 1997 00:26:35 -0800 (PST)
Message-Id: <199703270826.AAA19418@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Doug Russell <drussell@saturn-tech.com>
cc: Terry Lambert <terry@lambert.org>,
        David Dawes <dawes@rf900.physics.usyd.edu.au>,
        joerg_wunsch@uriah.heep.sax.de, freebsd-current@freebsd.org
Subject: Re: SIGABRTs killing X 
In-reply-to: Your message of "Wed, 26 Mar 1997 22:08:10 GMT."
             <Pine.BSF.3.95.970326195722.1233A-100000@586quick166.saturn-tech.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 27 Mar 1997 00:26:35 -0800
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>previous 3C509TP.  The last change before that was to put in 4x 8 meg EDO
>45ns SIMMs so I could turn up the memory speed knobbies in the CMOS to
>full blast.

   Ah. Try setting the memory speed one notch slower than full blast. This
appears to be a memory timing problem (or just bad RAM?). The most common
case of the X server getting a SIGABRT is via another unexpected signal
(usually SIGSEGV, SIGBUS, or SIGILL) - the server calls abort() in this
case which then sends itself a signal in order to cause the system to
generate a core file.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project