From owner-freebsd-doc Tue Sep 19 15: 1:27 2000 Delivered-To: freebsd-doc@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 0E12C37B423; Tue, 19 Sep 2000 15:01:26 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id e8JM1LG30737; Tue, 19 Sep 2000 15:01:21 -0700 Date: Tue, 19 Sep 2000 15:01:21 -0700 From: Brooks Davis To: Jeff Gibbons Cc: Nik Clayton , Steve Roome , freebsd-doc@FreeBSD.ORG, James Housley , Mark Ovens Subject: Re: signal 11 faq entry Message-ID: <20000919150121.A30358@Odin.AC.HMC.Edu> References: <20000919165723.D8111@moose.bri.hp.com> <20000919185552.B12114@canyon.nothing-going-on.org> <20000919145149.B32023@nike.relcast.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000919145149.B32023@nike.relcast.com>; from jgibbons@protogate.com on Tue, Sep 19, 2000 at 02:51:49PM -0700 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Sep 19, 2000 at 02:51:49PM -0700, Jeff Gibbons wrote: > Here's another possible for Nik's list of "common causes": Hmm, maybe what we really need is a question on this sort of thing that the signal 11 FAQ can refrence. Programs throwing signal 11 isn't the only symptom of flakey hardware. I'm got a system that locks solid periodicaly if you install memory in one of the slots (which is bad because there are only two of them). -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message