Hello,
I am trying to create a kernel for P1011 base board. I started by using an existing functional kernel configuration file .config. All component and memory are identical in this 2 board, just different processor. So I was hoping the kernel would work fine, but it did not and I am getting this error, after boot up:
I would appreciate any help in this matter,
U-Boot 2010.12-svn10008 (Nov 10 2014 - 17:38:13) ge4404
CPU: P1011, Version: 1.1, (0x80e50011)
Core: E500, Version: 5.1, (0x80212051)
Clock Configuration:
CPU0:800 MHz,
CCB:400 MHz,
DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), LBC:25 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
I2C: ready
SPI: ready
DRAM: Configuring DDR for 666.667 MT/s data rate
DDR: 2 GiB (DDR3, 32-bit, CL=6, ECC off)
FLASH: 128 MiB
L2: 256 KB enabled
NAND: 1024 MiB
MMC: FSL_ESDHC: 0
EEPROM: Read failed.
PCIe1: Root Complex of Slot 2, x2, regs @ 0xffe0a000
01:00.0 - 14e4:b240 - Network controller
PCIe1: Bus 00 - 01
PCIe2: disabled
In: serial
Out: serial
Err: serial
Net: eTSEC3 is in sgmii mode.
eTSEC1: No support for PHY id 0; assuming generic
eTSEC2: No support for PHY id 0; assuming generic
eTSEC3: No support for PHY id 0; assuming generic
eTSEC1, eTSEC2, eTSEC3
bootmode 2: Booting RFS 1, Kernel 0
Hit any key to stop autoboot: 0
. done
Erased 1 sectors
## Booting kernel from Legacy Image at e8800000 ...
Image Name: Linux-3.0.34-ts-powerpc-rt55+
Created: 2015-01-14 18:42:52 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 3306175 Bytes = 3.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at e8080000
Booting using the fdt blob at 0xe8080000
Uncompressing Kernel Image ... OK
Loading Device Tree to 00ffa000, end 00fff503 ... OK
WARNING: could not find compatiblenode fsl-usb2-dr: FDT_ERR_NOTFOUND.
WARNING: could not find compatible node fsl-usb2-dr: FDT_ERR_NOTFOUND.
Using P2020 RDB machine description
Memory CAM mapping: 256/256/256 Mb, residual: 1280Mb
Linux version 3.0.34-ts-powerpc-rt55+ (akobari@ubuntu) (gcc version 4.6.3 (Timesys 20130114) ) #5 SMP Wed Jan 14 13:42:47 EST 2015
CPU maps initialized for 1 thread per core
bootconsole [udbg0] enabled
setup_arch: bootmem
mpc85xx_rdb_setup_arch()
Found FSL PCI host bridge at 0x00000000ffe0a000. Firmware bus number: 0->1
PCI host bridge /pcie@ffe0a000 ranges:
MEM 0x0000000080000000..0x000000009fffffff -> 0x0000000080000000
IO 0x00000000ffc00000..0x00000000ffc0ffff -> 0x0000000000000000
/pcie@ffe0a000: PCICSRBAR @ 0xfff00000
MPC85xx RDB board from Freescale Semiconductor
arch: exit
Zone PFN ranges:
DMA 0x00000000 -> 0x00030000
Normal empty
HighMem 0x00030000 -> 0x00080000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00080000
MMU: Allocated 1088 bytes of context maps for 255 contexts
PERCPU: Embedded 7 pages/cpu @c2009000 s4448 r8192 d16032 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 520192
Kernel command line: console=ttyS0,115200 rootfstype=ubifs rw root=ubi0:rootfs ubi.mtd=7
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)
Memory: 2072916k/2097152k available (6340k kernel code, 24236k reserved, 280k data, 278k bss, 216k init)
Kernel virtual memory layout:
* 0xfffbf000..0xfffff000 : fixmap
* 0xff800000..0xffc00000 : highmem PTEs
* 0xff7ec000..0xff800000 : early ioremap
* 0xf1000000..0xff7ec000 : vmalloc & ioremap
SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:512
mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe40000, max 1 CPUs
mpic: ISU size: 256, shift: 8, mask: ff
mpic: Initializing for 256 sources
clocksource: timebase mult[5000000] shift[22] registered
Console: colour dummy device 80x25
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
Brought up 1 CPUs
devtmpfs: initialized
NET: Registered protocol family 16
PCI: Probing PCI hardware
pci 0000:00:00.0: ignoring class b20 (doesn't match header type 01)
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
pci 0000:00:00.0: PCI bridge to [bus 01-01]
pci 0000:00:00.0: bridge window [io 0xff7ed000-0xff7fcfff]
pci 0000:00:00.0: bridge window [mem 0x80000000-0x9fffffff]
pci 0000:00:00.0: bridge window [mem pref disabled]
pci 0000:00:00.0: enabling device (0106 -> 0107)
bio: create slab <bio-0> at 0
raid6: int32x1 123 MB/s
raid6: int32x2 199 MB/s
raid6: int32x4 296 MB/s
raid6: int32x8 254 MB/s
raid6: using algorithm int32x4 (296 MB/s)
Freescale Elo / Elo Plus DMA driver
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource timebase
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
fsl-elo-dma ffe0c300.dma: #0 (fsl,eloplus-dma-channel), irq 76
fsl-elo-dma ffe0c300.dma: #1 (fsl,eloplus-dma-channel), irq 77
fsl-elo-dma ffe0c300.dma: #2 (fsl,eloplus-dma-channel), irq 78
fsl-elo-dma ffe0c300.dma: #3 (fsl,eloplus-dma-channel), irq 79
fsl-l2ctlr ffe20000.l2-cache-controller: Entire L2 as cache, provide valid sram address and size
fsl-l2ctlr: probe of ffe20000.l2-cache-controller failed with error -22
fsl-elo-dma ffe21300.dma: #0 (fsl,eloplus-dma-channel), irq 21
fsl-elo-dma ffe21300.dma: #1 (fsl,eloplus-dma-channel), irq 22
fsl-elo-dma ffe21300.dma: #2 (fsl,eloplus-dma-channel), irq 23
fsl-elo-dma ffe21300.dma: #3 (fsl,eloplus-dma-channel), irq 24
fsl-pq_mdio: probe of ffe24520.mdio failed with error -16
audit: initializing netlink socket (disabled)
type=2000 audit(0.508:1): initialized
highmem bounce pool size: 64 pages
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 1488
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42) is a 16550A
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42) is a 16550A
Generic non-volatile memory driver v1.1
brd: module loaded
loop: module loaded
e8000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x002801
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.5.
number of CFI chips: 1
Creating 6 MTD partitions on "e8000000.nor":
0x000000000000-0x000000080000 : "NOR,512KB, Boot Configuration"
0x000000080000-0x000000100000 : "NOR,512KB, DTB Image"
0x000000100000-0x000000800000 : "NOR, 7MB Reserved"
0x000000800000-0x000001000000 : "NOR,8MB Linux Kernel 0"
0x000001000000-0x000001800000 : "NOR,8MB Linux Kernel 1"
0x000007f80000-0x000008000000 : "NOR,512KB, U-BOOT Boot Loader"
NAND device: Manufacturer ID: 0x01, Chip ID: 0xd3 (AMD NAND 1GiB 3,3V 8-bit)
Creating 3 MTD partitions on "ffa00000.flash":
0x000000000000-0x00001f000000 : "NAND,496MB UBIFS 0"
0x00001f000000-0x00003e000000 : "NAND,496MB UBIFS 1"
0x00003e000000-0x000040000000 : "32MB for Fastpath Configuration"
eLBC NAND device at 0xffa00000, bank 1
UBI: attaching mtd7 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 47
UBI: attached mtd7 to ubi0
UBI: MTD device name: "NAND,496MB UBIFS 1"
UBI: MTD device size: 496 MiB
UBI: number of good PEBs: 3968
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 3968
UBI: number of PEBs reserved for bad PEB handling: 39
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 1750748030
UBI: background thread "ubi_bgt0d" started, PID 1039
INFO: rcu_sched_state detected stall on CPU 0 (t=15000 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=60030 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=105060 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=150090 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=195120 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=240150 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=285180 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=330210 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=375240 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=420270 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=465300 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=510330 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=555360 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=600390 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=645420 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=690450 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=735480 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=780510 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=825540 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=870570 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=915600 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=960630 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1005660 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1050690 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1095720 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1140750 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1185780 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1230810 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1275840 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1320870 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1365900 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1410930 jiffies)
INFO: rcu_sched_state detected stall on CPU 0 (t=1455960
Why are you using such an old kernel? I suggest trying the latest upstream kernel (or if you prefer, the latest Freescale SDK kernel). Or, if you really want to run this TimeSys kernel, you should seek support from TimeSys.
What was the "different processor" that you had been using?
BTW, it's hard to read logs that have a blank line between each line...
Hello Scott,
Thanks for reply, I have no choice except to use this kernel:: Linux version 3.0.34-ts-powerpc-rt55+ (akobari@ubuntu) (gcc version 4.6.3 (Timesys 20130114) which is part of a broader product component we use in my company, and I thought Linux version 3.0 is pretty up-to-date,. Any way that's not the issue because I am using the exact kernel for our other board, based on P2020 processor with no issue at all. I am also in contact with TimeSys community as well. I just want to get as much as help I can get to solve my problem. The log file I attached was captured by my editor, and I did not realized it has extra line in between!!!
Again I am using the same kernel by TimeSys with the same .config for P2020 based board, so there is an identical uImage for both and one is working fine the other stuck in this INFO message:
INFO: rcu_sched_state detected stall on CPU
INFO: rcu_sched_state detected stall on CPU
INFO: rcu_sched_state detected stall on CPU
it looks like the cpu is waiting for some events
Ali,
Hello Ali Kobari,
A customer reported a similar problem previously, please check whether it would be helpful to use "nohz=off" Kernel boot parameter to disable dyntick-idle mode.
An idle CPU that is not receiving scheduling-clock interrupts is said to be "dyntick-idle". The CONFIG_NO_HZ_IDLE=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to idle CPUs, which is critically important both to battery-powered devices and to highly virtualized mainframes.
Therefore, system with aggressive real-time response constraints often run CONFIG_HZ_PERIODIC=y kernels(or CONFIG_NO_HZ=n) in order to avoid degrading from-idle transition latencies.
This boot parameter "nohz=" that can be used to disable dyntick-idle mode in CONFIG_NO_HZ_IDLE=y kernel by specifying "nohz=off". By the default, the system boot with "nohz=on", enabling dyntick-idle mode.
Have a great day,
Yiping
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------