mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Teresa Gámez" <t.gamez@phytec.de>
To: barebox@lists.infradead.org
Subject: [PATCH] AM335x: MLO image issue
Date: Mon, 23 Mar 2015 16:17:32 +0100	[thread overview]
Message-ID: <1427123853-26983-1-git-send-email-t.gamez@phytec.de> (raw)

Hello,

we have encountered an issue in the AM335x MLO, which seems to depend on the 
image size itself. The bootloader hangs up in the decompress_unlzo() function.
The decompress_unlzo() function fails with "dest len longer than block size"
and ends up in it's error function in an infinite loop.

As the error seems to depend in the image size, adding or removing random code
makes the image working again.

We have seen this issue so far only with a MLO size of 98823 bytes and
barebox.z size: 61003 bytes. But could reproduce it using different toolchains.

So we suspect this is an issue in the lzo code. 
Syncing the lzo code with the kernel code, seems to help.
For this we have attached a patch.
But we are unsure if this is the solution to the bug we have.

Any ideas on this?

Regards,
Teresa

Stefan Müller-Klieser (1):
  lib/lzo: port lzo fix from upstream kernel

 lib/lzo/lzo1x_decompress_safe.c | 105 ++++++++++++++++++++++------------------
 1 file changed, 58 insertions(+), 47 deletions(-)

-- 
1.9.1


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2015-03-23 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 15:17 Teresa Gámez [this message]
2015-03-23 15:17 ` [PATCH] lib/lzo: port lzo fix from upstream kernel Teresa Gámez
2015-03-24  8:26   ` Holger Schurig
2015-03-24  6:30 ` [PATCH] AM335x: MLO image issue Sascha Hauer
2015-03-24  8:30   ` Holger Schurig

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=1427123853-26983-1-git-send-email-t.gamez@phytec.de \
    --to=t.gamez@phytec.de \
    --cc=barebox@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox