Why do the default images in the QorIQ Linux SDK v2.0 PPCE5500 IMAGE.iso result in a "init[1]: unhandled signal 4" when run on a T1040 with qemu-system-ppc64 (and on a CentOS qemu on x86)?

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

Why do the default images in the QorIQ Linux SDK v2.0 PPCE5500 IMAGE.iso result in a "init[1]: unhandled signal 4" when run on a T1040 with qemu-system-ppc64 (and on a CentOS qemu on x86)?

1,401 Views
timtenhave
Contributor I

I took the default T1040 and T1042 uImage and ext2 rootfs from the "QorIQ Linux SDK v2.0 PPCE5500 IMAGE.iso" and tried to run them in a CentOS X86 qemu session and on my eval T1040 board.  Both result in an init failure when starting the init process.  See latest attempt on the T1040:


t1040d4rdb:~/CXM$ qemu-system-ppc64 -kernel uImage-t1040d4rdb.bin -cpu e5500 -M ppce500 -no-reboot -show-cursor -m 1024 -initrd fsl-image-core-t1040d4rdb-20160514203035.rootfs.ext2.gz -nographic -append "root=/dev/ram rw mem=1024M"
Using QEMU e500 machine description
Memory CAM mapping: 256/256/256 Mb, residual: 256Mb
Linux version 4.1.8-rt8+gbd51baf (jenkins@neptune) (gcc version 4.9.2 (GCC) ) #1 SMP Sun May 15 04:13:24 CST 2016
Found initrd at 0xc4000000:0xc5dfc6b0
CPU maps initialized for 1 thread per core
bootconsole [udbg0] enabled
setup_arch: initmem
qemu_e500_setup_arch()
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 @ef7df000 s19148 r8192 d21812 u49152
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260608
Kernel command line: root=/dev/ram rw mem=1024M
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: 932416K/1048576K available (7220K kernel code, 300K rwdata, 2016K rodata, 324K init, 458K bss, 116160K reserved, 0K cma-reserved, 262144K highmem)
Kernel virtual memory layout:
  * 0xfff5f000..0xfffff000  : fixmap
  * 0xffc00000..0xffe00000  : highmem PTEs
  * 0xffbfe000..0xffc00000  : early ioremap
  * 0xf1000000..0xffbfe000  : 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=1.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS:512 nr_irqs:512 16
mpic: Setting up MPIC " OpenPIC  " version 1.2 at fe0040000, max 1 CPUs
mpic: ISU size: 256, shift: 8, mask: ff
mpic: Initializing for 256 sources
clocksource timebase: mask: 0xffffffffffffffff max_cycles: 0x5c4093a7d1, max_idle_ns: 440795210635 ns
clocksource: timebase mult[2800000] 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 1 CPUs
devtmpfs: initialized
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
NET: Registered protocol family 16

Found FSL PCI host bridge at 0x0000000fe0008000. Firmware bus number: 0->255
PCI host bridge /pci@fe0008000 (primary) ranges:
 MEM 0x0000000c00000000..0x0000000c1fffffff -> 0x00000000e0000000
  IO 0x0000000fe1000000..0x0000000fe100ffff -> 0x0000000000000000
