lkml.org 
[lkml]   [2005]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??
Date
From
On Sun, 14 Aug 2005 22:12:55 +1000, Roger Luethi <rl@hellgate.ch> wrote:

>> @@ -31,7 +31,7 @@
>> #define APC_BPORT_REG 0x30
>>
>> #define APC_REGMASK 0x01
>> -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 that
> _inserts_ a hash mark a the beginning of a line of a header file? What
> are the odds?

A bitflip in the compressed image could expand the wrong token
resulting in dataloss just as easily as flip character case.

Since reporting this error I've eliminated filesystem and NIC
by substitution, fault occurs on ext2 and Intel pro/100.
>
>> Today disabled onboard via-rhine and used Intel pro/100 + e100 driver,
>> several source trees unpacked identically, running 2.6.12.4 or 2.4.31-hf3
>
> While that seems to point to the Rhine as the possible cause, I can't
> see how any driver could possibly be involved in this.

Neither can I, now testing outside of linux, eliminate OS as factor,
or, is it hardware or software? I dunno...

Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-08-14 22:15    [W:0.821 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site