mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karsten Wiese <annabellesgarden@yahoo.de>
To: Grant Coady <Grant.Coady@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH,RFC] quirks for VIA VT8237 southbridge
Date: Sat, 13 Aug 2005 18:34:16 +0200	[thread overview]
Message-ID: <200508131834.16629.annabellesgarden@yahoo.de> (raw)
In-Reply-To: <d86sf15b5b36ta7rgkjo2p980fku9e0lce@4ax.com>

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

  reply	other threads:[~2005-08-13 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-13 15:10 Karsten Wiese
2005-08-13 16:04 ` Grant Coady
2005-08-13 16:34   ` Karsten Wiese [this message]
2005-08-13 16:41   ` Jeff Garzik
2005-08-13 21:06     ` Grant Coady
2005-08-15 22:31 ` Bjorn Helgaas
2005-08-16 15:26   ` Karsten Wiese
2005-08-16 15:49     ` Bjorn Helgaas
2005-08-16 17:20       ` Alan Cox
2005-08-18 12:36         ` Karsten Wiese
2005-08-18 13:57           ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200508131834.16629.annabellesgarden@yahoo.de \
    --to=annabellesgarden@yahoo.de \
    --cc=Grant.Coady@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®