linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ashish <curieux.khetan@gmail.com>
To: sanjeev sharma <sanjeevsharmaengg@gmail.com>
Cc: scottwood@freescale.com, linuxppc-dev@lists.ozlabs.org,
	Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: MPC8641 based custom board Kernel stuck at 1000Mhz core clock
Date: Fri, 04 Apr 2014 13:12:40 +0530	[thread overview]
Message-ID: <533E6270.8070700@gmail.com> (raw)
In-Reply-To: <CAGUYZuR+rymKURoHURemEggZ8uktagyhGGuqtaWvN=11DQsoxw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5874 bytes --]

On Thursday 03 April 2014 08:55 AM, sanjeev sharma wrote:
> Are you able to capture kernel logs ?
>
> Regards
> Sanjeev Sharma
>
>
> On Thu, Mar 27, 2014 at 10:01 PM, <Valdis.Kletnieks@vt.edu 
> <mailto:Valdis.Kletnieks@vt.edu>> wrote:
>
>     On Thu, 27 Mar 2014 16:04:37 +0530, Ashish said:
>     > Hi,
>     >
>     >   I am using MPC8641-HPCN based custom board and able to boot
>     linux at
>     > MPX clock 400Mhz and core clock 800mhz. When I am increasing core
>     > frequency ie MPX clock at 400Mhz and core at 1Ghz, kernel stuck.
>
>     Step 0:  Prove to us that your core actually runs reliable and
>     stably at 1Ghz.
>
>     Step 1: Figure out *where* it gets stuck.  If you have earlyprintk
>     working on
>     your board, adding 'initcall_debug ignore_loglevel' to the kernel
>     cmdline often
>     helps track down where a kernel hangs during boot.
>
>
>     _______________________________________________
>     Kernelnewbies mailing list
>     Kernelnewbies@kernelnewbies.org
>     <mailto:Kernelnewbies@kernelnewbies.org>
>     http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
Hi,
Does kernel logs means debugging information that kernel prints while 
booting using printk or it is something else?
Here is kernel boot logs that kernel printed while booting...

U-Boot 2013.04 (Jan 27 2014 - 11:21:21)

Unicore software on multiprocessor system!!
To enable mutlticore build define CONFIG_MP
CPU:   8641, Version: 2.1, (0x80900021)
Core:  E600 Core 0, Version: 2.2, (0x80040202)
Clock Configuration:
        CPU:1000 MHz, MPX:400  MHz
        DDR:200  MHz (400 MT/s data rate), LBC:25   MHz
L1:    D-cache 32 KB enabled
        I-cache 32 KB enabled
L2:    512 KB enabled
Board: MPC8641-HPCN
I2C:   ready
DRAM:  512 MiB
SDRAM test phase 1:
SDRAM test phase 2:
SDRAM test passed.
Flash: 16 MiB
EEPROM: NXID v1
In:    serial
Out:   serial
Err:   serial
Net:   eTSEC1, eTSEC2, eTSEC3, eTSEC4 [PRIME]
Hit any key to stop autoboot:
Speed: 1000, full duplex
Using eTSEC4 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'uRamdisk'.
Load address: 0x600000
Loading: 
*\b#################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
  #################################################################
      ##################################################
      13.1 MiB/s
done
Bytes transferred = 22680188 (15a127c hex)
Speed: 1000, full duplex
Using eTSEC4 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'uImage'.
Load address: 0x16000000
Loading: 
*\b#################################################################
  #################################################################
      #######################################
      14 MiB/s
done
Bytes transferred = 2476304 (25c910 hex)
Speed: 1000, full duplex
Using eTSEC4 device
TFTP from server 192.168.10.1; our IP address is 192.168.10.2
Filename 'mpc8641_hpcn.dtb'.
Load address: 0x14000000
Loading: *\b#
      2.6 MiB/s
done
Bytes transferred = 5540 (15a4 hex)
## Booting kernel from Legacy Image at 16000000 ...
    Image Name:   Linux-3.13.6
    Image Type:   PowerPC Linux Kernel Image (gzip compressed)
    Data Size:    2476240 Bytes = 2.4 MiB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 00600000 ...
    Image Name:   rootfs
    Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
    Data Size:    22680124 Bytes = 21.6 MiB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
## Flattened Device Tree blob at 14000000
    Booting using the fdt blob at 0x14000000
    Uncompressing Kernel Image ... OK
    Loading Ramdisk to 1e923000, end 1fec423c ... OK
    Loading Device Tree to 007fb000, end 007ff5a3 ... OK /_*(some times 
it stucking here) *_/
Using MPC86xx HPCN machine description
Total memory = 512MB; using 1024kB for hash table (at cff00000)
Linux version 3.13.6 (ashish@ashish-VirtualBox) (gcc version 4.7.2 (GCC) 
) #8 Sat Mar 29 10:31:58 IST 2014
Found initrd at 0xde923000:0xdfec423c
bootconsole [udbg0] enabled
setup_arch: bootmem
mpc86xx_hpcn_setup_arch()
MPC86xx HPCN board from Freescale Semiconductor
arch: exit
Zone ranges:
   DMA      [mem 0x00000000-0x1fffffff]
   Normal   empty
   HighMem  empty
Movable zone start for each node
Early memory node ranges
   node   0: [mem 0x00000000-0x1fffffff] /_*(some times here) *_/



[-- Attachment #2: Type: text/html, Size: 9651 bytes --]

  reply	other threads:[~2014-04-04  7:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26  5:09 MPC8641 based custom board kernel Bug Ashish Khetan
2013-12-26  9:07 ` wyang
2013-12-26 11:48   ` Ashish Khetan
2013-12-26 22:51     ` Sri Ram Vemulpali
2013-12-27  5:20       ` Ashish Khetan
2013-12-27  6:40         ` Sri Ram Vemulpali
2014-03-27 10:34         ` MPC8641 based custom board Kernel stuck at 1000Mhz core clock Ashish
2014-03-27 16:31           ` Valdis.Kletnieks
2014-04-03  3:25             ` sanjeev sharma
2014-04-04  7:42               ` Ashish [this message]
2014-05-02  3:52                 ` sanjeev sharma
  -- strict thread matches above, loose matches on Subject: below --
2014-05-03 16:40 curieux.khetan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533E6270.8070700@gmail.com \
    --to=curieux.khetan@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sanjeevsharmaengg@gmail.com \
    --cc=scottwood@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).