Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Mar 1997 00:26:35 -0800
From:      David Greenman <dg@root.com>
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 
Message-ID:  <199703270826.AAA19418@root.com>
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> 

next in thread | previous in thread | raw e-mail | index | archive | help
>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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703270826.AAA19418>