From: Lars Michael <lars.michael@yahoo.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: NAND device: all blocks bad after restart, how to recover?
Date: Fri, 25 Mar 2011 07:03:07 -0700 (PDT) [thread overview]
Message-ID: <759739.22764.qm@web30205.mail.mud.yahoo.com> (raw)
In-Reply-To: <1299762378.6676.7.camel@localhost>
--- On Thu, 10/3/11, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> From: Artem Bityutskiy <dedekind1@gmail.com>
> Subject: Re: NAND device: all blocks bad after restart, how to recover?
> To: "Lars Michael" <lars.michael@yahoo.com>
> Cc: linux-mtd@lists.infradead.org
> Date: Thursday, 10 March, 2011, 14:06
> On Wed, 2011-03-09 at 08:39 -0800,
> Lars Michael wrote:
> > Hello,
> >
> > I repost this issue, with correct subject and hope to
> have some
> > feedback. After working with getting UBI images
> mounted in Linux (it did
> > work for a sec!) the NAND device suddenly went totally
> bad after a system
> > restart! So all blocks are reported bad and the mtd is
> no longer visible
> > in Linux.
>
> So do mtd tests work fine with your flash?
>
> > Before it had just a few bad blocks.
>
We investigated more and have found that the FlexBus on the Coldfire can cause problems for the NAND device. When the FlexBus devices are removed
the NAND device comes back to life, and is again accessible. So now I
can get back to the UBI part of the project :-)
Regards,
- Lars
next prev parent reply other threads:[~2011-03-25 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.15984.1299679972.1534.linux-mtd@lists.infradead.org>
2011-03-09 16:39 ` NAND device: all blocks bad after restart, how to recover? Lars Michael
2011-03-10 13:06 ` Artem Bityutskiy
2011-03-25 14:03 ` Lars Michael [this message]
2011-03-31 12:11 ` Artem Bityutskiy
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=759739.22764.qm@web30205.mail.mud.yahoo.com \
--to=lars.michael@yahoo.com \
--cc=dedekind1@gmail.com \
--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