Hi,
we are using P2020 Processor, when i power up the board
NOR BOOT CONSOLE: U_boot is working fine, but at kernel level it stalls middle only it shows like kernel panic not syncing: Attempted to kill the idle task! Rebooting in 180 seconds. or Unable to handle kernel paging request for data at address 0x00000009 Faulting instruction address: 0xc0093780 it doesn't boot totally what could be the problem, even it shows same thing from the SD boot also, i am attached console log , please help me.
console log
U-Boot 2014.07QorIQ-SDK-V1.7+g659b6a2 (Aug 19 2016 - 12:55:09)
CPU0: P2020E, Version: 2.1, (0x80ea0021)
Core: e500, Version: 5.1, (0x80211051)
Clock Configuration:
CPU0:1200 MHz, CPU1:1800 MHz,
CCB:600 MHz,
DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:37.500 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Board: P2020RDB-PCA CPLD: V4.2 PCBA: V4.0
rom_loc: nor upper bank
SD/MMC : 8-bit Mode
eSPI : Disabled
I2C: ready
SPI: ready
DRAM: Detected UDIMM
1 GiB (DDR3, 64-bit, CL=6, ECC off)
Flash: 64 MiB
L2: 512 KiB enabled
NAND: 128 MiB
MMC: FSL_SDHC: 0
PCIe1: disabled
PCIe2: disabled
In: serial
Out: serial
Err: serial
Net: No address specified for VSC7385 microcode.
Phy not found
PHY reset timed out
eTSEC1 [PRIME], eTSEC2, eTSEC3
Hit any key to stop autoboot: 0
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-3.12.19-rt30-QorIQ-SDK-V1.
Created: 2016-10-26 5:50:59 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 4214294 Bytes = 4 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 00c00000
Booting using the fdt blob at 0xc00000
Uncompressing Kernel Image ... OK
Loading Device Tree to 03ff9000, end 03fff56f ... OK
WARNING: could not find compatible node fsl-usb2-dr: FDT_ERR_NOTFOUND.
Using P2020RDB-PC machine description
Memory CAM mapping: 256/256/256 Mb, residual: 256Mb
Linux version 3.12.19-rt30-QorIQ-SDK-V1.7+g91a3ad25 (santosh@santosh-Inspiron-36
CPU maps initialized for 1 thread per core
bootconsole [udbg0] enabled
setup_arch: bootmem
mpc85xx_rdb_setup_arch()
mpc85xx_qe_init: Could not find Quicc Engine node
MPC85xx RDB board from Freescale Semiconductor
arch: exit
Zone ranges:
DMA [mem 0x00000000-0x2fffffff]
Normal empty
HighMem [mem 0x30000000-0x3fffffff]
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000-0x3fffffff]
MMU: Allocated 1088 bytes of context maps for 255 contexts
PERCPU: Embedded 7 pages/cpu @c1176000 s7104 r8192 d13376 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
Kernel command line: root=/dev/mtdblock2 rootfstype=jffs2 rw console=ttyS0,11520
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Sorting __ex_table...
Memory: 963772K/1048576K available (6024K kernel code, 320K rwdata, 1800K rodat)
Kernel virtual memory layout:
* 0xfff5f000..0xfffff000 : fixmap
* 0xffc00000..0xffe00000 : highmem PTEs
* 0xffbfc000..0xffc00000 : early ioremap
* 0xf1000000..0xffbfc000 : vmalloc & ioremap
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
NR_IRQS:512 nr_irqs:512 16
mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe40000, max 2 CPUs
mpic: ISU size: 256, shift: 8, mask: ff
mpic: Initializing for 256 sources
mpc85xx_rdb_pic_init: Could not find qe-ic node
clocksource: timebase mult[d555555] shift[24] registered
Console: colour dummy device 80x25
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
mpic: requesting IPIs...
Unable to handle kernel paging request for instruction fetch
Faulting instruction addOops: Kernel access of blists in Zone order,
Machine check in kernel mode.
Caused by (from MCSR=100Data Cache Parity Error
Oops: Machine check, sig: 7 [#2]
SMP NR_CPUS=8 P2020RDB-PC
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.12.19-rt30-QorIQ-SDK-V1.7+g91a3ad257
task: ef0535c0 ti: effee000 task.ti: ef06e000
NIP: c05ddc3c LR: c05ddc3c CTR: c0011180
REGS: effeff10 TRAP: 0204 Not tainted (3.12.19-rt30-QorIQ-SDK-V1.7+g91a3ad25)
MSR: 00021000 <CE,ME> CR: 22004022 XER: 00000000
GPR00: c05ddc3c ef06f630 ef0535c0 0000002d 00021000 0000002e 00000000 00000001
GPR08: c07f44a4 c07f44a0 c07f44a4 00000040 22004024 00000000 00000001 01411890
GPR16: 808010d6 80000910 09388281 c07e81c8 c07e81c8 c07e81c8 00000000 c08399c4
GPR24: 00021000 c0840000 ef06f6b0 c06fe664 ef06e000 c07f0000 0000000b c083c5b8
NIP [c05ddc3c] printk+0x68/0x78
LR [c05ddc3c] printk+0x68/0x78
Call Trace:
[ef06f630] [c05ddc3c] printk+0x68/0x78 (unreliable)
[ef06f670] [c000a808] die+0xe8/0x294
[ef06f6a0] [c000f4ac] handle_page_fault+0x7c/0x80
--- Exception: 400 at 0xfdfffbbc
LR = 0xfdfffbbf
Instruction dump:
90c10024 38c00000 90e10028 7d675b78 9101002c 39010008 9121000c 39210018
90010044 91410034 91210010 4baa0e31 <80010044> 38210040 7c0803a6 4e800020
---[ end trace 487d9901f2f411d7 ]---
Kernel panic - not syncing: Attempted to kill the idle task!
Rebooting in 180 seconds..
Rergards
Naresh
Hello naresh puli,
Are you using NXP demo board or bringing up a new target board now?
According to the log, it seems that you built images by yourself, would you please provide your Kernel configuration and dts file?
In addition, what had you modified in u-boot?
Thanks,
Yiping
hi,
how can i fix this kernel panic issue, how can i come out this problem its stopping me for a long time?? please help me
linux-headers-3.19.0-71-generic
# see Documentation/kbuild/kconfig-language.txt.
#
mainmenu "Linux/$ARCH $KERNELVERSION Kernel Configuration"
config SRCARCH
string
option env="SRCARCH"
source "arch/$SRCARCH/Kconfig"
pls give me specific response
Thanks
regards
naresh
Hello naresh puli,
Please provide Kernel configuration file (.config) and dts file, then I could do verification on my target board.
Thanks,
Yiping
hi yiping,
we are bring up new boards, how we check the kernel configuration and dts file
regards
naresh
have a nice day...
Hello naresh puli,
According to your Kernel boot log, Kernel uImage was generated on 2016-10-26. If it was generated by you, please send the .config file to me to do more investigation, which was saved with the command "make ARCH=powerpc menuconfig".
If the Kernel image was not generated by you, please boot your target board with the attached images, and captured the log to me.
tftp 1000000 uImage
tftp c00000 dtb
bootm 1000000 - c00000
If you don't have tftp sever, you also could use CodeWarrior to program uImage and dtb file to NOR flash, then boot from NOR FLASH directly.
Thanks,
Yiping