From owner-freebsd-current Fri Apr 14 18:09:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA20489 for current-outgoing; Fri, 14 Apr 1995 18:09:21 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA20475 for ; Fri, 14 Apr 1995 18:09:17 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id SAA02129; Fri, 14 Apr 1995 18:06:32 -0700 From: "Rodney W. Grimes" Message-Id: <199504150106.SAA02129@gndrsh.aac.dev.com> Subject: Re: Interesting (and odd) effect in -current To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Fri, 14 Apr 1995 18:06:32 -0700 (PDT) Cc: cmf@ins.infonet.net, current@FreeBSD.org In-Reply-To: <199504150051.RAA18822@ref.tfs.com> from "Poul-Henning Kamp" at Apr 14, 95 05:51:13 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1321 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rod, > > Wouldn't it be a good idea in general if we zero all of the RAM in locore.s > (except the messagebuffer that is) ? > > That way we will have flushed all the caches, and reset all parity bits... IMHO, no, this should have already been done by the BIOS at power up time. Humm... I just came up with a fast and dirty way to find out if we are ever reading memory we have not written into (should never ever occur, right, as that would be using unitialized data). If it wasn't so chip set specific, you could actually turn parity off, use the special ports to write bad parity in all of memory. Then let things fly. But I have digressed, if the BIOS didn't manage to get this write at power on, you would get NMI interrupts no matter what OS you ran. I don't see a reason to add code to FreeBSD that really belongs in the BIOS in the off chance that some really rare broken motherboard could then work. If some one can prove to me that a production motherboard failed to initialize the parity bits correctly I will replace the motherboard for them, and be good riddens of one more piece of junk to have to try and support with redundant code. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD