From: Richard Weinberger <richard@nod.at>
To: Akshay Bhat <abhat@lutron.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
hujianyang <hujianyang@huawei.com>
Subject: Re: UBIFS Panic
Date: Mon, 30 Jun 2014 19:34:29 +0200 [thread overview]
Message-ID: <53B19FA5.1030801@nod.at> (raw)
In-Reply-To: <53B19D09.2000007@lutron.com>
Am 30.06.2014 19:23, schrieb Akshay Bhat:
>
>
> On Mon 30 Jun 2014 10:48:01 AM EDT, Richard Weinberger wrote:
>> On Mon, Jun 30, 2014 at 3:01 PM, Akshay Bhat <abhat@lutron.com> wrote:
>>> Thanks for your response. Answers in-line.
>>>
>>>
>>> On Thu 26 Jun 2014 10:36:00 PM EDT, hujianyang wrote:
>>>>
>>>> How did you release data on the flash? What's the partitions on your
>>>> system?
>>>> Did you use MTD_UBI_FASTMAP?
>>>
>>>
>>> Image was flashed using the below command:
>>> ubiformat /dev/mtd11 -f rootfs.ubi -s 512 -O 2048
>>>
>>> UBI fastmap is enabled.
>>> CONFIG_MTD_UBI_FASTMAP=y
>>
>> Do you also use it or is it just enabled?
>
> We do not need/use the fastmap feature. (fm_autoconvert set to 0).
>
> Is enabling UBI_FASTMAP the cause for the panic? If so I can disabled the
> feature and re-test. Do you see any compatibility issue going from:
> Current config -> New config -> Failsafe config
I hope not. :)
Please retry with CONFIG_MTD_UBI_FASTMAP=n.
> Current config: CONFIG_MTD_UBI_FASTMAP = y; fm_autoconvert = 0
> New config: CONFIG_MTD_UBI_FASTMAP = n; fm_autoconvert = 0
> Failsafe kernel config (if the above kernel does not boot):
> CONFIG_MTD_UBI_FASTMAP = y; fm_autoconvert = 0
>
> Snippet of dmesg boot log:
> [ 0.000000] Kernel command line: console=ttyO0,115200n8 noinitrd mem=256M
> root=ubi0:rootfs rw ubi.mtd=11,2048 rootfstype=ubifs rootwait=1 ip=none quiet
> loglevel=3 panic=3
> ............
> [ 0.483696] UBI: default fastmap pool size: 95
> [ 0.483712] UBI: default fastmap WL pool size: 25
This indicates CONFIG_MTD_UBI_FASTMAP=y.
Thanks,
//richard
next prev parent reply other threads:[~2014-06-30 17:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:28 UBIFS Panic Akshay Bhat
2014-06-27 2:36 ` hujianyang
2014-06-30 13:01 ` Akshay Bhat
2014-06-30 14:48 ` Richard Weinberger
2014-06-30 17:23 ` Akshay Bhat
2014-06-30 17:34 ` Richard Weinberger [this message]
2014-07-01 1:09 ` hujianyang
2014-07-01 7:48 ` Richard Weinberger
2014-07-01 14:18 ` Akshay Bhat
2014-07-01 14:32 ` Richard Weinberger
2014-07-01 14:46 ` Akshay Bhat
2014-07-01 14:56 ` Richard Weinberger
2014-07-10 21:38 ` Akshay Bhat
2014-07-10 21:42 ` Richard Weinberger
2014-07-11 20:45 ` Richard Weinberger
2014-07-16 17:31 ` Akshay Bhat
2014-07-16 21:00 ` Richard Weinberger
2014-07-22 18:39 ` Akshay Bhat
2014-07-01 0:58 ` hujianyang
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=53B19FA5.1030801@nod.at \
--to=richard@nod.at \
--cc=abhat@lutron.com \
--cc=hujianyang@huawei.com \
--cc=linux-mtd@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).