Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

[K K]

Hi,

We have a lpc-3180 based board and it is up and running fine with 2.6.10
kernel version. We planned to port our board changes into 2.6.32 kernel
version.

As a part of this, we added the architecture dependent  code  (mach
files)  first. Then we changed some of the kernel upgradations.

kernel build successfully. When we booting the board with the new 2.6.32
kernel we are getting following messages and its stops.


------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

U-Boot 1.1.1 (Oct 10 2006 - 21:35:44)


U-Boot code: 80EC0000 -> 80EE9600  BSS: -> 80EEAEE0

SDRAM : 32M detected

RAM Configuration:

Bank #0: 80000000 31 MB

Bank #1: 00000000  0 kB

Flash:  0 kB

NAND:NAND device: Manufacturer ID: 0x20, Chip ID: 0x35 (ST Micro NAND 32MiB
1,8V 8-bit)

Scanning device for bad blocks

Using default environment


In:    serial

Out:   serial

Err:   serial

Hit any key to stop autoboot:  2 1 0

Boot reached stage 1

## Booting image at 80600000 ...

Boot reached stage 2

Boot reached stage 3

   Image Name:   Linux-2.6.32

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1278856 Bytes =  1.2 MB

   Load Address: 80008000

   Entry Point:  80008000

Boot reached stage 4

Boot reached stage 5

Boot reached stage 6

OK

Boot reached stage 7

Boot reached stage 8

Boot reached stage 14

Boot reached stage 15


Starting kernel ...


Uncompressing
Linux.............................................................................
done, booting the kernel.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

For this we tried to add some debug messages:

The complete scenario is as follows.



We have added some of our own print messages (using putstr() etc.) by
changing the code in  arch/arm/boot/compressed/head.S &
arch/arm/boot/compressed/misc.c files. Then, we  could see those messages
before and after calling  ?decompress_kernel? routine.  So, we moved to the
next stage of the booting i.e. checking the processor type. This is done in
?__lookup_processor_type? routine which can be found in
arch/arm/kernel/head-common.S. Here too, we added one of our prints and
this time using ?printascii? routine as ?putstr? is not usable here. But
these messages are not showing up during the boot log.



This can be caused by two reasons:

1. __lookup_processor_type is not being called.

2. Some of it or entire serial interface initialization is missing.



There is less probability for the first reason. Because, after the
decompression of the kernel, immediately the control is passed to the
extracted kernel. Where ?__lookup_processor_type? is the first routine to
be called (see arch/arm/kernel/head.S line 82 in v2.6.32). So there must be
some problem with the ?printascii? routine itself (i.e. serial
communication).

can you help, where the things may go wrong....

Thanks.

-KK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120524/ba1dabf9/attachment.html>

Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

[Domenico Andreoli]

On Thu, May 24, 2012 at 10:52:46AM +0530, K K wrote:
> Hi,

Hi,

> We have a lpc-3180 based board and it is up and running fine with 2.6.10
> kernel version. We planned to port our board changes into 2.6.32 kernel
> version.

2.6.32, really?

> kernel build successfully. When we booting the board with the new 2.6.32
> kernel we are getting following messages and its stops.

Two cases:

  1. earlyprintk is configured and enabled but points to the
     wrong console and your platform hangs on it because it's not
     initialized/ready. the correct console seems ok, the uncompressor
     is able to use it. check debug-macro.S to be sure it uses the
     correct address.

  2. earlyprintk is not enabled (or configured) and your kernel is
     not finding the console (any console= on the cmdline? driver
     issue?) or dies before finding it. try enabling earlyprintk (and
     check debug-macro.S as well).

cheers,
Domenico

ps: post also the kernel configuration

Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

[Baruch Siach]

Hi Domenico,

On Thu, May 24, 2012 at 12:32:21PM +0200, Domenico Andreoli wrote:
> On Thu, May 24, 2012 at 10:52:46AM +0530, K K wrote:
> > We have a lpc-3180 based board and it is up and running fine with 2.6.10
> > kernel version. We planned to port our board changes into 2.6.32 kernel
> > version.
> 
> 2.6.32, really?
> 
> > kernel build successfully. When we booting the board with the new 2.6.32
> > kernel we are getting following messages and its stops.
> 
> Two cases:
> 
>   1. earlyprintk is configured and enabled but points to the
>      wrong console and your platform hangs on it because it's not
>      initialized/ready. the correct console seems ok, the uncompressor
>      is able to use it. check debug-macro.S to be sure it uses the
>      correct address.
> 
>   2. earlyprintk is not enabled (or configured) and your kernel is
>      not finding the console (any console= on the cmdline? driver
>      issue?) or dies before finding it. try enabling earlyprintk (and
>      check debug-macro.S as well).

