lkml.org 
[lkml]   [1997]   [May]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] NMI trap revised (was Re: NMI errors in 2.0.30??)
Hi,

> I agree. It is certainly wrong to enable parity checks if non-parity memory is
> used. However, not enabling parity checks may also be wrong.

Well... if we enable it, we risk the machine will crash even if the RAM is OK.

And if we don't enable it, we risk only unreported parity errors.

> Maybe, it would be better to provide a method fo rextra hardware setup. How
> about something like the attached patch to setup.S. If you need it, you just
> turn it on; if you don't, nothing extra is generated.

I think of something else: I currently work on a generic chipset support
module which will have several options for turning on various features. I simply
can add an option forcing setting of the memory parity check logic.

Martin

\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.132 / U:1.264 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site