Am Samstag, 13. August 2005 18:04 schrieb Grant Coady:
>
> I'm tracking a dataloss on box with this chip, finding it difficult
> to nail a configuration that reliably produces dataloss, sometimes
> only one bit (e.g. 'c' --> 'C') of unpacking kernel source tree gets
> changed.
>
> Relevant? This is on a KM400 with Skt A Sempron + Seagate SATA HDD.
> http://bugsplatter.mine.nu/test/linux-2.6/sempro/
Very unlikely. Rare bitwise errors like yours are more likely caused by
i.e. broken IDE cable or too fast an IDE-controller setting for the
cable / drive. Or memory error. Or an itch on the mainboard. or++
Interrupt errors would cause errors blockwisely.
like whole sectors of data missing, device not working....
Karsten
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden:
http://mail.yahoo.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
