OK, I compiled 2.6.22 from kernel.org and the error still appears. I ran:
while (true) ; do md5sum bigfile.sql ; done
bigfile.sql is around 16GB, and I ran that loop for about an hour, and here's the results:
cb5714b4050178096ee5d7ebade86364 bigfile.sql f199dc20003be8f5913d38d92d0b99e3 bigfile.sql cb5714b4050178096ee5d7ebade86364 bigfile.sql aae3ef4d02ecbe21827d3d96f2179681 bigfile.sql 6edfeafe8a73ee07c075164dc93b319e bigfile.sql 55743d67dded508cacfb5abc0af016e5 bigfile.sql 889c5e708c1c884ea4efd11bdd1ff2c6 bigfile.sql
Any suggestions on how to determine whether this is actually a bug and not faulty hardware? This machine ran memtest for almost a week with no errors!
OK, I compiled 2.6.22 from kernel.org and the error still appears. I ran:
while (true) ; do md5sum bigfile.sql ; done
bigfile.sql is around 16GB, and I ran that loop for about an hour, and here's the results:
cb5714b40501780 96ee5d7ebade863 64 bigfile.sql 5913d38d92d0b99 e3 bigfile.sql 96ee5d7ebade863 64 bigfile.sql 1827d3d96f21796 81 bigfile.sql 7c075164dc93b31 9e bigfile.sql cacfb5abc0af016 e5 bigfile.sql ea4efd11bdd1ff2 c6 bigfile.sql
f199dc20003be8f
cb5714b40501780
aae3ef4d02ecbe2
6edfeafe8a73ee0
55743d67dded508
889c5e708c1c884
Any suggestions on how to determine whether this is actually a bug and not faulty hardware? This machine ran memtest for almost a week with no errors!