All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux
Date: Tue, 22 May 2018 08:24:37 +0200	[thread overview]
Message-ID: <8506860.QLH14q6iHR@blindfold> (raw)
In-Reply-To: <CAEBv-SHPiCynNcEkZWGk3yR+BqivT-56ErtAk9zzqiXEb6iYaw@mail.gmail.com>

Otto,

Am Dienstag, 22. Mai 2018, 03:30:04 CEST schrieb Otto Blom:
> Hi Richard !
> 
> To summarize the observations from the last few days.
> 
> * Linux 4.9 & U-boot 2018 behave the same when attempting to read from
> a ubifs file system
> * Whenever Linux 4.14 writes to a ubifs there is some form of
> incompatibility introduced
> causing assorted errors when the file system is read in Linux 4.9 or
> U-boot. However
> the files can still be read in Linux 4.14.
> 
> This lead me to suspect a problem with the OOB data. So I copied over
> a 16MB textfile to
> a freshly minted no-compression ubifs partition (running 4.14) and ran
> a nanddump both from
> Linux 4.9 and 4.14 and the contents are different - Bit errors are
> present in the 4.9-dump..

This smells like a problem on MTD/NAND-Level.
Decompression might fail because bits changes but didn't get fixed by your driver.

Thanks,
//richard

  reply	other threads:[~2018-05-22  6:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 21:12 [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux Otto Blom
2018-05-18  8:44 ` Heiko Schocher
2018-05-18  9:21   ` Richard Weinberger
2018-05-18 21:02     ` Otto Blom
2018-05-18 21:20       ` Richard Weinberger
2018-05-18 23:56         ` Otto Blom
2018-05-19  8:37           ` Richard Weinberger
2018-05-22  1:30             ` Otto Blom
2018-05-22  6:24               ` Richard Weinberger [this message]
2018-05-22  9:31                 ` Heiko Schocher
2018-05-22 17:23                   ` Otto Blom
2018-12-20 20:12                     ` jbd1986

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=8506860.QLH14q6iHR@blindfold \
    --to=richard@nod.at \
    --cc=u-boot@lists.denx.de \
    /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.