From owner-freebsd-stable Mon Jul 17 21: 9:58 2000 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 0EC7037B61F for ; Mon, 17 Jul 2000 21:09:55 -0700 (PDT) (envelope-from swb@grasslake.net) Received: from k6 (k6.grasslake.net [192.168.2.1]) by accord.grasslake.net (8.9.3/8.9.3) with SMTP id XAA08092; Mon, 17 Jul 2000 23:10:40 -0500 (CDT) (envelope-from swb@grasslake.net) Message-ID: <000801bff06d$f8f7bcb0$0102a8c0@k6> From: "Shawn Barnhart" To: Cc: References: <200007180001.RAA17101@freeway.dcfinc.com> Subject: Re: Signal 11 on 4-Stable buildworld; bad memory or what? Date: Mon, 17 Jul 2000 23:09:24 -0500 Organization: Grasslake.Net MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Chad R. Larson" | You mean, no problems you've noticed. You may very well be right | about no problems, but please be aware that Windows will not | detect/report many errors that will trip up FreeBSD. Quiet data | corruption is the sometimes result. Well, I wasn't trying to impune the charater of FreeBSD, but this cpu/ram/mobo combo I pushed pretty hard under Win2k without EVER getting errors. I have 128MB of RAM in it and I often had over 300MB total VM in use. Machine was powered up 24 x 7 and seldom rebooted for ANY reason. If there's a memory glitch, I'm sure it was silent as I didn't get the problems I typically associate with low budget kit and Windows. I've swapped the CPU for an Intel P166 and had another buildworld die, so I don't think the K6 is to blame. I'm going to run memtest all night long and see if it can identify any problems. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message