View Single Post
Posts: 290 | Thanked: 385 times | Joined on Jan 2012 @ Madrid, Spain
#1327
Hi.
I think the 'nand chip'/'omap2-onenand'/'whatever' is showing symptoms of ageing in my backup device (possibly a refurbrished one).....
Code:
[86115.653320] init: xsession/sysuid main process (8139) killed by FPE signal
[86115.653656] init: xsession/sysuid main process ended, respawning
[86409.535064] omap_device: smartreflex.1: new worst case activate latency 0: 2105712
[86443.541137] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0
[86443.541687] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x8
[86443.541931] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x10
[86443.546508] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0xc0
[86443.551147] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0
[86443.553894] onenand_wait: correctable ECC error = 0x5555, addr1 0xb, addr8 0xc
[86443.557708] onenand_wait: controller error! state 7 ctrl 0x0400 intr 0x8000
[86443.557769] onenand_write_ops_nolock: write failed -5
.... and I would like to ask:
Is it possible to use ubiboot to avoid the use of partitions mtd0 --> mtd6? I think this could help to extend the device's life a bit .
I'm running nandtest command and all six show r/w errors.
Maybe only using /dev/mtd0 as bootloader to redirect the process somewhere else would help?
Regard.
 

The Following User Says Thank You to pasko For This Useful Post: