From owner-freebsd-hackers Sat Sep 29 7:48: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r02.mx.aol.com (imo-r02.mx.aol.com [152.163.225.98]) by hub.freebsd.org (Postfix) with ESMTP id 2FF9237B40B for ; Sat, 29 Sep 2001 07:48:01 -0700 (PDT) Received: from Bsdguru@aol.com by imo-r02.mx.aol.com (mail_out_v31_r1.7.) id 3.f4.100fd30a (16781); Sat, 29 Sep 2001 10:47:54 -0400 (EDT) From: Bsdguru@aol.com Message-ID: Date: Sat, 29 Sep 2001 10:47:54 EDT Subject: Re: ecc on i386 To: ticso@mail.cicely.de Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 9/28/01 10:21:58 AM Eastern Daylight Time, ticso@mail.cicely.de writes: > > I dont think this is "good". Back in the XT days we used to get a false > > parity error every once on a while on an ISA card...taking the machine > down > > on a bit error (which XTs used to do) was completly wrong and unnecessary. > If > > Haeh - if your memory content has been changed behind you can only hope > that it doesn't trashed some important metadata and won't trash the > whole system. > Well it's much better if you check the use of the memory region and do > some inteligent handling. > But ignoring is definately a very dangerous thing. > Well if you didnt snip out the context you wouldnt have an argument at all, since I said to make it an option to shut down or issue a warning. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message