Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2001 15:10:24 +0100
From:      Wilko Bulte <wkb@freebie.xs4all.nl>
To:        Thiemo Nordenholz <nz@thiemo.net>
Cc:        Falko Meyer <wds_de@yahoo.de>, freebsd-alpha@FreeBSD.ORG
Subject:   Re: mprotect() takes quite long -- anyone knows this?
Message-ID:  <20011127151024.A3785@freebie.xs4all.nl>
In-Reply-To: <20011127123654.A56998@mygiea.ham01.thiemo.net>; from nz@thiemo.net on Tue, Nov 27, 2001 at 12:36:57PM %2B0100
References:  <3C03741A.55375021@yahoo.de> <20011127123654.A56998@mygiea.ham01.thiemo.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 27, 2001 at 12:36:57PM +0100, Thiemo Nordenholz wrote:

> > I think this can't be defective memory because this machine uses ECC-RAM
> > and you would see massive ECC-errors in this case.
> 
> Do you know what FreeBSD does when an ECC error is encountered? Does it log
> it? Does it just silently discard the information? Can the kernel know about
> ECC corrective actions at all? I have no clue of all that... Another
> information I'd be happy to get :-)

Kernels in general can know about ECC errors. Tru64 e.g. handles them.
So the hardware is there. I once had dodgy memory in a AS2100A which 
FreeBSD crashed on. But Tru64 and VMS ran on the same hardware OK.
This was a while ago, I'm not sure if there have been changes in
this area.

Wilko
-- 
|   / o / /_  _   		email: 	wilko@FreeBSD.org
|/|/ / / /(  (_)  Bulte		Arnhem, The Netherlands	

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011127151024.A3785>