lkml.org 
[lkml]   [2008]   [Aug]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: amd64 sata_nv (massive) memory corruption
Linas Vepstas wrote:
> 2008/8/3 Robert Hancock <hancockr@shaw.ca>:
>> Linas Vepstas wrote:
>>> What I don't like is that the corruption was utterly silent --
> [...]
>>> So the question is: is there some sort of sata (or pci) "loopback mode",
>>> where we could pump data through all of the busses and controllers, up
>>> near to the point where it would normally go out to the serdes to the
>>> disk,
>>> but instead have it loop back, so that we could test the buses between
>>> endpoints?
>> I don't imagine that would be very useful in this case. The SATA link, PCI
>> Express bus, HyperTransport bus all have parity or CRC error checking, so
>> presumably they couldn't be likely to cause undetected errors. The
>> transitions between them could cause problems,
>
> Well, but I suffered badly from an undetected error, in the sense
> that the operating system had no knowledge of it, and it corrupted
> data on disk as a result. As Alan Cox suggests, perhaps I didn't
> have EDAC turned on, or something ... I'm investigating now.
> But this is moot -- if there is software that already exists that
> could have reported the error to the kernel, then this software
> should have been installed/enabled/operating by default.

EDAC is mainly useful for detecting non-fatal problems (i.e. things like
corrupted transfers that were detected and retried, or ECC errors that
could be corrected) which might indicate a problem but might go
unnoticed otherwise. Usually, fatal problems that get detected by
hardware wouldn't be unnoticeable - they would typically raise NMIs and
cause funny kernel messages, cause machine check exceptions or just lock
up or reset the machine.

Of course, if you don't have ECC memory, and you have bad RAM or memory
timing problems, nothing can detect this at all, and EDAC wouldn't help you.

>
>> and most desktop machines
>> don't have ECC memory which could catch memory timing problems or bad RAM
>
> I'm unclear on ECC memory: if a motherboard "supports ECC",
> does it mean it actually uses ECC bits in the bus between the
> memory controller and the RAM? Or does it simply mean that
> it won't hang if I plug in ECC RAM (but otherwise ignore the bits)?

I think just about all chipsets (more specifically, memory controllers,
this includes AMD CPUs) support ECC and use the bits, at least if all
the installed memory supports it. I've never heard of a board that
couldn't handle ECC at all.

>
> Personally I'm ready to pop $$$ for ECC it if will actually do
> something for me, this has been painful.
>
> --linas
>


\
 
 \ /
  Last update: 2008-08-05 08:39    [from the cache]
©2003-2011 Jasper Spaans