earlyprintk on ARM is only available since commit 93fd03a8 (ARM: Add an 
earlyprintk debug console), which is included in kernel version 2.6.33. For 
older kernels you can used the following printk hack instead (with 
CONFIG_DEBUG_LL enabled):


diff --git a/kernel/printk.c b/kernel/printk.c
index 5052b54..d685f8a 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
 	/* Emit the output into the temporary buffer */
 	printed_len += vscnprintf(printk_buf + printed_len,
 				  sizeof(printk_buf) - printed_len, fmt, args);
+	{
+		extern void printascii(const char *);
+		printascii(printk_buf);
+	}
 
 
 	/*

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

[Arend van Spriel]

On 05/24/2012 07:22 AM, K K wrote:
> Hi,
> 
> We have a lpc-3180 based board and it is up and running fine with 2.6.10
> kernel version. We planned to port our board changes into 2.6.32 kernel
> version.
> 
> As a part of this, we added the architecture dependent  code  (mach
> files)  first. Then we changed some of the kernel upgradations.
> 
> kernel build successfully. When we booting the board with the new 2.6.32
> kernel we are getting following messages and its stops.

I had a similar issue with a Pandaboard and I needed to patch u-boot:

diff --git a/include/configs/omap4_common.h b/include/configs/omap4_common.h
index d8ac8c0..89f9e89 100644
--- a/include/configs/omap4_common.h
+++ b/include/configs/omap4_common.h
@@ -36,6 +36,7 @@
 #define CONFIG_OMAP44XX                1       /* which is a 44XX */
 #define CONFIG_OMAP4430                1       /* which is in a 4430 */
 #define CONFIG_ARCH_CPU_INIT
+#define CONFIG_SYS_DCACHE_OFF  1       /* not d-cache in u-boot */

 /* Get CPU defs */
 #include <asm/arch/cpu.h>


Gr. AvS

Linux Kernel boot up stops after message "Uncompressing Linux....done, booting the kernel"

[K K]

Hi,

> 2.6.32, really?

Yes kernel is 2.6.32.

>Two cases:

> 1. earlyprintk is configured and enabled but points to the
>    wrong console and your platform hangs on it because it's not
>    initialized/ready. the correct console seems ok, the uncompressor
>     is able to use it. check debug-macro.S to be sure it uses the
>    correct address.

> 2. earlyprintk is not enabled (or configured) and your kernel is
>     not finding the console (any console= on the cmdline? driver
>     issue?) or dies before finding it. try enabling earlyprintk (and
>     check debug-macro.S as well).

I have checked debug-macro.S , console was properly configured and enabled.
Now i can able to see the debug messages on the console.

Thanks..





On Thu, May 24, 2012 at 4:02 PM, Domenico Andreoli <cavokz@gmail.com> wrote:

> On Thu, May 24, 2012 at 10:52:46AM +0530, K K wrote:
> > Hi,
>
> Hi,
>
> > We have a lpc-3180 based board and it is up and running fine with 2.6.10
> > kernel version. We planned to port our board changes into 2.6.32 kernel
> > version.
>
> 2.6.32, really?
>
> > kernel build successfully. When we booting the board with the new 2.6.32
> > kernel we are getting following messages and its stops.
>
> Two cases:
>
>  1. earlyprintk is configured and enabled but points to the
>     wrong console and your platform hangs on it because it's not
>     initialized/ready. the correct console seems ok, the uncompressor
>     is able to use it. check debug-macro.S to be sure it uses the
>     correct address.
>
>  2. earlyprintk is not enabled (or configured) and your kernel is
>     not finding the console (any console= on the cmdline? driver
>     issue?) or dies before finding it. try enabling earlyprintk (and
>     check debug-macro.S as well).
>
> cheers,
> Domenico
>
> ps: post also the kernel configuration
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120525/7b925653/attachment-0001.html>