From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: ext Kyungmin Park <kmpark@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCHJ] [MTD] [OneNAND] Allow for controller errors when reading
Date: Mon, 14 Apr 2008 10:04:05 +0300 [thread overview]
Message-ID: <480301E5.1040607@nokia.com> (raw)
In-Reply-To: <9c9fda240804111933w2963db9bx3d78bdca46b1f1fc@mail.gmail.com>
Kyungmin Park wrote:
> On Fri, Apr 11, 2008 at 8:05 PM, Adrian Hunter
> <ext-adrian.hunter@nokia.com> wrote:
>> Controller errors while reading can be caused by
>> corruption caused by a previous powerloss. Because
>> upper level software like JFFS2 treat -EIO as fatal,
>> it is necessary to treat the error as an ECC error.
>>
>
> Umm interesting. You mean it occurs controller error before ecc error
> at power loss case.
> And it needs to define the terminology the Sudden Power Off Recovery
> or POR shortly.
> I'm not sure a previous powerloss means POR.
No it is not what I meant. I have sent another patch which I hope is
clearer.
> Anyway could you show the controller error value?
The controller error value is still printed.
> Since it needs to
> distinguish others e.g., initial bad blocks condition.
The bbt scan has its own wait function - I guess it is
possible to get a controller error while reading oob
from an eraseblock that is not actually a bad block.
I am not sure how it would be possible to tell the
difference.
next prev parent reply other threads:[~2008-04-14 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 11:05 [PATCHJ] [MTD] [OneNAND] Allow for controller errors when reading Adrian Hunter
2008-04-12 2:33 ` Kyungmin Park
2008-04-14 7:04 ` Adrian Hunter [this message]
2008-04-14 7:42 ` Adrian Hunter
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=480301E5.1040607@nokia.com \
--to=ext-adrian.hunter@nokia.com \
--cc=kmpark@infradead.org \
--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