mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul <krushka@iprimus.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Fwd: File system corruption
Date: Fri, 31 Jan 2003 22:12:11 +1000	[thread overview]
Message-ID: <03013122121103.01189@paul.home.com.au> (raw)
In-Reply-To: <20030108145503.F25712@bitwizard.nl>

I have finally received a new batch of CF cards (Mittoni brand) and these do 
not have the problem with data corruption as the Sandisk cards did.  So this 
fault is specific to one batch of Sandisk cards (so far)

Rogier has written below what might be causing this and I would like to try 
fixing it...gulp!  Can anyone spare a minute to point out the function I need 
to change to test the suggested "fix"?  I've looked around a bit and the 
closest I got was to finding an "outsl" function but can't find where the 
actual data is written to the device...

On Wed,  8 Jan 2003 11:55 pm, Rogier Wolff wrote:
> On Wed, Jan 08, 2003 at 02:15:06PM +0000, Alan Cox wrote:
> > On Wed, 2003-01-08 at 11:35, Paul wrote:
> > > What I have found is that just after the start of a sector, usually 43
> > > to 45 bytes, 6 bytes are skipped and the sequence starts again.  This
> > > continues until the next sector starts, where the sequence corrects. 
> > > This appears to happen every 65536 bytes or some multiple of 65536.  It
> > > may skip three blocks of 65536 and then corrupt on the next block of
> > > 65536 bytes.
> >
> > Ok that I'm afraid bears no resemblance to anything the software side
> > does (we write in chunks but we do single PIO block transfers of each
> > sector).
>
> After examining the resulting image, Paul has a "clock" line to his
> flash device that is a bit noisy. This occasionally causes one
> 16-bit entity to be clocked into the device twice.
>
> To detect this going wrong, we could (but only as a configurable
> option), write 255 16-bit words to the device (remember this is PIO!),
> check that DRQ is still active and only then write the last word.
> (at which point DRQ should go inactive).
>
> 				Roger.

  reply	other threads:[~2003-01-31 11:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 11:38 Paul
2003-01-06 15:06 ` Alan Cox
2003-01-06 14:31   ` Arjan van de Ven
2003-01-07 12:08   ` Rogier Wolff
2003-01-08 11:35     ` Paul
2003-01-08 14:15       ` Alan Cox
2003-01-08 13:55         ` Rogier Wolff
2003-01-31 12:12           ` Paul [this message]
2003-01-08 13:38     ` Paul

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=03013122121103.01189@paul.home.com.au \
    --to=krushka@iprimus.com.au \
    --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®