> Just to add some x86/netbsd relevance here, I wonder if an
> parity/uncorrectable ECC error in netbsd souldn't be handled a bit
> more like a SEGV if it occurs in user pages.  If we have a 64Meg
> machine and the kernel only uses all of 4 megs or so, we will have a
> much higher probability of memory corrupting a user page than any
> kernel page.  Panicing the kernel is probably an over-reaction.  I
> recall Sunos (4.1 ???) had a layered approach that was kind of clever.
> What I recall of it:
> 
> 	user write-protected text pages - refetch from disk
> 	User data pages - kill program
> 	Kernel pages - panic

Yes, this is the way it _should_ be done.   Ultrix does it this way
too...

			       _MelloN_