Kernel reboots while unpacking

[mi_yagi]

Hi,
I have QQ2440 board and I have a problem with booting my board since yesterday. The kernel reboots in the middle of uncompressing itself and I can't find any reason for that. I haven't been using the board for a couple weeks but I left it in perfectly working state with Angstrom distro running on the SD card.
My setup is:

• U-Boot 1.3.2-moko12
  Linux 2.6.29 (both patched using the patches from Leshaks site)

I use following env settings for uboot:

Code: Select all

qq2440 #    printenv
bootdelay=3
baudrate=115200
ethaddr=08:00:3e:26:0a:5b
mtdids=nand0=nandflash0
mtdparts=mtdparts=nandflash0:2m@0(kernel),8m(jffs2),-(yaffs)
"noinitrd=root=/dev/mtdblock1 rootfstype=jffs2 rw console=ttySAC0,115200"
partition=nand0,0
mtddevnum=0
mtddevname=kernel
bootcmd=nand read 0x32000000 0x100000 0x200000; bootm 0x32000000
filesize=200000
fileaddr=32000000
netmask=255.255.255.0
ipaddr=192.168.0.2
serverip=192.168.0.1
bootargs=noinitrd root=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext2 rw init=/sbin/init console=ttySAC0,115200
stdin=serial
stdout=serial
stderr=serial

Environment size: 572/65532 bytes

I am 100% sure that the "S3C Reboot on decompression errror" is switched off in the Kernel config.
Here's the output I get on the serial terminal:

Code: Select all

qq2440 # boot

NAND read: device 0 offset 0x100000, size 0x200000
 2097152 bytes read: OK
## Booting kernel from Legacy Image at 32000000 ...
   Image Name:
   Created:      2009-02-13  13:30:46 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1598560 Bytes =  1.5 MB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.......

U-Boot 1.3.2-moko12 (Apr 18 2010 - 21:33:57)

I2C:   ready
DRAM:  64 MB
Flash:  2 MB
NAND:  64 MiB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0

I'm currently recompiling the kernel with some extra debug options on to see if there will be any hints on what goes wrong but if anyone had same issue and has a clue how to solve it I would really appriciate his help.

Thanks & regards,
Chris Ciesielski