LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Angielski <jangiels@speakeasy.net>
To: "Povolotsky, Alexander" <Alexander.Povolotsky@marconi.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ?
Date: Thu, 30 Dec 2004 19:28:04 -0500	[thread overview]
Message-ID: <1104452884.13899.6.camel@nighteyes.localdomain> (raw)
In-Reply-To: <313680C9A886D511A06000204840E1CF0A647439@whq-msgusr-02.pit.comms.marconi.com>

On Thu, 2004-12-30 at 17:27, Povolotsky, Alexander wrote:
> Hi,
> 
> After few days of wondering through debugging (and with great help) I fixed
> (by inserting watch dog resets into beginning of  while loops in zlib
> functions) my first problem -strange reboot failures during decompression of
> the kernel image by the bootloader.
> However my luck expired beyond this fix so far ... ;-).
> Now I am getting "controlled" failure (during the same decompression as
> described above):

A quick suggestion would be try increase the load address that you are
using for loading the kernel image.  You might have a slight bit of
overlap that is only showing up after the memory contains non-zero
values.

Jeff Angielski

  parent reply	other threads:[~2004-12-31  0:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 22:27 inflate returned FFFFFFFD - what does this error exactly mean ? Povolotsky, Alexander
2004-12-30 22:44 ` Nigel Cunningham
2004-12-30 23:08 ` Wolfgang Denk
2004-12-31  0:28 ` Jeff Angielski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-02  5:58 Povolotsky, Alexander
2005-01-02 15:32 ` Dan Malek
2005-01-02 16:07 Povolotsky, Alexander

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=1104452884.13899.6.camel@nighteyes.localdomain \
    --to=jangiels@speakeasy.net \
    --cc=Alexander.Povolotsky@marconi.com \
    --cc=linuxppc-embedded@ozlabs.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