inflate returned FFFFFFFD - what does this error exactly mean ?

inflate returned FFFFFFFD - what does this error exactly mean ?

[Povolotsky, Alexander]

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):

I_BAD
return Z_DATA_ERROR
after zlib_inflate
inflate returned FFFFFFFD
exit

what does this error exactly mean ?

Thanks,
Best Regards,
Alex 

Re: inflate returned FFFFFFFD - what does this error exactly mean ?

[Nigel Cunningham]

Hi.

linuxppc-embedded-bounces@ozlabs.org wrote on 31/12/2004 09:27:53:

> 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):
>
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
>
> what does this error exactly mean ?

Going from include/linux/zlib.h, it is a data error: your compressed stream
has somehow been corrupted?

Regards,

Nigel

Re: inflate returned FFFFFFFD - what does this error exactly mean ?

[Wolfgang Denk]

Hi Alex,

in message <313680C9A886D511A06000204840E1CF0A647439@whq-msgusr-02.pit.comms.marconi.com> you wrote:
> 
> 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

You know why I recommended U-Boot :-)

> Now I am getting "controlled" failure (during the same decompression as
> described above):
> 
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
> 
> what does this error exactly mean ?

Most probably it means that the areas where the compressed  image  is
stored   and   to  where  you  copy  the  uncompressed  code  to  are
over-lapping. Try storing the compressed image at  a  higher  address
(like 0x400000 or so).

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
How many seconds are there in a year? If I tell you there are 3.155 x
10^7, you won't even try to remember it. On the other hand, who could
forget that, to within half a percent, pi seconds is  a  nanocentury.
                                               -- Tom Duff, Bell Labs

Re: inflate returned FFFFFFFD - what does this error exactly mean ?

[Jeff Angielski]

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

RE: inflate returned FFFFFFFD - what does this error exactly mean ?

[Povolotsky, Alexander]

>Try storing the compressed image at  a  higher  address
>(like 0x400000 or so).

Originally I had relocation address be 0x00400000;
I also tried 0x00500000 and finally 0x00600000 (shown below)
- all 3 cases give the same error.


loaded at:     00180000 00268160
relocated to:  00600000 006E8160
board data at: 006E6124 006E6140
relocated to:  0060509C 006050B8
zimage at:     0060587D 006E5F82
avail ram:     006E9000 02000000

Linux/PPC load: console=ttyCPM0 panic=3 root=/dev/ram
Uncompressing Linux...
in gzip
after zalloc
after zlib_inflateInit2
after zlib_inflate
inflate returned FFFFFFFD
exit
-----Original Message-----
From: wd@denx.de [mailto:wd@denx.de]
Sent: Thursday, December 30, 2004 6:09 PM
To: Povolotsky, Alexander
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly
mean ? 


Hi Alex,

in message
<313680C9A886D511A06000204840E1CF0A647439@whq-msgusr-02.pit.comms.marconi.co
m> you wrote:
> 
> 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

You know why I recommended U-Boot :-)

> Now I am getting "controlled" failure (during the same 
> decompression as described above):
> 
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
> 
> what does this error exactly mean ?

Most probably it means that the areas where the compressed  image  is stored
and   to  where  you  copy  the  uncompressed  code  to  are over-lapping.
Try storing the compressed image at  a  higher  address
(like 0x400000 or so).

Best regards,

Wolfgang Denk
-----Original Message-----
From: Nigel Cunningham [mailto:Nigel.Cunningham@cyclades.com]
Sent: Thursday, December 30, 2004 5:45 PM
To: Povolotsky, Alexander
Cc: linuxppc-embedded@ozlabs.org; linuxppc-embedded-bounces@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ?

Hi.

linuxppc-embedded-bounces@ozlabs.org wrote on 31/12/2004 09:27:53:

> 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):
>
> I_BAD
> return Z_DATA_ERROR
> after zlib_inflate
> inflate returned FFFFFFFD
> exit
>
> what does this error exactly mean ?

Going from include/linux/zlib.h, it is a data error: your compressed stream
has somehow been corrupted?

Regards,

Nigel
-- 

Re: inflate returned FFFFFFFD - what does this error exactly mean ?

[Dan Malek]

On Jan 2, 2005, at 12:58 AM, Povolotsky, Alexander wrote:

> Originally I had relocation address be 0x00400000;
> I also tried 0x00500000 and finally 0x00600000 (shown below)
> - all 3 cases give the same error.
>
>
> loaded at:     00180000 00268160
> relocated to:  00600000 006E8160

You are doing this backward.  You need to load the
image into memory at a higher address like 0x400000.
According to this message, you are loading at 0x180000.
Don't change the relocation address for the build, just
the address where you initially load it into memory.


	-- Dan

RE: inflate returned FFFFFFFD - what does this error exactly mean ?

[Povolotsky, Alexander]

>You need to load the
>image into memory at a higher address like 0x400000.

Where the initial load address is getting set ?

-----Original Message-----
From: Dan Malek [mailto:dan@embeddededge.com]
Sent: Sunday, January 02, 2005 10:33 AM
To: Povolotsky, Alexander
Cc: 'Jeff Angielski'; 'wd@denx.de'; linuxppc-embedded@ozlabs.org
Subject: Re: inflate returned FFFFFFFD - what does this error exactly mean ?


On Jan 2, 2005, at 12:58 AM, Povolotsky, Alexander wrote:

> Originally I had relocation address be 0x00400000;
> I also tried 0x00500000 and finally 0x00600000 (shown below)
> - all 3 cases give the same error.
>
>
> loaded at:     00180000 00268160
> relocated to:  00600000 006E8160

You are doing this backward.  You need to load the
image into memory at a higher address like 0x400000.
According to this message, you are loading at 0x180000.
Don't change the relocation address for the build, just
the address where you initially load it into memory.


	-- Dan
-----Original Message-----
From: Povolotsky, Alexander 
Sent: Sunday, January 02, 2005 12:58 AM
To: 'wd@denx.de'; 'Jeff Angielski'
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: inflate returned FFFFFFFD - what does this error exactly
mean ? 


>Try storing the compressed image at  a  higher  address
>(like 0x400000 or so).

Originally I had relocation address be 0x00400000;
I also tried 0x00500000 and finally 0x00600000 (shown below)
- all 3 cases give the same error.


loaded at:     00180000 00268160
relocated to:  00600000 006E8160
board data at: 006E6124 006E6140
relocated to:  0060509C 006050B8
zimage at:     0060587D 006E5F82
avail ram:     006E9000 02000000

Linux/PPC load: console=ttyCPM0 panic=3 root=/dev/ram
Uncompressing Linux...
in gzip
after zalloc
after zlib_inflateInit2
after zlib_inflate
inflate returned FFFFFFFD
exit
--