From: Artem Bityutskiy <dedekind@infradead.org>
To: Manoj <manoj23@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: write error while using UBI/UBIFS
Date: Thu, 11 Jun 2009 09:10:30 +0300 [thread overview]
Message-ID: <1244700630.5847.409.camel@localhost.localdomain> (raw)
In-Reply-To: <1c3f4270906101843u65d64a98recfa07b1a67f3d3d@mail.gmail.com>
On Wed, 2009-06-10 at 18:43 -0700, Manoj wrote:
> So I finally got all patches applied to my tree. I don't see an error
> with mount operation now.
> But I am seeing corrupted data messages.
Is this a real flash? Looks like you have a malfunctioning flash
or driver. Make sure your NAND is fine. You may try running
flash tests which you may find in drivers/mtd/tests in new
kernels, or here:
http://git.infradead.org/users/ahunter/nand-tests.git
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2009-06-11 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 3:05 write error while using UBI/UBIFS Manoj
2009-06-08 5:59 ` Artem Bityutskiy
2009-06-09 2:13 ` Manoj
2009-06-09 5:30 ` Artem Bityutskiy
2009-06-11 1:43 ` Manoj
2009-06-11 6:10 ` Artem Bityutskiy [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=1244700630.5847.409.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manoj23@gmail.com \
/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