<html><head></head><body><div style='font-family:Calibri,"Segoe UI",Meiryo,"Microsoft YaHei UI","Microsoft JhengHei UI","Malgun Gothic","Khmer UI","Nirmala UI",Tunga,"Lao UI",Ebrima,sans-serif;font-size:16px;'><div>hi thanks for your reply. the problem is still there. At 800MHZ core its working fine but for 1Ghz its still happening. </div><div>Any suggestion or check point I can monitor.</div><div> </div><div> </div> <div style="border-top-color: rgb(229, 229, 229); border-top-width: 2px; border-top-style: solid;"> <strong>From:</strong> sanjeev sharma<br> <strong>Sent:</strong> 02 May 2014 09:22<br> <strong>To:</strong> Ashish<br> <strong>CC:</strong> Valdis Kletnieks; scottwood@freescale.com; linuxppc-dev@lists.ozlabs.org; kernelnewbies<br> <strong>Subject:</strong> Re: MPC8641 based custom board Kernel stuck at 1000Mhz core clock<br> </div> <div> </div><div dir="ltr"><div><div>Hello Ashish,<br><br></div>is this issue resolved and is this always happening when you are changing core to 1Ghz because i am confused here with sometime Keyword.<br><br></div>Regards<br>Sanjeev Sharma<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 4, 2014 at 1:12 PM, Ashish <span dir="ltr"><<a href="mailto:curieux.khetan@gmail.com" target="_blank">curieux.khetan@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">
<div><div><div class="h5">
<div>On Thursday 03 April 2014 08:55 AM,
sanjeev sharma wrote:<br>
</div>
<blockquote>
<div dir="ltr">
<div>Are you able to capture kernel logs ?<br>
<br>
</div>
Regards<br>
Sanjeev Sharma<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Mar 27, 2014 at 10:01 PM, <span dir="ltr"><<a href="mailto:Valdis.Kletnieks@vt.edu" target="_blank">Valdis.Kletnieks@vt.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">
<div>On Thu, 27 Mar 2014 16:04:37 +0530, Ashish
said:<br>
> Hi,<br>
><br>
> I am using MPC8641-HPCN based custom board and able
to boot linux at<br>
> MPX clock 400Mhz and core clock 800mhz. When I am
increasing core<br>
> frequency ie MPX clock at 400Mhz and core at 1Ghz,
kernel stuck.<br>
<br>
</div>
Step 0: Prove to us that your core actually runs reliable
and stably at 1Ghz.<br>
<br>
Step 1: Figure out *where* it gets stuck. If you have
earlyprintk working on<br>
your board, adding 'initcall_debug ignore_loglevel' to the
kernel cmdline often<br>
helps track down where a kernel hangs during boot.<br>
<br>
<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote></div></div>
Hi, <br>
Does kernel logs means debugging information that kernel prints
while booting using printk or it is something else?<br>
Here is kernel boot logs that kernel printed while booting...<br>
<br>
U-Boot 2013.04 (Jan 27 2014 - 11:21:21)
<br>
<br>
Unicore software on multiprocessor system!!
<br>
To enable mutlticore build define CONFIG_MP
<br>
CPU: 8641, Version: 2.1, (0x80900021)
<br>
Core: E600 Core 0, Version: 2.2, (0x80040202)
<br>
Clock Configuration:
<br>
CPU:1000 MHz, MPX:400 MHz
<br>
DDR:200 MHz (400 MT/s data rate), LBC:25 MHz
<br>
L1: D-cache 32 KB enabled
<br>
I-cache 32 KB enabled
<br>
L2: 512 KB enabled
<br>
Board: MPC8641-HPCN<br>
I2C: ready
<br>
DRAM: 512 MiB
<br>
SDRAM test phase 1:
<br>
SDRAM test phase 2:
<br>
SDRAM test passed.
<br>
Flash: 16 MiB
<br>
EEPROM: NXID v1
<br>
In: serial
<br>
Out: serial
<br>
Err: serial
<br>
Net: eTSEC1, eTSEC2, eTSEC3, eTSEC4 [PRIME]
<br>
Hit any key to stop autoboot: <br>
Speed: 1000, full duplex
<br>
Using eTSEC4 device
<br>
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
<br>
Filename 'uRamdisk'.
<br>
Load address: 0x600000
<br>
Loading:
* #################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
#################################################################
<br>
##################################################
<br>
13.1 MiB/s
<br>
done
<br>
Bytes transferred = 22680188 (15a127c hex)
<br>
Speed: 1000, full duplex
<br>
Using eTSEC4 device
<br>
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
<br>
Filename 'uImage'.
<br>
Load address: 0x16000000
<br>
Loading:
* #################################################################
<br>
#################################################################
<br>
#######################################
<br>
14 MiB/s
<br>
done
<br>
Bytes transferred = 2476304 (25c910 hex)
<br>
Speed: 1000, full duplex
<br>
Using eTSEC4 device
<br>
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
<br>
Filename 'mpc8641_hpcn.dtb'.
<br>
Load address: 0x14000000
<br>
Loading: * #
<br>
2.6 MiB/s
<br>
done
<br>
Bytes transferred = 5540 (15a4 hex)
<br>
## Booting kernel from Legacy Image at 16000000 ...
<br>
Image Name: Linux-3.13.6
<br>
Image Type: PowerPC Linux Kernel Image (gzip compressed)
<br>
Data Size: 2476240 Bytes = 2.4 MiB
<br>
Load Address: 00000000
<br>
Entry Point: 00000000
<br>
Verifying Checksum ... OK
<br>
## Loading init Ramdisk from Legacy Image at 00600000 ...
<br>
Image Name: rootfs
<br>
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
<br>
Data Size: 22680124 Bytes = 21.6 MiB
<br>
Load Address: 00000000
<br>
Entry Point: 00000000
<br>
Verifying Checksum ... OK
<br>
## Flattened Device Tree blob at 14000000
<br>
Booting using the fdt blob at 0x14000000
<br>
Uncompressing Kernel Image ... OK
<br>
Loading Ramdisk to 1e923000, end 1fec423c ... OK
<br>
Loading Device Tree to 007fb000, end 007ff5a3 ... OK <i><u><b>(some
times it stucking here)
</b></u></i><br>
Using MPC86xx HPCN machine description
<br>
Total memory = 512MB; using 1024kB for hash table (at cff00000)
<br>
Linux version 3.13.6 (ashish@ashish-VirtualBox) (gcc version 4.7.2
(GCC) ) #8 Sat Mar 29 10:31:58 IST 2014
<br>
Found initrd at 0xde923000:0xdfec423c
<br>
bootconsole [udbg0] enabled
<br>
setup_arch: bootmem
<br>
mpc86xx_hpcn_setup_arch()
<br>
MPC86xx HPCN board from Freescale Semiconductor
<br>
arch: exit
<br>
Zone ranges:
<br>
DMA [mem 0x00000000-0x1fffffff]
<br>
Normal empty
<br>
HighMem empty
<br>
Movable zone start for each node
<br>
Early memory node ranges
<br>
node 0: [mem 0x00000000-0x1fffffff]
<i><u><b>(some
times here)
</b></u></i><br>
<br>
<br>
</div>
</blockquote></div><br></div>
</div></body></html>