Is there any characterisation of the corrupted data; last time I
looked at the bz there wasn't.
I mean, is it reliably any of:
a) What's the size of the corruption?
block, cache line, word, bit???
b) Position?
e.g. last word in a block or something?
c) Data?
pile of zero's/ff's junk/etc?
d) Is it a missed write, old data, or partially written block?
Dave
Puh. I'm kinda lost on what we could do about this on the Linux
side.
Because it also depends on the CPU series, a firmware or hardware issue
seems to be more likely than a Linux bug.
ATM ASRock is still trying to reproduce the issue. (I'm in contact with
them to. But they have Chinese new year holidays in Taiwan this week.)
If they can't reproduce it, they have to provide an explanation why the
issues are seen by so many users.
Regards Stefan