Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Grant Coady
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi <[EMAIL PROTECTED]> wrote: @@ -31,7 +31,7 @@ #define APC_BPORT_REG 0x30 #define APC_REGMASK0x01 -define APC_BPMASK 0x03 +#define APC_BPMASK 0x03 Color me skeptical. I've seen some weird bit flips and

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Roger Luethi
> @@ -31,7 +31,7 @@ > #define APC_BPORT_REG 0x30 > > #define APC_REGMASK0x01 > -define APC_BPMASK 0x03 > +#define APC_BPMASK 0x03 Color me skeptical. I've seen some weird bit flips and data corruption; "paramters" to "paramEters" I could buy. But data

Resolved?: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Grant Coady
On Fri, 12 Aug 2005 09:43:31 +1000, Grant Coady <[EMAIL PROTECTED]> wrote: Hi there, Problem was dataloss on extracting kernel source, sometimes only one character changed. Details on http://bugsplatter.mine.nu/test/boxen/sempro/ Not the NIC, not reiserfs, not the kernel config, not even

Resolved?: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Grant Coady
On Fri, 12 Aug 2005 09:43:31 +1000, Grant Coady [EMAIL PROTECTED] wrote: Hi there, Problem was dataloss on extracting kernel source, sometimes only one character changed. Details on http://bugsplatter.mine.nu/test/boxen/sempro/ Not the NIC, not reiserfs, not the kernel config, not even

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Roger Luethi
@@ -31,7 +31,7 @@ #define APC_BPORT_REG 0x30 #define APC_REGMASK0x01 -define APC_BPMASK 0x03 +#define APC_BPMASK 0x03 Color me skeptical. I've seen some weird bit flips and data corruption; paramters to paramEters I could buy. But data corruption

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-14 Thread Grant Coady
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi [EMAIL PROTECTED] wrote: @@ -31,7 +31,7 @@ #define APC_BPORT_REG 0x30 #define APC_REGMASK0x01 -define APC_BPMASK 0x03 +#define APC_BPMASK 0x03 Color me skeptical. I've seen some weird bit flips and data

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Grant Coady
On Sat, 13 Aug 2005 00:21:30 +1000, Masoud Sharbiani <[EMAIL PROTECTED]> wrote: Can you turn on UDP checksums and try again? That would isolate the fault between the network or SATA. It is the second tarball extraction from cache that suffers data corruption, not a network error. I am in

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Masoud Sharbiani
Can you turn on UDP checksums and try again? That would isolate the fault between the network or SATA. cheers, Masoud Grant Coady wrote: On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <[EMAIL PROTECTED]> wrote: How to test and isolate this error is in NIC driver, SATA driver or

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Grant Coady
On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <[EMAIL PROTECTED]> wrote: >> How to test and isolate this error is in NIC driver, SATA driver or >> filesystem? >> > >Could it be that tarbal on NFS server changed? >It is not very likely that error in kernel drivers fixed typos in

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Vladimir V. Saveliev
Hello Grant Coady wrote: Greetings, Situation is dataloss with no errors logged. Test: unpack 2.6.12 tarball from NFS mount source, diff against previous attempt: $ diff -Nrup linux-2.6.12.old linux-2.6.12 Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Vladimir V. Saveliev
Hello Grant Coady wrote: Greetings, Situation is dataloss with no errors logged. Test: unpack 2.6.12 tarball from NFS mount source, diff against previous attempt: $ diff -Nrup linux-2.6.12.old linux-2.6.12 Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Grant Coady
On Fri, 12 Aug 2005 14:43:42 +0400, Vladimir V. Saveliev [EMAIL PROTECTED] wrote: How to test and isolate this error is in NIC driver, SATA driver or filesystem? Could it be that tarbal on NFS server changed? It is not very likely that error in kernel drivers fixed typos in source code.

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Masoud Sharbiani
Can you turn on UDP checksums and try again? That would isolate the fault between the network or SATA. cheers, Masoud Grant Coady wrote: On Fri, 12 Aug 2005 14:43:42 +0400, Vladimir V. Saveliev [EMAIL PROTECTED] wrote: How to test and isolate this error is in NIC driver, SATA driver or

Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-12 Thread Grant Coady
On Sat, 13 Aug 2005 00:21:30 +1000, Masoud Sharbiani [EMAIL PROTECTED] wrote: Can you turn on UDP checksums and try again? That would isolate the fault between the network or SATA. It is the second tarball extraction from cache that suffers data corruption, not a network error. I am in

Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-11 Thread Grant Coady
Greetings, Situation is dataloss with no errors logged. Test: unpack 2.6.12 tarball from NFS mount source, diff against previous attempt: $ diff -Nrup linux-2.6.12.old linux-2.6.12 Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and linux-2.6.12/include/asm-sparc/a.out.h differ diff

Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??

2005-08-11 Thread Grant Coady
Greetings, Situation is dataloss with no errors logged. Test: unpack 2.6.12 tarball from NFS mount source, diff against previous attempt: $ diff -Nrup linux-2.6.12.old linux-2.6.12 Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and linux-2.6.12/include/asm-sparc/a.out.h differ diff