From: Adrian Hunter <adrian.hunter@nokia•com>
To: Felix Radensky <felix@embedded-sol•com>
Cc: "linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>,
"linux-mtd@lists•infradead.org" <linux-mtd@lists•infradead.org>
Subject: Re: UBIFS problem on MPC8536DS
Date: Wed, 14 Oct 2009 19:44:23 +0300 [thread overview]
Message-ID: <4AD5FFE7.7080703@nokia.com> (raw)
In-Reply-To: <4AD5D053.9000901@embedded-sol.com>
Felix Radensky wrote:
> Adrian Hunter wrote:
>> Felix Radensky wrote:
>>> Hi,
>>>
>>> I have a strange problem in linux-2.6.31 running on MPC8536DS board.
>>> It is 100% reproducible, by opening a 350MB tar file into ubifs volume
>>> on NAND flash, and starting erase of NOR flash partition right after
>>> that.
>>>
>>> If I don't start NOR erase, everything works fine. Also, If I run
>>> sync after
>>> tar, no problem occurs. The NOR flash is 32MB Spansion, NAND is
>>> 4GB Samsung.
>>>
>>> The error messages are as follows:
>>>
>>> UBI error: ubi_io_write: error -5 while writing 2048 bytes to PEB
>>> 5812:12288, written 0 bytes
>>> UBI warning: ubi_eba_write_leb: failed to write data to PEB 5812
>>> UBI: recover PEB 5812, move data to PEB 19400
>>> UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB
>>> 5812:512, read 512 bytes
>>> UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB
>>> 19400:512, written 0 bytes
>>> UBI warning: recover_peb: failed to write to PEB 19400
>>> UBI: try again
>>> UBI: recover PEB 5812, move data to PEB 19401
>>> UBI: run torture test for PEB 19400
>>> UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB
>>> 19401:512, written 0 bytes
>>> UBI warning: recover_peb: failed to write to PEB 19401
>>> UBI: try again
>>> UBI: recover PEB 5812, move data to PEB 19402
>>> UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB
>>> 19402:512, written 0 bytes
>>> UBI warning: recover_peb: failed to write to PEB 19402
>>> UBI: try again
>>> UBI: recover PEB 5812, move data to PEB 19403
>>> UBI error: ubi_io_write: error -5 while writing 512 bytes to PEB
>>> 19403:512, written 0 bytes
>>> UBI warning: recover_peb: failed to write to PEB 19403
>>> UBI warning: ubi_ro_mode: switch to read-only mode
>>> UBIFS error (pid 1149): ubifs_wbuf_write_nolock: cannot write 2522
>>> bytes to LEB 389:10240, error -5
>>> UBIFS warning (pid 1149): ubifs_ro_mode: switched to read-only mode,
>>> error -5
>>> UBIFS error (pid 1149): do_writepage: cannot write page 0 of inode
>>> 30708, error -5
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 858 bytes in
>>> jhead 2, error -30
>>> UBIFS error (pid 1149): do_writepage: cannot write page 2 of inode
>>> 29486, error -30
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 721 bytes in
>>> jhead 2, error -30
>>> UBIFS error (pid 1149): do_writepage: cannot write page 1 of inode
>>> 30070, error -30
>>> UBI error: ubi_io_write: error -5 while writing 2048 bytes to PEB
>>> 5022:88064, written 0 bytes
>>> UBI warning: ubi_eba_write_leb: failed to write data to PEB 5022
>>> UBI: recover PEB 5022, move data to PEB 19404
>>> UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB
>>> 5022:512, read 512 bytes
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19404
>>> UBI: try again
>>> UBI: recover PEB 5022, move data to PEB 19405
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19405
>>> UBI: try again
>>> UBI: recover PEB 5022, move data to PEB 19406
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19406
>>> UBI: try again
>>> UBI: recover PEB 5022, move data to PEB 19407
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19407
>>> UBIFS error (pid 1044): ubifs_wbuf_sync_nolock: cannot write 2048
>>> bytes to LEB 788:86016
>>> UBIFS error (pid 1044): ubifs_bg_wbufs_sync: cannot sync
>>> write-buffer, error -30
>>> UBIFS warning (pid 1044): ubifs_ro_mode: switched to read-only mode,
>>> error -30
>>> UBI error: ubi_io_write: error -5 while writing 2048 bytes to PEB
>>> 5817:26624, written 0 bytes
>>> UBI warning: ubi_eba_write_leb: failed to write data to PEB 5817
>>> UBI: recover PEB 5817, move data to PEB 19408
>>> UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB
>>> 5817:512, read 512 bytes
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19408
>>> UBI: try again
>>> UBI: recover PEB 5817, move data to PEB 19409
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19409
>>> UBI: try again
>>> UBI: recover PEB 5817, move data to PEB 19410
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19410
>>> UBI: try again
>>> UBI: recover PEB 5817, move data to PEB 19411
>>> UBI error: ubi_io_write: read-only mode
>>> UBI warning: recover_peb: failed to write to PEB 19411
>>> UBIFS error (pid 1047): ubifs_wbuf_sync_nolock: cannot write 2048
>>> bytes to LEB 385:24576
>>> UBIFS error (pid 1047): ubifs_bg_wbufs_sync: cannot sync
>>> write-buffer, error -30
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 160 bytes in
>>> jhead 1, error -30
>>> UBIFS error (pid 1149): ubifs_write_inode: can't write inode 30709,
>>> error -30
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 160 bytes in
>>> jhead 1, error -30
>>> UBIFS error (pid 1149): ubifs_write_inode: can't write inode 30710,
>>> error -30
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 160 bytes in
>>> jhead 1, error -30
>>> UBIFS error (pid 1149): ubifs_write_inode: can't write inode 30698,
>>> error -30
>>> UBIFS error (pid 1149): make_reservation: cannot reserve 160 bytes in
>>> jhead 1, error -30
>>> UBIFS error (pid 1149): ubifs_write_inode: can't write inode 30711,
>>> error -30
>>>
>>> I'd appreciate any hints on what can cause this. Is it a hardware
>>> problem, mtd layer problem
>>> or UBI problem ?
>> It sounds like you are saying one MTD partition somehow affects another.
>> You should check the MTD partitions are set up correctly. Are you using
>> tools that make assumptions about which mtd partition is which?
>>
>> How do you erase the NOR flash? Is the device node (/dev/mtd...)
>> correct?
> I can also reproduce the problem by reading from NOR, i.e.
>
> dd if=/dev/mtd4 of=/dev/null
I doubt the problem is in UBI or UBIFS, and plenty of people use multiple
MTD partitions with no problem.
Do the NAND and NOR use the same memory controller?
I don't think I can be much help I'm afraid.
next prev parent reply other threads:[~2009-10-14 16:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 10:54 UBIFS problem on MPC8536DS Felix Radensky
2009-10-14 12:36 ` Adrian Hunter
2009-10-14 13:02 ` Felix Radensky
2009-10-14 13:21 ` Felix Radensky
2009-10-14 16:44 ` Adrian Hunter [this message]
2009-10-14 17:48 ` Felix Radensky
2009-10-14 18:13 ` Scott Wood
2009-10-14 20:12 ` Felix Radensky
2009-10-15 20:07 ` Scott Wood
2009-10-16 5:01 ` Felix Radensky
2009-10-16 15:31 ` Scott Wood
2009-10-18 9:38 ` Felix Radensky
2009-10-19 15:40 ` Scott Wood
2009-10-19 19:39 ` Felix Radensky
2009-10-19 19:47 ` Scott Wood
2009-10-19 20:19 ` Felix Radensky
2009-10-20 15:30 ` Felix Radensky
2009-10-22 8:20 ` Felix Radensky
2009-10-22 16:07 ` Scott Wood
2009-10-15 9:54 ` Norbert van Bolhuis
2009-10-15 10:45 ` MPC5121 CAN and USB Kári Davíðsson
2009-10-15 11:20 ` Paul Gibson
2009-10-15 11:36 ` Kári Davíðsson
2009-10-15 18:30 ` Wolfgang Denk
2009-10-15 23:03 ` Paul Gibson
2009-10-15 23:10 ` Wolfgang Denk
2009-10-19 6:46 ` David Jander
2009-10-16 13:53 ` Kári Davíðsson
2009-10-15 12:49 ` UBIFS problem on MPC8536DS Felix Radensky
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=4AD5FFE7.7080703@nokia.com \
--to=adrian.hunter@nokia$(echo .)com \
--cc=felix@embedded-sol$(echo .)com \
--cc=linux-mtd@lists$(echo .)infradead.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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