mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Barbier, Renaud" <renaud.barbier@abaco.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: barebox 2019.07 ubiformat
Date: Wed, 25 Sep 2019 17:44:16 +0000	[thread overview]
Message-ID: <MN2PR16MB3117C56576A8FB7A258431B691870@MN2PR16MB3117.namprd16.prod.outlook.com> (raw)

We recently jumped from barebox 2016.07 to 2019.07. 
Everything went well till the NAND got ubiformated.

Using the version from2016.07, the NOR boot partition can be formatted (FIT image) and NAND (file system) and the system boots.
When using the barebox 2019-07, both storage can be formatted but when booting (Linux 4.16 or 5.2) I get:

nand: device found, Manufacturer ID: 0x01, Chip ID: 0xdc
nand: AMD/Spansion S34ML04G1
nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
1 fixed-partitions partitions found on MTD device ff800000.flash
Creating 1 MTD partitions on "ff800000.flash":
0x000000000000-0x000020000000 : "nand"
fsl,ifc-nand ff800000.nand: IFC NAND device at 0xff800000, bank 1
...
...
ubi0: default fastmap pool size: 200
ubi0: default fastmap WL pool size: 100
ubi0: attaching mtd5
ubi0: fixable bit-flip detected at PEB 2
ubi0: fixable bit-flip detected at PEB 3
ubi0: fixable bit-flip detected at PEB 4
...
ubi0: fixable bit-flip detected at PEB 3270
random: crng init done
ubi0: scanning is finished
__nand_correct_data: uncorrectable ECC error
__nand_correct_data: uncorrectable ECC error
__nand_correct_data: uncorrectable ECC error
...
__nand_correct_data: uncorrectable ECC error
ubi0 warning: ubi_io_read: error -74 (ECC error) while reading 22528 bytes from PEB 0:4096, read only 22528 bytes, retry
__nand_correct_data: uncorrectable ECC error
...
ubi0 error: ubi_io_read: error -74 (ECC error) while reading 22528 bytes from PE
B 0:4096, read 22528 bytes
CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.0-owc-g39fb4f3.tethys-dx1014 #1
Call Trace:
[cf825d18] [c02e7d0c] ubi_io_read+0x1b4/0x37c (unreliable)
[cf825d68] [c02dd9a0] ubi_read_volume_table+0x128/0xb8c
[cf825dc8] [c02ef46c] ubi_attach+0xbc/0x3a0
[cf825df8] [c02e1710] ubi_attach_mtd_dev+0x654/0xcf8
[cf825e58] [c0575ec0] ubi_init+0x198/0x224
[cf825e98] [c0003194] do_one_initcall+0x3c/0x1a8
[cf825ef8] [c055fba8] kernel_init_freeable+0x12c/0x1dc
[cf825f28] [c00033b0] kernel_init+0x14/0x114
[cf825f38] [c000f268] ret_from_kernel_thread+0x14/0x1c

So far I have been looking at the commit in barebox regarding MTD/UBI/UBIFS to v2019.09 and cannot see anything obvious.
I could rebase forward if necessary. Is that something that is been observed by anybody?

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2019-09-25 17:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 17:44 Barbier, Renaud [this message]
2019-09-26  6:41 ` Sascha Hauer
2019-09-26 14:15   ` Barbier, Renaud
2019-09-27  6:44     ` Sascha Hauer
2019-09-27  8:43       ` Barbier, Renaud
2019-10-18 14:36         ` Barbier, Renaud
2019-10-18 15:09           ` Barbier, Renaud
2019-10-21  7:52             ` Sascha Hauer

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=MN2PR16MB3117C56576A8FB7A258431B691870@MN2PR16MB3117.namprd16.prod.outlook.com \
    --to=renaud.barbier@abaco.com \
    --cc=barebox@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