[U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command

From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fix initrd length miscalculation in bootm command
Date: Tue, 20 Feb 2007 13:19:13 -0600	[thread overview]
Message-ID: <45DB49B1.3030505@freescale.com> (raw)
In-Reply-To: <20070220190645.23C2235363D@atlas.denx.de>

Wolfgang Denk wrote:
> In message <45DB2370.6090804@freescale.com> you wrote:
>> Also, I was wondering if 200000 is too low of a load address.  Doesn't the 
>> kernel lock that memory or something?
> 
> If you hve a big kernel, that's definitely too low.

I moved it to 400000, and now the kernel starts to boot, but it panics.

bootm $loadaddr
## Booting image at 00400000 ...
    Image Name:   Linux Multiboot-Image
    Created:      2007-02-20  17:28:04 UTC
    Image Type:   PowerPC Linux Multi-File Image (gzip compressed)
    Data Size:    20407878 Bytes = 19.5 MB
    Load Address: 00000000
    Entry Point:  00000000
    Contents:
    Image 0:  1416615 Bytes =  1.4 MB
    Image 1: 18987192 Bytes = 18.1 MB
    Image 2:     4054 Bytes =  4 kB
    Verifying Checksum ... OK
    Uncompressing Multi-File Image ... OK
    Loading Ramdisk to 0ed59000, end 0ff748b8 ... OK
    Loading Device Tree to 0ed56000, end 0ed56fd5 ... Using MPC834x ITX machine 
description
Linux version 2.6.20-gc2944612 (b04825 at ld0169-tx32) (gcc version 4.0.2) #1 Mon 
Feb 19 17:22:35 CST 2007
Found initrd at 0xced59000:0xcff748b8

[snip]

Kernel command line: root=/dev/ram rw console=ttyS0,115200

[snip]

md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Couldn't find valid RAM disk image starting at 0.
No filesystem could mount root, tried:  ext3 ext2 msdos vfat
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)

Now here's something interesting.  The output from "Using MPC834x ITX machine 
description" and "PID hash table entries: 1024 (order: 10, 4096 bytes)" is 
actually displayed twice.  It's as if the kernel spontaneously reboot after 
display the PID line, and then on the second boot it continues as normal.  Is 
this what really happens, or is it some kind of early printk() funkiness?

BTW, the above happens with or without my patch.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale