From owner-freebsd-stable Sat Sep 25 9:47: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1B21014E32 for ; Sat, 25 Sep 1999 09:46:56 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA04974; Sun, 26 Sep 1999 01:46:50 +0900 (JST) Message-ID: <37ECF565.EA11AAAE@newsguy.com> Date: Sun, 26 Sep 1999 01:16:37 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Michael A. Endsley" Cc: thomas@hentschel.net, freebsd-stable@FreeBSD.ORG Subject: Re: Signal 11 on 3.3 installation References: <3.0.6.32.19990923220533.007ad910@mail.gci.net> <3.0.6.32.19990924085123.00896430@mail.gci.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michael A. Endsley" wrote: > > If this is so (bad ram), then why could I: > 1). Install FreeBSD 3.0 with no problems > 2). Install FreeBSD 3.2 with no problems > 3). Upgrade Debian Linux from Hamm to Slink with no problems > 4). Install OS/2 Warp4 (and fixpaks) with no problems? It happens. RAM will blow you up depending on it's usage pattern. It might work for years, and then a simple change in the usage pattern will come up with the defect. > Also, I just as I was getting ready to get it bed, I turned on another > computer (P166) and tried it. > Guess what? It caught the signal 11 at the exact same spot. Exact same spot? Then it is *NOT* a RAM problem. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org Rule 69: Do unto other's code as you'd have it do unto yours To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message