From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Nataraj S Narayan <nataraj@vaaraahi.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Ubifs issues on Samsung Nand versus Micron
Date: Fri, 12 Aug 2011 17:27:01 +0200 [thread overview]
Message-ID: <4E454645.7060802@parrot.com> (raw)
In-Reply-To: <4E458415.7040005@vaaraahi.com>
Nataraj S Narayan a écrit :
> Hi
>
> Using Samsung Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB
> 3,3V 8-bit), on at91sam9263 board, with Arm-linux.
>
> Getting the following errors intermittently:-
>
>
> UBI error: ubi_io_read: error -74 (ECC error) while reading 129024 bytes
> from PEB 517:2048, read 129024 bytes
> usb 1-1: new full speed USB device number 2 using at91_ohci
> UBIFS: recovery needed
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> uncorrectable error :
> UBI error: ubi_io_read: error -74 (ECC error) while reading 106496 bytes
> from PEB 782:2048, read 106496 bytes
> UBIFS error (pid 1): ubifs_recover_leb: LEB 225 scanning failed
> VFS: Cannot open root device "ubi0:root" or unknown-block(0,0)
> ~
>
>
> Same issue when on kernel 2.6.30 and also on "commit
> d6c9836c1114242aa89ea228bb1c43c17752b76c" of ubifs-2.6.
>
> I don't have the said problem with Mircon Nand.
>
> Please help to find a solution to this issue. Is it the nand driver
> which is the culprit?
>
Are you sure your timming are correct ?
Try to see if you reproduce the problem with slower timming.
Matthieu
prev parent reply other threads:[~2011-08-12 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 19:50 Ubifs issues on Samsung Nand versus Micron Nataraj S Narayan
2011-08-12 15:27 ` Matthieu CASTET [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=4E454645.7060802@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nataraj@vaaraahi.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