<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3698" name=GENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><FONT size=2><FONT face=Arial>Hi Scott,<BR></FONT><BR><FONT face=Arial>I am
currently trying to bring up 2.6.39 kernel on a target based on
MPC8247<BR>Processor, using the attched .dts file . I get the below logs
while the kernel is booting.<BR>I see that the unflattening of the device tree
and the initial loading of the kernel and ramdisk file system is happening
correctly. Can you point me where exactly I can look for this issue. I am
attaching the .config and .dts file I am using<FONT face=Arial
size=2>.</FONT></P></FONT></FONT><FONT size=2><FONT face=Arial>
<P><BR></FONT><FONT color=#ff0000>bootm 1000000 2000000 c00000</FONT><BR>##
Current stack ends at 0x03e93cc8<BR>* kernel: cmdline image address =
0x01000000<BR>## Booting kernel from Legacy Image at 01000000
...<BR> Image Name: Linux-2.6.39<BR> Image
Type: PowerPC Linux Kernel Image (gzip compressed)<BR>
Data Size: 1766015 Bytes = 1.7 MiB<BR> Load
Address: 00000000<BR> Entry Point:
00000000<BR> <FONT color=#ff0000> Verifying Checksum ...
OK<BR> kernel data at 0x01000040, len = 0x001af27f
(1766015)<BR></FONT>* ramdisk: cmdline image address = 0x02000000<BR>##
Loading init Ramdisk from Legacy Image at 02000000 ...<BR> Image
Name:<BR> Image Type: PowerPC Linux RAMDisk Image (gzip
compressed)<BR> Data Size: 2211111 Bytes = 2.1
MiB<BR> Load Address: 00000000<BR> Entry Point:
00000000<BR> <FONT color=#ff0000>Verifying Checksum ...
OK<BR> ramdisk start = 0x02000040, ramdisk end =
0x0221bd67<BR></FONT>* fdt: cmdline image address = 0x00c00000<BR>##
Checking for 'FDT'/'FDT Image' at 00c00000<BR>* fdt: raw FDT blob<BR>##
<FONT color=#ff0000>Flattened Device Tree blob at
00c00000<BR></FONT> Booting using the fdt blob at
0xc00000<BR> of_flat_tree at 0x00c00000 size
0x00000f12<BR> Uncompressing Kernel Image ... OK<BR>
kernel loaded at 0x00000000, end = 0x00389d20<BR>## initrd_high = 0xffffffff,
copy_to_ram = 1<BR> Loading Ramdisk to 03c76000, end 03e91d27 ...
OK<BR> ramdisk load start = 0x03c76000, ramdisk load end =
0x03e91d27<BR>## device tree at 00c00000 ... 00c00f11 (len=16146
[0x3F12])<BR> Loading Device Tree to 007fc000, end 007fff11 ...
OK<BR>Updating property 'clock-frequency' = 00 fe 70 b8<BR>Updating
property 'bus-frequency' = 03 f9 c2 e0<BR>Updating property
'timebase-frequency' = 00 7f 38 5c<BR>Updating property 'clock-frequency'
= 09 f0 67 30<BR><FONT color=#ff0000>## Transferring control to Linux (at
address 00000000) ...<BR> Booting using OF flat tree...<BR>Using
Freescale MPC8272 ADS machine description<BR>Linux version 2.6.39 (2.6.39)
(ktuser@ktuser) (gcc version 4.4.5 (Buildroot 2011<BR>.02) ) #5 Wed Aug 24
15:02:07 IST 2011<BR>Found initrd at 0xc3c76000:0xc3e91d27<BR>No bcsr in device
tree<BR>Zone PFN ranges:<BR></FONT> DMA
0x00000000 -> 0x00004000<BR> Normal empty<BR>Movable zone
start PFN for each node<BR>early_node_map[1] active PFN
ranges<BR> 0: 0x00000000 -> 0x00004000<BR>Built 1 zonelists
in Zone order, mobility grouping on. Total pages: 16256<BR>Kernel command
line: mem=64M root=/dev/ram rw<BR>PID hash table entries: 256 (order: -2, 1024
bytes)<BR>Dentry cache hash table entries: 8192 (order: 3, 32768
bytes)<BR>Inode-cache hash table entries: 4096 (order: 2, 16384
bytes)<BR>Memory: 57972k/65536k available (3524k kernel code, 7564k reserved,
100k data, 1<BR>137k bss, 168k init)<BR>Kernel virtual memory layout:<BR>
* 0xfffdf000..0xfffff000 : fixmap<BR> * 0xfdfb6000..0xfe000000
: early ioremap<BR> * 0xc5000000..0xfdfb6000 : vmalloc &
ioremap<BR>SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=1,
Nodes=1<BR>NR_IRQS:512 nr_irqs:512 16<BR>No pci pic node in device
tree.<BR>clocksource: timebase mult[1dfc2974] shift[22] registered<BR>console
[ttyCPM0] enabled<BR>pid_max: default: 32768 minimum: 301<BR>Mount-cache hash
table entries: 512<BR>NET: Registered protocol family 16<BR>PCI: Probing PCI
hardware<BR>bio: create slab <bio-0> at 0<BR>vgaarb: loaded<BR>Switching
to clocksource timebase<BR><BR>brd: module loaded<BR>loop: module
loaded<BR>of-flash ff800000.flash: do_map_probe() failed<BR>PPP generic driver
version 2.4.2<BR>PPP Deflate Compression module registered<BR>tun: Universal
TUN/TAP device driver, 1.6<BR>tun: (C) 1999-2004 Max Krasnyansky
<maxk@qualcomm.com><BR>eth0: fs_enet: 00:00:00:00:00:00<BR>eth1: fs_enet:
00:00:00:00:00:00<BR>CPM2 Bitbanged MII: probed<BR>mousedev: PS/2 mouse device
common for all mice<BR>TCP cubic registered<BR>NET: Registered protocol family
10<BR>IPv6 over IPv4 tunneling driver<BR>NET: Registered protocol family
17<BR>Freeing unused kernel memory: 168k init<BR>Populating /dev using udev:
/sbin/udevd: '/lib/libc.so.6' library contains unsup<BR>ported
TLS<BR>/sbin/udevd: '/lib/libc.so.6' library contains unsupported
TLS<BR>/sbin/udevd: can't load library 'libc.so.6'<BR>FAIL<BR>/sbin/udevstart:
'/lib/libc.so.6' library contains unsupported TLS<BR>/sbin/udevstart:
'/lib/libc.so.6' library contains unsupported TLS<BR>/sbin/udevstart: can't load
library 'libc.so.6'<BR>FAIL<BR>done<BR>Starting network...<BR><FONT face=Arial
color=#0000ff></FONT></P>
<P><FONT face=Arial color=#0000ff>Regards, </FONT></P>
<P><FONT face=Arial color=#0000ff>Smitha</FONT> </FONT> </P><P><strong><span style='font-size:10.0pt;font-family:
"Palatino Linotype","serif";color:green'> Please do not print this email unless it is absolutely necessary. </span></strong><span style='font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
<p> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. </p>
<p>WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. </p>
<p>
www.wipro.com
</p>
</BODY></HTML>