Re: Problem during decompressing kernel routine

Re: Problem during decompressing kernel routine

[Matt Porter]

On Mon, Sep 10, 2001 at 09:20:18AM -0500, Cindy Peters wrote:
>
> I am upgrading to kernel version 2.4.6 from version 2.2.13. I have followed
> through the boot loader code and everything seems to be running correctly. I
> see the following messages:

<snip>

> An image with the same boot loader and the old kernel will run just fine. I
> have examined the header of the vmlinux.gz file and compared it to the old
> version and it looks OK.
>
> Does anyone have any ideas of what the problem is?

Hi Cindy,

You forgot to mention what platform is exhibiting the problem.

--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Problem during decompressing kernel routine

[Cindy Peters]

I am upgrading to kernel version 2.4.6 from version 2.2.13. I have followed
through the boot loader code and everything seems to be running correctly. I
see the following messages:

loaded at:	00200000   0020FBF0
relocated at:	00100000   0010FBF0
board data at:	001001F8   00100214
relocated to:	00200100   0020011C
zimage at:	00205328   00277584
initrd at:		00277584   0046B35B
relocated to:	00E0C000  00FFFDF8
avail ram:	00278000   00600000

Linux/PPC load: root=/dev/ram
Uncompressing Linux...

An image with the same boot loader and the old kernel will run just fine. I
have examined the header of the vmlinux.gz file and compared it to the old
version and it looks OK.

Does anyone have any ideas of what the problem is?

Thanks,

Cindy Peters
Adaptive Micro-Ware, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: Problem during decompressing kernel routine

[Cindy Peters]

I did add some print statements and it gets to the inflate() routine and
does not return. I forgot to mention this. I printed the parameters for the
inflate routine and they seem to be correct.

	s.next_in =   0020533A
	s.avail_in =  0007224A
	s.next_out =  00000000
	s.avail_out = 00400000


Wolfgang wrote:
>Somewhere in the last version of the Linux kernel  they  changed  the
>clock from MHz to Hz. Check you version of the source, and modify the
>value passed in the bd_info structure as needed.

I checked it and the value was correct.

Thanks,

Cindy Peters

-----Original Message-----
From: Peter Desnoyers [mailto:pdesnoyers@chinook.com]
Sent: Monday, September 10, 2001 9:53 AM
To: Cindy Peters
Subject: Re: Problem during decompressing kernel routine


You could try debugging with printouts in the decompression routine.  In
arch/ppc/boot/mbx/misc.c, decompress_kernel() you'll find the following
lines:

        puts("\nUncompressing Linux...");

        gunzip(0, 0x400000, zimage_start, &zimage_size);
        puts("done.\n");
        puts("Now booting the kernel\n");

You're clearly going off into the weeds on the second line, and puts()
is working so you can use it to debug.

--
.....................................................................
 Peter Desnoyers            (781) 457-1165   pdesnoyers@chinook.com
 Chinook Communications     (617) 661-1979   pjd@fred.cambridge.ma.us
 100 Hayden Ave, Lexington MA 02421

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Problem during decompressing kernel routine

[THEDREAM]

I donot know exact answer. because I donot know your situation such as which CPU
you use, how you port Linux and so on.

So I just guess the reason.

I sometimes saw the same message that you see.

In this case, I could port the Kernel when I checked IMMR values in the Kernel.

It's an assumption.

Good Luck. Bye ~~~


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/