/pci@fe0008000: PCICSRBAR @ 0xdff00000
setup_pci_atmu: end of DRAM 40000000
EDAC PCI0: Giving out device to module MPC85xx_edac controller mpc85xx_pci_err: DEV fe0008000.pci (INTERRUPT)
MPC85xx_edac acquired irq 24 for PCI Err
MPC85xx_edac PCI err registered
fsl-pamu: fsl_pamu_init: could not find a PAMU node
PCI: Probing PCI hardware
fsl-pci fe0008000.pci: PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  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 PCI bridge 1, will remap
PCI: Cannot allocate resource region 0 of device 0000:00:00.0, will remap
pci 0000:00:00.0: BAR 0: assigned [mem 0xc00000000-0xc000fffff]
pci 0000:00:00.0: BAR 8: assigned [mem 0xc00100000-0xc001fffff]
pci 0000:00:01.0: BAR 6: assigned [mem 0xc00200000-0xc0023ffff pref]
pci 0000:00:01.0: BAR 1: assigned [mem 0xc00240000-0xc00240fff]
pci 0000:00:01.0: BAR 0: assigned [io  0x1000-0x101f]
pci 0000:00:00.0: PCI bridge to [bus 01]
pci 0000:00:00.0:   bridge window [mem 0xc00100000-0xc001fffff]
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
No BMan portals available!
No QMan portals available!
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: 30704K (c4000000 - c5dfc000)
futex hash table entries: 256 (order: 2, 16384 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(3.636: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)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
console [ttyS0] disabled
serial8250.0: ttyS0 at MMIO 0xfe0004500 (irq = 42, base_baud = 115200) is a 16550A
console [ttyS0] enabled
console [ttyS0] enabled
bootconsole [udbg0] disabled
bootconsole [udbg0] disabled
ePAPR hypervisor byte channel driver
Generic non-volatile memory driver v1.1
brd: module loaded
loop: module loaded
st: Version 20101219, fixed bufsize 32768, s/g segs 256
libphy: Fixed MDIO Bus: probed
Freescale FM module, FMD API version 21.1.0
Freescale FM Ports module
fsl_mac: fsl_mac: FSL FMan MAC API based driver
fsl_dpa: FSL DPAA Ethernet driver
fsl_advanced: FSL DPAA Advanced drivers:
fsl_proxy: FSL DPAA Proxy initialization driver
fsl_dpa_shared: FSL DPAA Shared Ethernet driver
fsl_dpa_macless: FSL DPAA MACless Ethernet driver
fsl_oh: FSL FMan Offline Parsing port driver
e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
usbcore: registered new interface driver usb-storage
i2c /dev entries driver
Freescale(R) MPC85xx EDAC driver, (C) 2006 Montavista Software
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
No fsl,qman node
Freescale USDPAA process driver
fsl-usdpaa: no region found
Freescale USDPAA process IRQ driver
Freescale pme2 db driver
PME2: fsl_pme2_db_init: not on ctrl-plane
Freescale pme2 scan driver
fsl-pme2-scan: device pme_scan registered
Freescale hypervisor management driver
fsl-hv: no hypervisor found
ipip: IPv4 over IPv4 tunneling driver
Initializing XFRM netlink socket
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
fsl_generic: FSL DPAA Generic Ethernet driver
hctosys: unable to open rtc device (rtc0)
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 324K (c0909000 - c095a000)
init[1]: unhandled signal 4 at b78f766c nip b78f766c lr b78f2c98 code 30001
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

CPU: 0 PID: 1 Comm: init Not tainted 4.1.8-rt8+gbd51baf #1
Call Trace:
[ea03fd60] [c0706328] dump_stack+0x78/0xa0 (unreliable)
[ea03fd70] [c0704318] panic+0xd8/0x22c
[ea03fdd0] [c002ffec] do_exit+0x90c/0x910
[ea03fe10] [c0030f18] do_group_exit+0x48/0xb0
[ea03fe30] [c003cd14] get_signal+0x264/0x540
[ea03fe80] [c0007254] do_signal+0x34/0x1c0
[ea03ff30] [c00074c8] do_notify_resume+0x68/0x80
[ea03ff40] [c000fdbc] do_user_signal+0x74/0xc4
--- interrupt: 700 at 0xb78f766c
    LR = 0xb78f2c98
Rebooting in 180 seconds..t1040d4rdb:

0 Kudos
3 Replies

75 Views
LovejeetSingh
Contributor I

Hi @timtenhave 

We are trying to boot uImage with qemu-system-ppc64 on Ubuntu x86_64 and facing the same issue:

 

init[1]: unhandled signal 4 at b7a3766c **bleep** b7a3766c lr b7a32c98 code 30001
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

CPU: 0 PID: 1 Comm: init Not tainted 4.1.8-rt8+gbd51baf #1
Call Trace:
[ea03fd60] [c0706328] dump_stack+0x78/0xa0 (unreliable)
[ea03fd70] [c0704318] panic+0xd8/0x22c
[ea03fdd0] [c002ffec] do_exit+0x90c/0x910
[ea03fe10] [c0030f18] do_group_exit+0x48/0xb0
[ea03fe30] [c003cd14] get_signal+0x264/0x540
[ea03fe80] [c0007254] do_signal+0x34/0x1c0
[ea03ff30] [c00074c8] do_notify_resume+0x68/0x80
[ea03ff40] [c000fdbc] do_user_signal+0x74/0xc4
--- interrupt: 700 at 0xb7a3766c
    LR = 0xb7a32c98
Rebooting in 180 seconds..

 

 

I am writing to confirm whether you are able to boot on centOS qemu and what exactly was causing the issue ? 

0 Kudos

864 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Tim Tenhave,

I have verified KVM/QEMU setting up procedure on T1040D4RDB board, there is no problem. Please refer to my procedure.

First please configure Linux Kernel with the following Kernel options enabled and rebuild uImage.

1.Enabling KVM
[*] Virtualization --->
    [*] KVM support for PowerPC E500MC/E5500/E6500 processors
    [*] KVM in-kernel MPIC emulation

Then on T1040RDB board, please boot up Linux with uImage mentioned above and execute the following command.

root@t1040d4rdb:~# qemu-system-ppc64 -enable-kvm -nographic -m 1024 -cpu e5500 -M ppce500 -kernel uImage -initrd fsl-image-core-t1040d4rdb-20160514203035.rootfs.ext2.gz  -append "root=/dev/ram rw console=ttyS0,115200"  -serial tcp::4444,server
QEMU 2.4.0 monitor - type 'help' for more information
(qemu) QEMU waiting for connection on: disconnected:tcp::4444,server

On the PC, please access guest with the following command.

$ telnet 192.168.2.102 4444


Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

864 Views
timtenhave
Contributor I

Thank you for the tip!  I will give this a try over the next few days as I am sharing the T1040 board right now.

Tim

0 Kudos