UBIFS assert when rebooting a read only ubifs when it's been remounted r/w

[Martin Townsend]

On Tue, May 24, 2016 at 1:26 PM, Richard Weinberger <richard at nod.at> wrote:
> Am 24.05.2016 um 12:37 schrieb Martin Townsend:
>> Here's a link to the image
>> https://file.io/0s7OA9
>
> 404 :-(
>
>> I've just tried on another board and can still get the same assert so
>> it's not just a one off. I also saw this warning whilst formatting
>> this board.  I tried reflashing again until I did not get the warning
>> below but still saw the assert so I don't think they are related.
>> ubiformat: mtd12 (nand), size 533725184 bytes (509.0 MiB), 4072
>> eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
>> libscan: scanning eraseblock 4071 -- 100 % complete
>> ubiformat: 4070 eraseblocks are supposedly empty
>> ubiformat: 2 bad eraseblocks found, numbers: 1324, 1640
>> ubiformat: flashing eraseblock 191 -- 17 % complete  [   51.525672]
>> ------------[ cut here ]------------
>> [   80.185567] WARNING: CPU: 0 PID: 896 at
>> /home/poweroasis/bia/build/am43-controller-aquila/tmp/work-shared/am43-controller-aquila/kernel-source/drivers/mtd/nand/nand_base.c:928
>> nand_wait+0x150/0x174()
>
> Not good. Please verify.
> See the comment above that WARN_ON().
>

Try this one:
http://gofile.io/?id=P2z2Zd


Oops sorry about that, trying to do to many things today and missed
the cut here. manged to get the WARN_ON twice in succession this
morning but as you can guess it won't fire now.  It did get this error
though?
ubiformat: formatting eraseblock 3867 -- 93 % co[   92.443658] nand:
nand_erase_nand: attempt to erase a bad block at page 0x0003dc80
ubiformat: formatting eraseblock 3934 -- 95 % complete  libmtd:
error!: MEMERASE64 ioctl failed for eraseblock 3934 (mtd12)
        error 5 (Input/output error)

ubiformat: error!: failed to erase eraseblock 3934
           error 5 (Input/output error)
ubiformat: marking block 3934 bad
ubiformat: formatting eraseblock 4071 -- 100 % complete

I'll send the full backtrace when I get it to fire again.


> Thanks,
> //richard