From owner-freebsd-current Fri Apr 14 18:28:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id SAA21098 for current-outgoing; Fri, 14 Apr 1995 18:28:32 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA21090 for ; Fri, 14 Apr 1995 18:28:30 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id SAA18903; Fri, 14 Apr 1995 18:28:22 -0700 From: Poul-Henning Kamp Message-Id: <199504150128.SAA18903@ref.tfs.com> Subject: Re: Interesting (and odd) effect in -current To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Fri, 14 Apr 1995 18:28:22 -0700 (PDT) Cc: cmf@ins.infonet.net, current@FreeBSD.org In-Reply-To: <199504150106.SAA02129@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Apr 14, 95 06:06:32 pm Content-Type: text Content-Length: 895 Sender: current-owner@FreeBSD.org Precedence: bulk > 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. I belive himem.sys clears memory to aviod that problem... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'