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: Sat, 19 May 2018 10:37:55 +0200 [thread overview]
Message-ID: <3321141.P3ba7yLJY1@blindfold> (raw)
In-Reply-To: <CAEBv-SE0_kTEQkKbbKyE13PM=dMXYGbpWDv4M0+EEV7yzsAK8A@mail.gmail.com>
Am Samstag, 19. Mai 2018, 01:56:33 CEST schrieb Otto Blom:
> UBIFS error (ubi0:0 pid 0): crypto_comp_decompress: cannot decompress
> 2801 bytes, compressor lzo, error -6
LZO_E_LOOKBEHIND_OVERRUN...
> UBIFS error (ubi0:0 pid 0): ubifs_decompress: cannot decompress 2801
> bytes, compressor lzo, error -6
> ubifs_decompress RC: -6 len: 4096 out_len: 3377
> UBIFS error (ubi0:0 pid 0): read_block: bad data node (block 3, inode 68)
> magic 0x6101831
> crc 0xf15144c6
> node_type 1 (data node)
> group_type 0 (no node group)
> sqnum 3276
> len 2849
> key (68, data, 3)
> size 4096
> compr_typ 1
> data size 2801
> data:
> UBIFS error (ubi0:0 pid 0): do_readpage: cannot read page 3 of inode
> 68, error -22
> Error reading file '/boot/Image'
So, LZO *does* return an error.
Did you edit the logs in your last mails? Or was some U-Boot silencing option
enabled?
Please double-check whether your setup is correct.
Does it work if you disable compression?
Your UBIFS image looks good.
I checked the data node by hand and was able to read that file on 4.9.100 and linus
as of today.
Thanks,
//richard
next prev parent reply other threads:[~2018-05-19 8:37 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 [this message]
2018-05-22 1:30 ` Otto Blom
2018-05-22 6:24 ` Richard Weinberger
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=3321141.P3ba7yLJY1@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.