Otto,
What did this issue end up being for you? I'm seeing a similar issue on my
Xilinx-based platform?
Justin D.
--
Sent from: http://u-boot.10912.n7.nabble.com/
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Thanks a lot for your help Richard & Heiko ! I appreciate it
I agree, this does not look u-boot or ubifs related anymore
/Otto
On Tue, May 22, 2018 at 2:31 AM, Heiko Schocher wrote:
> Hello Otto,
>
> Am 22.05.2018 um 08:24 schrieb Richard Weinberger:
>>
>> Otto,
>>
>> Am Dienstag, 22. Mai 2018
Hello Otto,
Am 22.05.2018 um 08:24 schrieb Richard Weinberger:
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
* Whe
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
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 re
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, err
Otto,
Am Freitag, 18. Mai 2018, 23:02:17 CEST schrieb Otto Blom:
> Hallo Heiko & Richard !
>
> Turns out the len and out_len do not match, much like you suspected.
> Out_len is 2 bytes short (4094 vs 4096) See log below
>
> UBIFS DBG tnc: search key (5725, data, 124)
> UBIFS DBG tnc: found 1, lv
Hi Richard !
Correct, the first error is printed in U-boot 2018.1 (which also
matches the error I see if I try to read the file in Linux 4.9).
The ubi file is created using Yocto 2.4.1 (comes with PetaLinux
2018.1) with the following settings
MKUBIFS_ARGS = " -m 2048 -e 126976 -c 4096 -x lzo "
U
Hallo Heiko & Richard !
Turns out the len and out_len do not match, much like you suspected.
Out_len is 2 bytes short (4094 vs 4096) See log below
UBIFS DBG tnc: search key (5725, data, 124)
UBIFS DBG tnc: found 1, lvl 0, n 2
UBIFS DBG tnc: LEB 566:61864, key (5725, data, 124)
UBIFS DBG io: LEB 5
Otto, Heiko,
Am Freitag, 18. Mai 2018, 10:44:43 CEST schrieb Heiko Schocher:
> Hello Otto,
>
> Am 17.05.2018 um 23:12 schrieb Otto Blom:
> > Hi There !
> >
> > I'm seeing a strange problem with u-boot 2018.1 and Linux 4.14 (Xilinx
> > Petalinux 2018.1).
> > If I write a ubifs image to flash usin
Hello Otto,
Am 17.05.2018 um 23:12 schrieb Otto Blom:
Hi There !
I'm seeing a strange problem with u-boot 2018.1 and Linux 4.14 (Xilinx
Petalinux 2018.1).
If I write a ubifs image to flash using Linux 4.9 I can mount and read
files from the image
in both u-boot 2018.1 and Linux 4.14. However as
Hi There !
I'm seeing a strange problem with u-boot 2018.1 and Linux 4.14 (Xilinx
Petalinux 2018.1).
If I write a ubifs image to flash using Linux 4.9 I can mount and read
files from the image
in both u-boot 2018.1 and Linux 4.14. However as soon as I write a new
file to the file-system
from Linux
12 matches
Mail list logo
