freezing at kmem_cache_init when boot linux

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

freezing at kmem_cache_init when boot linux

824 Views
kangdokhui
Contributor I

Hello

I am not good at english.

I have a problem with booting.

I am  using p1011 cpu. 

console print kmem_cache_init and freeze

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

## Booting kernel from Legacy Image at 03000000 ...

   Image Name:   Linux-3.12.19-rt30-QorIQ-SDK-V1.

   Created:      2014-12-03   6:46:34 UTC

   Image Type:   PowerPC Linux Kernel Image (gzip compressed)

   Data Size:    4114839 Bytes = 3.9 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 04000000 ...

   Image Name:   fsl-image-minimal-p1020rdb-20141

   Created:      2014-10-10   1:58:10 UTC

   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)

   Data Size:    2962290 Bytes = 2.8 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 05000000

   Booting using the fdt blob at 0x5000000

   Uncompressing Kernel Image ... OK

   Loading Ramdisk to 1fb19000, end 1fdec372 ... OK

   Loading Device Tree to 03ffa000, end 03fffb05 ... OK

setup_arch: bootmem

mpc85xx_rdb_setup_arch()

mpc85xx_qe_init: Could not find Quicc Engine node

MPC85xx RDB board from Freescale Semiconductor

arch: exit

Top of RAM: 0x20000000, Total RAM: 0x20000000

Memory hole size: 0MB

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]

On node 0 totalpages: 131072

free_area_init_node: node 0, pgdat c08038d4, node_mem_map c0942000

  DMA zone: 1024 pages used for memmap

  DMA zone: 0 pages reserved

  DMA zone: 131072 pages, LIFO batch:31

MMU: Allocated 1088 bytes of context maps for 255 contexts

pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768

pcpu-alloc: [0] 0

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048

Kernel command line: root=/dev/ram0 rw ramdisk_size=30000 mem=512M console=ttyS0,115200n8

PID hash table entries: 2048 (order: 1, 8192 bytes)

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

Sorting __ex_table...

Memory: 524016K/524288K available (5904K kernel code, 316K rwdata, 1808K rodata, 228K init, 1196K bss, 272K reserved, 0K highmem)

Kernel virtual memory layout:

  * 0xfffcf000..0xfffff000  : fixmap

  * 0xff800000..0xffc00000  : highmem PTEs

  * 0xff7fd000..0xff800000  : early ioremap

  * 0xe1000000..0xff7fd000  : vmalloc & ioremap

kmem_cache_init

----------------------------------------------------------------------------------------------------------------------------------

what should I do to solve this problem?

thanks.


ps. If I change mem=512M to mem=128M  then it show more progress.

Labels (1)
0 Kudos
Reply
2 Replies

621 Views
scottwood
NXP Employee
NXP Employee

Use an external debugger to determine the PC, LR, etc. where the CPU is stuck.  Also double check that DDR has been configured correctly including timings.

0 Kudos
Reply

621 Views
kangdokhui
Contributor I

thank you.

it was DDR setting problem.

I didn`t set correctly ddr configuration in u-boot.

now it works well.

0 Kudos
Reply