From: Artem Bityutskiy <dedekind1@gmail.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubi deadlock on .36+
Date: Thu, 04 Nov 2010 09:29:09 +0200 [thread overview]
Message-ID: <1288855749.2075.7.camel@localhost> (raw)
In-Reply-To: <AANLkTimKc_EtT6NEwbga8g7AKoGnDSt7UMQwgou_jCXD@mail.gmail.com>
On Wed, 2010-11-03 at 23:30 +0200, Grazvydas Ignotas wrote:
> Hi,
>
> there seems to be some issue with NAND on my OMAP3 board that causes
> CRC errors on 2.6.36 and 2.6.37-rc1. Those seem to be triggering a bug
> in UBI that makes it loop forever (or very long) printing this:
>
> uncorrectable error :
> UBI error: ubi_io_read: error -74 (ECC error) while reading 512 bytes
> from PEB 0:512, read 512 bytes
> uncorrectable error :
> UBI error: ubi_io_read: error -74 (ECC error) while reading 512 bytes
> from PEB 68:512, read 512 bytes
> UBI: run torture test for PEB 68
> UBI: PEB 68 passed torture test, do not mark it a bad
>
>
> here is full log of one minute session, after which I killed power:
> http://notaz.gp2x.de/misc/pnd/logs/linux_20101103_ubi_lockup
Hmm, could you please enable UBI debugging and provide me the logs? See
here for some hints:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_how_send_bugreport
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-11-04 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:30 ubi deadlock on .36+ Grazvydas Ignotas
2010-11-04 7:29 ` Artem Bityutskiy [this message]
2010-11-04 13:07 ` Grazvydas Ignotas
2010-11-13 12:37 ` Artem Bityutskiy
2010-11-13 13:15 ` Artem Bityutskiy
2010-11-13 14:23 ` Grazvydas Ignotas
2010-11-14 7:50 ` 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=1288855749.2075.7.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=notasas@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;
as well as URLs for NNTP newsgroup(s).