All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: krushka@iprimus.com.au,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: File system corruption
Date: Wed, 8 Jan 2003 14:55:03 +0100	[thread overview]
Message-ID: <20030108145503.F25712@bitwizard.nl> (raw)
In-Reply-To: <1042035305.24099.13.camel@irongate.swansea.linux.org.uk>

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. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currently in such an      * 
* excursion: The stable situation does not include humans. ***************

  reply	other threads:[~2003-01-08 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 11:38 Fwd: File system corruption 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 [this message]
2003-01-31 12:12           ` Paul
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=20030108145503.F25712@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.