public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jason Liu <liu.h.jason@gmail.com>
To: rithesh@tesbv.com
Cc: linux-mtd@lists.infradead.org, thomas@tesbv.com
Subject: Re: UBIFS second time booting issue
Date: Mon, 26 Oct 2009 18:05:26 +0800	[thread overview]
Message-ID: <e8775dd00910260305v1c6ebe76t56eca8e09071e562@mail.gmail.com> (raw)
In-Reply-To: <20091026145935.uvck3scgs8wgcc8o@bangalore.tesbv.com>

2009/10/26  <rithesh@tesbv.com>:
> Hello,
>
> I have built a ubifs filesystem of size 8MiB. The following steps were
> followed:
>
>
> ./mkfs.ubifs -r /home/rithesh/TITAN/ubifilesystem/ -m 512 -e 15360 -c 511 -o
> /tmp/ubifs.img
>
> ./ubinize -o /tmp/ubi.img -m 512 -s 512 -p 16384 ubinize.cfg
>
> My nand flash is 256MiB with the block size of 16KiB and 512 bytes of page
> size.
>
> The ubinize.cfg contains the following:
>
> [ubifs]
> mode=ubi
> image=/tmp/ubifs.img
> vol_id=0
> vol_size=8MiB
> vol_type=dynamic
> vol_name=rootfs
> vol_flags=autoresize
>
>
> ISSUE:
>
> The ubi.img which gets generate out of the following steps is flashed and
> the kernel comes up for the first time but fails to boot up the second time.
>
> Hence i have enabled the Debug message to traces the bug which points
> towards "switching of ubifs filesystem to readonly mode" but i am not sure
> why this should happen.
> Before switching the readonly mode the ubifs write to the flash fails
> continues, please see the logfile  attached to this mail.
>
> Please guide me through this problem.
>
> Thanks and Regards,
> Rithesh.M
> TES Electronic Solutions(I) Pvt LTD.
>
What utility did you used to write the UBIFS image to NAND flash?
Please make sure not to program the page which data is all 0xFF. Your
issue is called by writting the page which data is all 0xFF.

  reply	other threads:[~2009-10-26 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  9:29 UBIFS second time booting issue rithesh
2009-10-26 10:05 ` Jason Liu [this message]
2009-10-29  4:30   ` rithesh
2009-10-29  8:22     ` Artem Bityutskiy

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=e8775dd00910260305v1c6ebe76t56eca8e09071e562@mail.gmail.com \
    --to=liu.h.jason@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rithesh@tesbv.com \
    --cc=thomas@tesbv.com \
    /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