Date: Tue, 20 Oct 1998 10:17:20 -0700 (PDT) From: Tom <tom@uniserve.com> To: Bart Lindsey <bart@burra.zip.com.au> Cc: bm@malepartus.de, freebsd-stable@FreeBSD.ORG Subject: Re: ECC memory support Message-ID: <Pine.BSF.4.02A.9810201014300.26709-100000@shell.uniserve.ca> In-Reply-To: <199810201305.XAA01587@burra.zip.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 20 Oct 1998, Bart Lindsey wrote: > Hi Burkard, > > ECC occurs between the memory modules and the motherboard. The kernel doesn't > get involved and the process is transparent to the kernel. The kernel is involved, as it will handle the NMI generated by the memory fault, and panic the system, which hopefully cleanly restart the system. Also, some systems can do more with the NMI, like shutdown whatever was contained in the bad location. FreeBSD doesn't do this. FreeBSD just calls panic. > The PC architecture doesn't handle memory problems very nicely and typically > the CPU resets without warning or just freezes without the kernel having any > opportunity to trap an error. Only on non-ECC or non-parity systems where the system will run through bad memory. > Depending on the revision of your motherboard, you might have to download > the bios patch described at URL: > > http://www.asus.com/downloads/bios/Jbios.asp?Motherboard=P/I-P55T2P4S#instructions > > There are two factors mentioned which can cause parity errors: > 1. PS2 mouse installed or > 2. AMD K6 installed and ECC/parity enabled. > > Good Luck! > > Bart. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02A.9810201014300.26709-100000>