From: Artem Bityutskiy <dedekind1@gmail.com>
To: Russell Zuck <rzuck@cincinnatitechnologies.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS corruption after software upgrade
Date: Fri, 31 Aug 2012 14:30:26 +0300 [thread overview]
Message-ID: <1346412626.9709.41.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <500F0D81.8050902@cincinnatitechnologies.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Tue, 2012-07-24 at 17:02 -0400, Russell Zuck wrote:
> I am attempting to troubleshoot an issue where the root partition
> (ubi0_0) of my embedded platform becomes corrupted after a few upgrades
> of our system software.
Just took a look at your dmesg log again, it really does not look like
UBIFS issue. Something has changed so that UBIFS reads all 0xFFs instead
of nodes - may be driver returns bogus data.
If you have a working kernel then you can bisect and find the commit
which broke your system.
E.g., if you know 2.6.32 worked, but 2.6.35 does not, you can check if
2.6.33 works or not. If yes, check 2.6.34. When you find the first
non-working release, you may start using 'git bisect' to find the quilty
commit.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-08-31 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 21:02 UBIFS corruption after software upgrade Russell Zuck
2012-08-01 12:40 ` Russell Zuck
2012-08-02 2:10 ` Subodh Nijsure
2012-08-22 13:18 ` Artem Bityutskiy
2012-08-24 17:55 ` Russell Zuck
2012-08-27 16:17 ` Russell Zuck
2012-08-31 11:21 ` Artem Bityutskiy
2012-08-22 13:21 ` Artem Bityutskiy
2012-08-22 13:02 ` Artem Bityutskiy
2012-08-31 11:30 ` Artem Bityutskiy [this message]
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=1346412626.9709.41.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rzuck@cincinnatitechnologies.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.