All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ian Eure <Ian Eure" <ieure@insynq.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: <mtd@infradead.org>
Subject: Re: doc2k: "formatting block"?
Date: Wed, 7 Feb 2001 09:20:45 -0800 (PST)	[thread overview]
Message-ID: <14977.33773.1956.20539@pyramid.insynq.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102061909140.2237-100000@imladris.demon.co.uk>

David Woodhouse writes:
 > On Tue, 6 Feb 2001, Ian Eure <Ian Eure wrote:
 > 
 > > while testing a 32mb doc2000, i see these messages:
 > > 
 > > -- snip --
 > > DiskOnChip 2000 found at address 0xD0000
 > > Flash chip found: Manufacturer ID: 98, Chip ID: 73 (Toshiba TH58V128DC)
 > > 2 flash chips found. Total DiskOnChip size: 32 Mb
 > > Block 807: referencing block 110 already in another chain
 > > Formatting chain at block 807
 > > Formatting block 807
 > > Unreferenced block 366, formatting it
 > > -- snip --
 > 
 > Eep. Can you reproduce it? Did this happen after the M-Systems drivers (or 
 > firmware) had been writing to the device, or is it purely our software? 
 > It's unlikely to be hardware.
 > 
it's reproducible, but only with this one 32mb doc2000. i only have
this chip, and a 48mb doc2000 for testing right now.

the doc had been written to by the m-sys driver before.

 > I'm trying to grok that code - even if the block _is_ linked in another 
 > chain, we should be able to work out which chain it _ought_ to be in by 
 > its own VirtUnitNum entry. We still have to format the chain in which the 
 > block _isn't_ supposed to be, and there's definitely some data corruption 
 > happened, but we should be able to do a little better than we do ATM, I 
 > think.
 > 
 > I don't see how this could be caused by a fold in progress - we don't fold 
 > one chain into _another_, only into itself. But the comment implies 
 > otherwise...
 > 
 > 	printk("Block %d: referencing block %d already in another chain\n", 
 > 		block, rep_block);
 > 	/* XXX: should handle correctly fold in progress chains */
 > 	do_format_chain = 1;
 > 	s->ReplUnitTable[block] = BLOCK_NIL;
 > 
i'm an intermediate c programmer, and have no experience with kernel
programming. but, i'd like to try and help you, so i'm just gonna jump
in. some patches may (or may not) fly out in a few days or weeks. :)

-- 
 ___________________________________
| Ian Eure - <ieure@insynq.com>     | "You're living in a facist world...
|         -  Developer -            | Freedom is a luxury." -Front Line
|        -  InsynQ, Inc. -          | Assembly, "Digital Tension Dementia"
| Your Internet Utility Company.tm  |________________________________________


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-02-07 17:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 18:11 doc2k: "formatting block"? Ian Eure <Ian Eure
2001-02-06 19:28 ` David Woodhouse
2001-02-07 17:20   ` Ian Eure <Ian Eure [this message]
2001-02-07 17:27     ` David Woodhouse
2001-02-07 17:44       ` Ian Eure <Ian Eure

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=14977.33773.1956.20539@pyramid.insynq.com \
    --to=ieure@insynq.com \
    --cc=dwmw2@infradead.org \
    --cc=mtd@infradead.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.