linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hujianyang <hujianyang@huawei.com>
To: Akshay Bhat <abhat@lutron.com>
Cc: Richard Weinberger <richard@nod.at>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS Panic
Date: Tue, 1 Jul 2014 09:09:22 +0800	[thread overview]
Message-ID: <53B20A42.6020008@huawei.com> (raw)
In-Reply-To: <53B19D09.2000007@lutron.com>

> 
> 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 don't know. But I found func ubi_wl_get_peb() in drivers/mtd/ubi/wl.c
will return an error ENOSPC without any error messages. And this func
seems related with fastmap feature.

I don't have much experience in this.

  parent reply	other threads:[~2014-07-01  1:10 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
2014-07-01  1:09         ` hujianyang [this message]
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=53B20A42.6020008@huawei.com \
    --to=hujianyang@huawei.com \
    --cc=abhat@lutron.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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).