Date: Thu, 8 Jan 2004 18:40:14 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD Crashes with AMD Message-ID: <20040108074014.GJ25474@server.vk2pj.dyndns.org> In-Reply-To: <200401081409.10503.doconnor@gsoft.com.au> References: <200401071731.40481.doconnor@gsoft.com.au> <200401081058.26112.doconnor@gsoft.com.au> <3FFCCC5B.3010001@mindcore.net> <200401081409.10503.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 08, 2004 at 02:09:10PM +1030, Daniel O'Connor wrote: >> I don't recall offhand if their BIOS currently posts ECC vs non ECC as >> part of their POST or not, but the presumed support is in there, or >> their docs and specs are completely wrong ;-) > >Heh :) >That's the thing about ECC, it's hard to test unless you have a known faulty >memory module lying around :( If you have a spare known-good ECC DIMM, you can convert it to a known- faulty DIMM by cutting a single I/O lead on one of the RAM chips. If you pick a chip where you can read the part number, you should be able to download a datasheet (including pinouts) from the chip manufacturer. You might also be able to cut an I/O track on the DIMM itself. Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040108074014.GJ25474>