"init[1]: unhandled signal 11" error while booting Linux for QorIQ P3041 Processor

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

"init[1]: unhandled signal 11" error while booting Linux for QorIQ P3041 Processor

Jump to solution
3,282 Views
DemirYumruk
Contributor I

Hi,

I'm using QorIQ SDK v2.0-1703 on Ubuntu 14.04. I compiled kernel and fsl-image-core adhering to the SDK documentation. But I am getting the error mentioned in the title. Can you tell me what I did wrong?

U-boot:

ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,115200 ramdisk_size=10000000 log_buf_len=128K;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskaddr $fdtaddr

Boot log:

=> run ramboot
Using FM1@DTSEC3 device
TFTP from server
Filename 'deneme/fsl-image-core-p3041ds-20210526113014.rootfs.ext2.gz.u-boot'.
Load address: 0x5000000
Loading: #################################################################
################
5.9 MiB/s
done
Bytes transferred = 46027992 (2be54d8 hex)
Using FM1@DTSEC3 device
TFTP from server
Filename 'deneme/uImage--4.1-r0-p3041ds-20210526112624.bin'.
Load address: 0x1000000
Loading: #################################################################
######################################################
5.8 MiB/s
done
Bytes transferred = 4600148 (463154 hex)
Using FM1@DTSEC3 device
TFTP from server
Filename 'deneme/uImage--4.1-r0-p3041ds-20210526112624.dtb'.
Load address: 0x2000000
Loading: ###
4.2 MiB/s
done
Bytes transferred = 35066 (88fa hex)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-4.1.35-rt41
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 4600084 Bytes = 4.4 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 05000000 ...
Image Name: fsl-image-core-p3041ds-202105261
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 46027928 Bytes = 43.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
Uncompressing Kernel Image ... OK
Loading Ramdisk to 2d41a000, end 2ffff498 ... OK
Loading Device Tree to 03fe4000, end 03fff8f9 ... OK
Reserved memory: initialized node bman-fbpr, compatible id fsl,bman-fbpr
Reserved memory: initialized node qman-fqd, compatible id fsl,qman-fqd
Reserved memory: initialized node qman-pfdr, compatible id fsl,qman-pfdr
Using CoreNet Generic machine description
Memory CAM mapping: 256/256/256 Mb, residual: 256Mb
Linux version 4.1.35-rt41 (freescale@freescale-qoriq) (gcc version 4.9.2 (GCC) ) #1 SMP Thu Apr 8 17:19:30 +03 2021
Found initrd at 0xed41a000:0xeffff498
CPU maps initialized for 1 thread per core
bootconsole [udbg0] enabled
setup_arch: initmem
CoreNet Generic board
arch: exit
Zone ranges:
DMA [mem 0x0000000000000000-0x000000002fffffff]
Normal empty
HighMem [mem 0x0000000030000000-0x000000003fffffff]
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x0000000000000000-0x000000003fffffff]
Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
MMU: Allocated 1088 bytes of context maps for 255 contexts
PERCPU: Embedded 12 pages/cpu @ecb9f000 s19148 r8192 d21812 u49152
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
Kernel command line: root=/dev/ram rw console=ttyS0,115200 ramdisk_size=10000000 log_buf_len=128K
log_buf_len: 131072 bytes
early log buf free: 13620(83%)
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: 860384K/1048576K available (7144K kernel code, 308K rwdata, 2056K rodata, 300K init, 458K bss, 188192K reserved, 0K cma-reserved, 204792K highmem)
Kernel virtual memory layout:
* 0xfff5f000..0xfffff000 : fixmap
* 0xffc00000..0xffe00000 : highmem PTEs
* 0xffbfd000..0xffc00000 : early ioremap
* 0xf1000000..0xffbfd000 : vmalloc & ioremap
Hierarchical RCU implementation.
RCU debugfs-based tracing is enabled.
Additional per-CPU info printed with stalls.
RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
NR_IRQS:512 nr_irqs:512 16
mpic: Setting up MPIC " OpenPIC " version 1.2 at ffe040000, max 4 CPUs
mpic: ISU size: 512, shift: 9, mask: 1ff
mpic: Initializing for 512 sources
clocksource timebase: mask: 0xffffffffffffffff max_cycles: 0x50b88126c, max_idle_ns: 440795202180 ns
clocksource: timebase mult[2db6db6e] shift[24] registered
Console: colour dummy device 80x25
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
e500 family performance monitor hardware support registered
Brought up 4 CPUs
devtmpfs: initialized
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
NET: Registered protocol family 16
Bman ver:0a02,01,00
qman-fqd addr 0x000000003f000000 size 0x800000
qman-pfdr addr 0x000000003c000000 size 0x2000000
Qman ver:0a01,01,02,00

