From owner-freebsd-current Fri Apr 14 19:03:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21820 for current-outgoing; Fri, 14 Apr 1995 19:03:12 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA21810 for ; Fri, 14 Apr 1995 19:03:03 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id TAA18250; Fri, 14 Apr 1995 19:02:58 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA00566; Fri, 14 Apr 1995 19:02:57 -0700 Message-Id: <199504150202.TAA00566@corbin.Root.COM> To: Poul-Henning Kamp cc: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes), cmf@ins.infonet.net, current@FreeBSD.org Subject: Re: Interesting (and odd) effect in -current In-reply-to: Your message of "Fri, 14 Apr 95 17:51:13 PDT." <199504150051.RAA18822@ref.tfs.com> From: David Greenman Reply-To: davidg@Root.COM Date: Fri, 14 Apr 1995 19:02:55 -0700 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... We don't need to do this in locore; we can do it in the same place where the old memory test was (which is before the VM system is turned on, etc.). I considered doing this when I removed the memory test code, but then changed my mind and decided that I wanted to know about problems with uninitialized memory. Perhaps when options DIAGNOSTIC is true, we fill memory with 0xdeadbeef and when not true, we fill with 0. ...or just fill with 0xdeadbeef all the time - I don't care. -DG