From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tim Harvey <tharvey@gateworks.com>, Richard Weinberger <richard@nod.at>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org,
Huang Shijie <b32955@freescale.com>,
Elie De Brauwer <eliedebrauwer@gmail.com>,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: UBIFS corruption after power cut - possibly unstable bits issue?
Date: Tue, 03 Nov 2015 11:10:26 +0200 [thread overview]
Message-ID: <1446541826.6126.124.camel@gmail.com> (raw)
In-Reply-To: <CAJ+vNU28eboKDTei09-rjWOTJ_17CPQ0+UxpOOuc0cr_kj0qhw@mail.gmail.com>
On Mon, 2015-11-02 at 12:27 -0800, Tim Harvey wrote:
> [ 9.507115] UBIFS error (ubi0:0 pid 1): ubifs_recover_master_node:
> failed to recover master node
> ^^^ master node recovery fails
> ...
> [ 9.618335] Kernel panic - not syncing: VFS: Unable to mount root
> fs on unknown-block(0,0)
You need to enable debugging messages, and/or add some custom prints to
'get_master_node()', which for some reason returns an error and makes
'ubifs_recover_master_node()' fail. Figure out where it fails, and we
then can try figuring out why and may be fix it. Add custom printk's if
needed.
next prev parent reply other threads:[~2015-11-03 9:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 19:37 UBIFS corruption after power cut - possibly unstable bits issue? Tim Harvey
2015-10-26 20:01 ` Richard Weinberger
2015-10-26 20:31 ` Tim Harvey
2015-10-26 21:41 ` Richard Weinberger
2015-10-27 19:01 ` Tim Harvey
2015-10-27 19:52 ` Richard Weinberger
2015-11-02 20:27 ` Tim Harvey
2015-11-02 20:31 ` Tim Harvey
2015-11-02 21:31 ` Richard Weinberger
2015-11-02 22:11 ` Brian Norris
2015-11-03 13:38 ` Boris Brezillon
2015-11-16 15:01 ` Tim Harvey
2015-11-30 21:58 ` Tim Harvey
2015-12-01 9:12 ` Boris Brezillon
2015-11-03 9:10 ` Artem Bityutskiy [this message]
2015-11-03 10:06 ` Michal Suchanek
2015-11-03 10:18 ` Ricard Wanderlof
2015-11-03 10:43 ` 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=1446541826.6126.124.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=eliedebrauwer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tharvey@gateworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.