Re: ubiattach problem

[Oren <oren_s3@VERIFONE.com>]

I already have these option on.

#
# UBI - Unsorted block images
#
CONFIG_MTD_UBI=y
CONFIG_MTD_UBI_WL_THRESHOLD=4096
CONFIG_MTD_UBI_BEB_RESERVE=1
# CONFIG_MTD_UBI_GLUEBI is not set

#
# UBI debugging options
#
CONFIG_MTD_UBI_DEBUG=y
CONFIG_MTD_UBI_DEBUG_MSG=y
CONFIG_MTD_UBI_DEBUG_PARANOID=y
CONFIG_MTD_UBI_DEBUG_DISABLE_BGT=y
CONFIG_MTD_UBI_DEBUG_USERSPACE_IO=y
# CONFIG_MTD_UBI_DEBUG_EMULATE_BITFLIPS is not set
# CONFIG_MTD_UBI_DEBUG_EMULATE_WRITE_FAILURES is not set
# CONFIG_MTD_UBI_DEBUG_EMULATE_ERASE_FAILURES is not set

#
# Additional UBI debugging messages
#
CONFIG_MTD_UBI_DEBUG_MSG_BLD=y
CONFIG_MTD_UBI_DEBUG_MSG_EBA=y
CONFIG_MTD_UBI_DEBUG_MSG_WL=y
CONFIG_MTD_UBI_DEBUG_MSG_IO=y

On Tue, 2009-07-07 at 16:28 +0300, Artem Bityutskiy wrote:
> On Tue, 2009-07-07 at 16:21 +0300, Oren wrote:
> > ubinize: LEB size:      126976
> > ubinize: PEB size:      131072
> > ubinize: min. I/O size: 2048
> > ubinize: sub-page size: 2048
> > ubinize: VID offset:    2048
> > ubinize: data offset:   4096
> > ubinize: loaded the ini-file "images/ubinize.cfg"
> > ubinize: count of sections: 1
> > 
> > ubinize: parsing section "ubifs"
> > ubinize: mode=ubi, keep parsing
> > ubinize: volume type: dynamic
> > ubinize: volume ID: 0
> > ubinize: volume size: 16777216 bytes
> > ubinize: volume name: NAND-block1
> > ubinize: volume alignment: 1
> > ubinize: autoresize flags found
> > ubinize: adding volume 0
> > ubinize: writing volume 0
> > ubinize: image file: images/ubifs_ncomp.img
> > 
> > ubinize: writing layout volume
> > ubinize: done
> 
> OK, thanks. Can I please see what the kernel UBI is doing?
> 
> Could you please enable this option in the kernel config:
> 
> Device Drivers  --->
>   <*> Memory Technology Device (MTD) support  --->
>     UBI - Unsorted block images  --->
>       Additional UBI debugging messages  --->
>         [*] Additional UBI initialization and build messages
> 
> Then attach the UBI device, reproduce the problem, and give me UBI
> output. I want to see what UBI finds on the flash. Please, refer
> this section for more information about how to capture the debugging
> messages:
> http://www.linux-mtd.infradead.org/faq/ubi.html#L_how_debug
>