Machine: fsl,P3041DS
SoC family: QorIQ
SoC ID: svr:0x82110320, Revision: 2.0
Found FSL PCI host bridge at 0x0000000ffe200000. Firmware bus number: 0->0
PCI host bridge /pcie@ffe200000 ranges:
MEM 0x0000000c00000000..0x0000000c1fffffff -> 0x00000000e0000000
IO 0x0000000ff8000000..0x0000000ff800ffff -> 0x0000000000000000
/pcie@ffe200000: PCICSRBAR @ 0xdf000000
setup_pci_atmu: end of DRAM 40000000
EDAC PCI0: Giving out device to module MPC85xx_edac controller mpc85xx_pci_err: DEV ffe200000.pcie (INTERRUPT)
MPC85xx_edac acquired irq 482 for PCI Err
MPC85xx_edac PCI err registered
PCI: Probing PCI hardware
fsl-pci ffe200000.pcie: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io 0xf1040000-0xf104ffff] (bus address [0x0000-0xffff])
pci_bus 0000:00: root bus resource [mem 0xc00000000-0xc1fffffff] (bus address [0xe0000000-0xffffffff])
pci_bus 0000:00: root bus resource [bus 00-ff]
pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
PCI: Cannot allocate resource region 0 of device 0000:00:00.0, will remap
pci 0000:00:00.0: BAR 0: no space for [mem size 0x01000000]
pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x01000000]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0: bridge window [io 0xf1040000-0xf104ffff]
pci 0000:00:00.0: bridge window [mem 0xc00000000-0xc1fffffff]
pci_bus 0000:00: Some PCI device resources are unassigned, try booting with pci=realloc
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
EDAC MC: Ver: 3.0.0
bman-fbpr addr 0x000000003e000000 size 0x1000000
Bman err interrupt handler present
Bman portal initialised, cpu 0
Bman portal initialised, cpu 1
Bman portal initialised, cpu 2
Bman portal initialised, cpu 3
Bman portals initialised
Qman err interrupt handler present
Qman portal initialised, cpu 0
Qman portal initialised, cpu 1
Qman portal initialised, cpu 2
Qman portal initialised, cpu 3
Qman portals initialised
Bman: BPID allocator includes range 32:32
Qman: FQID allocator includes range 256:256
Qman: FQID allocator includes range 32768:32768
Qman: CGRID allocator includes range 0:256
Qman: pool channel allocator includes range 33:15
No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
Switched to clocksource timebase
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
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.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 44948K (ed41a000 - effff000)
futex hash table entries: 1024 (order: 4, 65536 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(0.556:1): initialized
HugeTLB registered 4 MB page size, pre-allocated 0 pages
HugeTLB registered 16 MB page size, pre-allocated 0 pages
HugeTLB registered 64 MB page size, pre-allocated 0 pages
HugeTLB registered 256 MB page size, pre-allocated 0 pages
HugeTLB registered 1 GB page size, pre-allocated 0 pages
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
ntfs: driver 2.1.32 [Flags: R/O].
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
bounce: pool size: 64 pages
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
console [ttyS0] disabled
ÿRAMDISK: gzip image found at block 000 (irq = 36, base_baud = 21875000) is a 16550A
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 300K (c08ff000 - c094a000)
init[1]: unhandled signal 11 at b7cd29b0 **bleep** b7cd29b0 lr 00000000 code 30001

0 Kudos
1 Solution
3,276 Views
yipingwang
NXP TechSupport
NXP TechSupport

I downloaded SDK 2.0 1703, built uImage, dtb and rootfs filesystem, I verified them on my P3041DS board and uploaded them to the following link.

https://drive.google.com/file/d/1-7lDfVaADTj__BY3pWoXpzK7BS7HOT1V/view?usp=sharing

It seems that there is problem with your rootfs filesystem, please try whether my images can work on your target board. They work normally on my P3041DS.

View solution in original post

0 Kudos
4 Replies
3,273 Views
DemirYumruk
Contributor I

Hi yipingwang,

I am able to successfully boot my own card with the files you provided. Did you make any changes to the kernel, recipes, device tree, u-boot arguments etc. other than the default configuration?

Thank you,

DemirYumruk

0 Kudos
3,255 Views
yipingwang
NXP TechSupport
NXP TechSupport

I didn't change anything just use the default configuration, please create a new build project to rebuild the rootfs filesystem.

0 Kudos
3,241 Views
DemirYumruk
Contributor I

Hi,

I realized that I was getting this error because of a change I made in the image recipe. Thank you for your interest.

0 Kudos
3,277 Views
yipingwang
NXP TechSupport
NXP TechSupport

I downloaded SDK 2.0 1703, built uImage, dtb and rootfs filesystem, I verified them on my P3041DS board and uploaded them to the following link.

https://drive.google.com/file/d/1-7lDfVaADTj__BY3pWoXpzK7BS7HOT1V/view?usp=sharing

It seems that there is problem with your rootfs filesystem, please try whether my images can work on your target board. They work normally on my P3041DS.

0 Kudos