From: Sarah Diesburg <diesburg@cs.fsu.edu>
To: linux-mtd@lists.infradead.org
Subject: Re: inftl and diskonchip 2000 256MB
Date: Mon, 23 Jun 2008 17:35:59 -0400 [thread overview]
Message-ID: <4860173F.4040304@cs.fsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.62.0806201305110.20473@diablo.cs.fsu.edu>
Sarah Diesburg wrote:
> output of "modprobe inftl" (starts with block 10, goes all the way to
> block 11166)
> ...
> INFTL: formatting chain at block 7435
> INFTL: formatting block 7435
> INFTL: corrupt block 7436 in chain
> 7436, chain length 0, erase mark 0xffff?
> INFTL: formatting chain at block 7436
> INFTL: formatting block 7436
> INFTL: corrupt block 7437 in chain
> 7437, chain length 0, erase mark 0xffff?
> ...
I'm still getting this "corrupt block" error for almost every single
block on each modprobe of inftl, even with my backup chip installed.
I'm slowly crawling through the code, but can anyone offer any obvious
advice on what may be wrong?
Thanks for any suggestions at all!
-- Sarah
--
Sarah Diesburg
Florida State University
"I've got so many kernels I can start making popcorn!"
prev parent reply other threads:[~2008-06-23 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 17:57 inftl and diskonchip 2000 256MB Sarah Diesburg
2008-06-23 21:35 ` Sarah Diesburg [this message]
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=4860173F.4040304@cs.fsu.edu \
--to=diesburg@cs.fsu.edu \
--cc=linux-mtd@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox