From owner-freebsd-security Wed Mar 28 6:40: 1 2001 Delivered-To: freebsd-security@freebsd.org Received: from bilver.wjv.com (dhcp-1-39.n01.orldfl01.us.ra.verio.net [157.238.210.39]) by hub.freebsd.org (Postfix) with ESMTP id 487C737B71B for ; Wed, 28 Mar 2001 06:39:57 -0800 (PST) (envelope-from bill@bilver.wjv.com) Received: (from bill@localhost) by bilver.wjv.com (8.11.1/8.11.1) id f2SEdtj11175 for freebsd-security@FreeBSD.ORG; Wed, 28 Mar 2001 09:39:55 -0500 (EST) (envelope-from bill) Date: Wed, 28 Mar 2001 09:39:54 -0500 From: Bill Vermillion To: freebsd-security@FreeBSD.ORG Subject: Re: weird daily check output Message-ID: <20010328093954.D10350@wjv.com> Reply-To: bv@wjv.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from owner-freebsd-security-digest@FreeBSD.ORG on Wed, Mar 28, 2001 at 02:56:01AM -0800 Organization: W.J.Vermillion / Orlando - Winter Park Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Date: Tue, 27 Mar 2001 16:34:24 -0500 > From: "Jonathan M. Slivko" > Subject: Re: weird daily check output > Actually, what I was refferring to was the portion when FreeBSD > actually first started, and gave the copyright info, etc. It said: > FrEeBSD, or something like that. I just thought that it was odd :P Well 'something like that' is not quite exact enough :-). If the first E was capitalized the second should have been also. I've seen this one time a long time ago. I traced it through a core dump and found there was a pattern. After bringing up man ASCII I discovered that the ones in the wrong case were either all odd or even, forget which, and I determined it was the first bit in the memory that was stuck high. So could have a bit stuck low or high. It was on a 3MB add in memory board - that's how long ago it was - and because of the bit position it had to a 'corner chip' in one of any of the 32 bit blocks of chips [96 chips to make up 3MB]. And there, nestled among the 256K chips was a lonely 64K chip. All the standard boot memory diagnostics passed it. You need to run a memory check program that performs a walking-bit test, or checkerboard tests, adjacent bit tests, etc. -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message