Kernel panic - not syncing: Attempted to kill init! on t1042 based board

chandrashekhar · ‎07-23-2014

Hi Team,

We are booting linux kernel on our customised T1042 based board. We are seeing kernel crash at initialization. below is the log message,

bootm 0x3000000 0x7000000 0x5000000
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 03000000 ...
   Image Name:   Linux-3.8.13-rt9-QorIQ-SDK-T1040
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    4118920 Bytes = 3.9 MiB
   Load Address: 00000000
   Entry Point: 00000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 07000000 ...
   Image Name:   fsl-image-core-t1042rdb-20140625
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    26491645 Bytes = 25.3 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

image_setup_linux
Loading Ramdisk to 2e6bc000, end 2ffffafd ... OK
Loading Device Tree to 03fe2000, end 03ffef5a ... OK

SPAG : ft_cpu_setup, 642
Single Source Clock Configuration

fdt_portal,96, addr : 0xfffffff3

fdt_portal,96, addr : 0xfffffff3
Warning: MAC address for l2switch not found
Using T104x RDB machine description
Memory CAM mapping: 256/256/256 Mb, residual: 3328Mb
Linux version 3.8.13-rt9-QorIQ-SDK-T1040-BSP0.2 (asr907@asr907-ThinkStation-S20) (gcc version 4.7.3 (GCC) ) #1 SMP Thu Jun 26 03:41:01 IST 2014
Found initrd at 0xee6bc000:0xeffffafd
No /soc@ffb000000/qman@318000 property 'fsl,qman-fqd', using memblock_alloc(0000000000400000)
No /soc@ffb000000/qman@318000 property 'fsl,qman-pfdr', using memblock_alloc(0000000002000000)
Qman ver:0a01,03,01
No /soc@ffb000000/bman@31a000 property 'fsl,bman-fbpr', using memblock_alloc(0000000001000000)
Bman ver:0a02,02,01
pme: No /soc@ffb000000/pme@316000 property 'fsl,pme-pdsr', using memblock_alloc(0x0000000001000000)
pme: No /soc@ffb000000/pme@316000 property 'fsl,pme-sre', using memblock_alloc(0x0000000000a00000)
No USDPAA memory, no 'usdpaa_mem' bootarg
CPU maps initialized for 1 thread per core
bootconsole [udbg0] enabled
setup_arch: bootmem
Freescale RCPM driver
T104x RDB board from Freescale Semiconductor
arch: exit
Zone ranges:
DMA      [mem 0x00000000-0x2fffffff]
Normal   empty
HighMem [mem 0x30000000-0xffffffff]
Movable zone start for each node
Early memory node ranges
node   0: [mem 0x00000000-0xffffffff]
MMU: Allocated 1088 bytes of context maps for 255 contexts
PERCPU: Embedded 8 pages/cpu @c2913000 s9024 r8192 d15552 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1040384
Kernel command line: ${bootargs} root /dev/ram0 rw console=ttyS0,9600
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: 3979328k/4194304k available (8464k kernel code, 214976k reserved, 316k data, 431k bss, 268k init)
Kernel virtual memory layout:
* 0xfff5f000..0xfffff000 : fixmap
* 0xffc00000..0xffe00000 : highmem PTEs
* 0xffbfa000..0xffc00000 : early ioremap
* 0xf1000000..0xffbfa000 : vmalloc & ioremap
Hierarchical RCU implementation.
        RCU debugfs-based tracing is enabled.
        RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
NR_IRQS:512 nr_irqs:512 16
mpic: Setting up MPIC " OpenPIC " version 1.2 at ffb040000, max 4 CPUs
mpic: ISU size: 512, shift: 9, mask: 1ff
mpic: Initializing for 512 sources
clocksource: timebase mult[10000000] shift[23] registered
Console: colour dummy device 80x25
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
mpic: requesting IPIs...
e500 family performance monitor hardware support registered
smp_85xx_kick_cpu: timeout waiting for core 1 to ack
smp: failed starting cpu 1 (rc -2)
smp_85xx_kick_cpu: timeout waiting for core 2 to ack
smp: failed starting cpu 2 (rc -2)
smp_85xx_kick_cpu: timeout waiting for core 3 to ack
smp: failed starting cpu 3 (rc -2)
Brought up 1 CPUs
devtmpfs: initialized
NET: Registered protocol family 16

Found FSL PCI host bridge at 0x0000000ffb240000. Firmware bus number: 0->0
PCI host bridge /pcie@ffb240000 (primary) ranges:
MEM 0x0000000c00000000..0x0000000c0fffffff -> 0x00000000e0000000
IO 0x0000000ff8000000..0x0000000ff800ffff -> 0x0000000000000000
/pcie@ffb240000: PCICSRBAR @ 0xff000000
/pcie@ffb240000: Setup 64-bit PCI DMA window
/pcie@ffb240000: WARNING: Outbound window cfg leaves gaps in memory map. Adjusting the memory map could reduce unnecessary bounce buffering.
/pcie@ffb240000: DMA window size is 0xe0000000
EDAC PCI0: Giving out device to module 'MPC85xx_edac' controller 'mpc85xx_pci_err': DEV 'ffb240000.pcie' (INTERRUPT)
MPC85xx_edac acquired irq 20 for PCI Err
MPC85xx_edac PCI err registered
Found FSL PCI host bridge at 0x0000000ffb250000. Firmware bus number: 0->9
PCI host bridge /pcie@ffb250000 ranges:
MEM 0x0000000c10000000..0x0000000c1fffffff -> 0x00000000e0000000
IO 0x0000000ff8010000..0x0000000ff801ffff -> 0x0000000000000000
/pcie@ffb250000: PCICSRBAR @ 0xff000000
/pcie@ffb250000: Setup 64-bit PCI DMA window
/pcie@ffb250000: WARNING: Outbound window cfg leaves gaps in memory map. Adjusting the memory map could reduce unnecessary bounce buffering.
/pcie@ffb250000: DMA window size is 0xe0000000
EDAC PCI1: Giving out device to module 'MPC85xx_edac' controller 'mpc85xx_pci_err': DEV 'ffb250000.pcie' (INTERRUPT)
MPC85xx_edac acquired irq 21 for PCI Err
MPC85xx_edac PCI err registered
Found FSL PCI host bridge at 0x0000000ffb260000. Firmware bus number: 0->0
PCI host bridge /pcie@ffb260000 ranges:
MEM 0x0000000c20000000..0x0000000c2fffffff -> 0x00000000e0000000
IO 0x0000000ff8020000..0x0000000ff802ffff -> 0x0000000000000000
/pcie@ffb260000: PCICSRBAR @ 0xff000000
/pcie@ffb260000: Setup 64-bit PCI DMA window
/pcie@ffb260000: WARNING: Outbound window cfg leaves gaps in memory map. Adjusting the memory map could reduce unnecessary bounce buffering.
/pcie@ffb260000: DMA window size is 0xe0000000
EDAC PCI2: Giving out device to module 'MPC85xx_edac' controller 'mpc85xx_pci_err': DEV 'ffb260000.pcie' (INTERRUPT)
MPC85xx_edac acquired irq 22 for PCI Err
MPC85xx_edac PCI err registered
Found FSL PCI host bridge at 0x0000000ffb270000. Firmware bus number: 0->0
PCI host bridge /pcie@ffb270000 ranges:
MEM 0x0000000c30000000..0x0000000c3fffffff -> 0x00000000e0000000
IO 0x0000000ff8030000..0x0000000ff803ffff -> 0x0000000000000000
/pcie@ffb270000: PCICSRBAR @ 0xff000000
/pcie@ffb270000: Setup 64-bit PCI DMA window
/pcie@ffb270000: WARNING: Outbound window cfg leaves gaps in memory map. Adjusting the memory map could reduce unnecessary bounce buffering.
/pcie@ffb270000: DMA window size is 0xe0000000
EDAC PCI3: Giving out device to module 'MPC85xx_edac' controller 'mpc85xx_pci_err': DEV 'ffb270000.pcie' (INTERRUPT)
MPC85xx_edac acquired irq 23 for PCI Err
MPC85xx_edac PCI err registered
software IO TLB [mem 0x03ff4000-0x07ff4000] (64MB) mapped at [c3ff4000-c7ff3fff]
PCI: Probing PCI hardware
fsl-pci ffb240000.pcie: 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-0xc0fffffff] (bus address [0xe0000000-0xefffffff])
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]
fsl-pci ffb250000.pcie: PCI host bridge to bus 0001:02
pci_bus 0001:02: root bus resource [io 0x60000-0x6ffff] (bus address [0x0000-0xffff])
pci_bus 0001:02: root bus resource [mem 0xc10000000-0xc1fffffff] (bus address [0xe0000000-0xefffffff])
pci_bus 0001:02: root bus resource [bus 02-ff]

.

after some more messages

.

bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
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:512
Qman: FQID allocator includes range 32768:32768
Qman: CGRID allocator includes range 0:256
Qman: pool channel allocator includes range 1025:15
Switching to clocksource timebase
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
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.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 25872k freed
fsl-ifc ffb124000.localbus: Freescale Integrated Flash Controller
audit: initializing netlink socket (disabled)
type=2000 audit(1.724:1): initialized
bounce pool size: 64 pages
HugeTLB registered 1 MB page size, pre-allocated 0 pages
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
Machine check in kernel mode.
Caused by (from MCSR=8000): Load Error Report
Oops: Machine check, sig: 7 [#1]
SMP NR_CPUS=8 T104x RDB
Modules linked in:
NIP: c024b950 LR: c01802d8 CTR: 00000000
REGS: ee6a7f10 TRAP: 0204 Not tainted (3.8.13-rt9-QorIQ-SDK-T1040-BSP0.2)
MSR: 00029002 <CE,EE,ME> CR: 84000048 XER: 00000000
TASK = e80669b0[1] 'swapper/0' THREAD: e8076000 CPU: 0
GPR00: c01802b8 e8077ea0 e80669b0 00000000 0000000f e8007fb8 e80b1340 00000001
GPR08: f11ed52c f11ed000 00000000 c08809c0 44000022 00000000 c0002670 00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000000dd
GPR24: c0890000 c0890000 00000000 c0816bbc e8076000 c08b0000 00000000 c08b2c7c
NIP [c024b950] zlib_inflateReset+0x40/0x90
LR [c01802d8] cramfs_uncompress_init+0x78/0xa0
Call Trace:
[e8077ea0] [c01802b8] cramfs_uncompress_init+0x58/0xa0 (unreliable)
[e8077ec0] [c0816bcc] init_cramfs_fs+0x10/0x4c
[e8077ed0] [c00020a8] do_one_initcall+0x148/0x1b0
[e8077f00] [c08018e8] kernel_init_freeable+0x12c/0x1e4
[e8077f30] [c0002684] kernel_init+0x14/0x110
[e8077f40] [c000f648] ret_from_kernel_thread+0x64/0x6c
Instruction dump:
41de0070 39400000 38e00001 9149001c 3909052c 90e30028 91430014 91430008
91430018 38600000 91490000 91490004 <80c90020> 9149000c 91490034 7ce73030
---[ end trace 47406ac656220eeb ]---

Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007

Rebooting in 180 seconds..

Are we missing some configuration/parameter passing from u-boot? On further debug found that it is crashing while executing below statement from "lib/zlib_inflate/inflate.c"

state->wsize = 1U << state->wbits;

Any suggestions for the above failure?

Regards,

Chandra

scottwood · ‎07-24-2014

First, double and triple check your DDR configuration. You might be using timings or other settings that are close enough to mostly work, but occasionally fail. Also make sure that the DDR itself is good.

Do you see any errors reported in the DDR registers? If no, check other error registers such as CPC.

If none of that helps, add code to the machine check handler to look up the TLB entry being accessed. I notice that in both machine checks, it appears to be an access from an address >= 0xf0000000, which is the vmalloc/ioremap/kmap area. Assuming this is due to kmap, limiting memory to <= 768 MiB can make it easier to spot the physical address being accessed without needing to do a TLB search.

View solution in original post

scottwood · ‎07-24-2014

First, double and triple check your DDR configuration. You might be using timings or other settings that are close enough to mostly work, but occasionally fail. Also make sure that the DDR itself is good.

Do you see any errors reported in the DDR registers? If no, check other error registers such as CPC.

If none of that helps, add code to the machine check handler to look up the TLB entry being accessed. I notice that in both machine checks, it appears to be an access from an address >= 0xf0000000, which is the vmalloc/ioremap/kmap area. Assuming this is due to kmap, limiting memory to <= 768 MiB can make it easier to spot the physical address being accessed without needing to do a TLB search.

chandrashekhar · ‎07-24-2014

Thanks Scott,

Yes, u-boot were passing the size of memory to linux kernel for which TLB was not created. After passing the correct memsize we could resolve this issue.

-Chandra

scottwood · ‎07-24-2014

I don't follow -- the suggestion to limit the memory size was just a debugging aid, to get non-kmap effective addresses. If there were truly no TLB entry, you would have gotten a TLB miss, not a machine check.

It's probably just coincidence that you don't see the issue when not using all of the memory (e.g. maybe the RAM is bad at a specific address).

chandrashekhar · ‎07-24-2014

After masking "state-wsize = 1U<< state->wbits" boot up moves further but fails on initrd_load. below is the log message,

NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
NTFS driver 2.1.30 [Flags: R/O].
jffs2: version 2.2. (NAND) 2001-2006 Red Hat, Inc.
msgmni has been set to 1166
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0xffb11c500 (irq = 36) is a 16550A_FSL64
console [ttyS0] enabled, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
serial8250.0: ttyS1 at MMIO 0xffb11c600 (irq = 36) is a 16550A_FSL64
serial8250.0: ttyS2 at MMIO 0xffb11d500 (irq = 37) is a 16550A_FSL64
serial8250.0: ttyS3 at MMIO 0xffb11d600 (irq = 37) is a 16550A_FSL64
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
fe8000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00227e
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
fsl_espi ffb110000.spi: master is unqueued, this is deprecated
m25p80 spi32766.0: unrecognized JEDEC id ffffff
fsl_espi ffb110000.spi: at 0xf111e000 (irq = 53)
libphy: Fixed MDIO Bus: probed
libphy: Freescale XGMAC MDIO Bus: probed
Freescale FM module (Jun 26 2014:22:25:53), FMD API version 21.1.0
Freescale FM Ports module (Jun 26 2014:22:25:55)
dpaa_debugfs: FSL DPAA Ethernet debugfs entries ()
fsl_mac: fsl_mac: FSL FMan MAC API based driver ()
fsl_mac ffb4e0000.ethernet: FMan MEMAC
fsl_mac ffb4e0000.ethernet: FMan MAC address: 00:04:9f:03:05:e4
fsl_mac ffb4e2000.ethernet: FMan MEMAC
fsl_mac ffb4e2000.ethernet: FMan MAC address: 00:04:9f:03:05:e5
fsl_mac ffb4e4000.ethernet: FMan MEMAC
fsl_mac ffb4e4000.ethernet: FMan MAC address: 00:00:04:9f:03:05
fsl_mac ffb4e6000.ethernet: FMan MEMAC
fsl_mac ffb4e6000.ethernet: FMan MAC address: 00:04:9f:03:05:e7
fsl_dpa: FSL DPAA Ethernet driver ()
fsl_dpa: fsl_dpa: Probed interface eth0
fsl_dpa: fsl_dpa: Probed interface eth1
fsl_dpa: fsl_dpa: Probed interface eth2
fsl_dpa: fsl_dpa: Probed interface eth3
fsl_dpa_shared: FSL DPAA Shared Ethernet driver ()
fsl_dpa_proxy: FSL DPAA Proxy initialization 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.1.4-k
e1000e: Copyright(c) 1999 - 2012 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
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 44, io mem 0xffb210000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 45, io mem 0xffb211000
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
i2c /dev entries driver
mpc-i2c ffb118100.i2c: timeout 1000000 us
usb 1-1: new high-speed USB device number 2 using fsl-ehci
mpc-i2c ffb118000.i2c: timeout 1000000 us
mpc-i2c ffb119000.i2c: timeout 1000000 us
mpc-i2c ffb119100.i2c: timeout 1000000 us
EDAC MC: Ver: 3.0.0
Freescale(R) MPC85xx EDAC driver, (C) 2006 Montavista Software
EDAC MC0: Giving out device to 'MPC85xx_edac' 'mpc85xx_mc_err': DEV mpc85xx_mc_err
MPC85xx_edac acquired irq 490 for MC
MPC85xx_edac MC err registered
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
platform caam_qi.0: Linux CAAM Queue I/F driver initialised
caam ffb300000.crypto: Instantiated RNG4 SH0
caam ffb300000.crypto: Instantiated RNG4 SH1
caam ffb300000.crypto: device ID = 0x0a12040000000000 (Era 6)
caam ffb300000.crypto: job rings = 4, qi = 1
caam algorithms registered in /proc/crypto
caam_jr ffb301000.jr: registering rng-caam
scsi0 : usb-storage 1-1:1.0
platform caam_qi.0: fsl,sec-v5.0 algorithms registered in /proc/crypto
fsl,sec-v5.0 algorithms registered in /proc/crypto
Freescale USDPAA process driver
fsl-usdpaa: no region found
usb 2-1: new high-speed USB device number 2 using fsl-ehci
Freescale USDPAA process IRQ driver
fsl-pme ffb316000.pme: ver: 0x00100202
Freescale pme2 db driver
Freescale pme2 scan driver
fsl-pme2-scan: device pme_scan registered
Freescale hypervisor management driver
fsl-hv: no hypervisor found
IPv4 over IPv4 tunneling driver
TCP: cubic registered
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_dpa_macless: FSL DPAA MACless Ethernet driver ()
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Machine check in kernel mode.
Caused by (from MCSR=8000): Load Error Report
Oops: Machine check, sig: 7 [#1]
SMP NR_CPUS=8 T104x RDB
Modules linked in:
NIP: c0019888 LR: c00a4d04 CTR: 00000004
REGS: ee6b1f10 TRAP: 0204 Not tainted (3.8.13-rt9-QorIQ-SDK-T1040-BSP0.2)
MSR: 00029002 <CE,EE,ME> CR: 44000082 XER: 20000000
TASK = e80659b0[1] 'swapper/0' THREAD: e8076000 CPU: 0
GPR00: 00000004 e8077cf0 e80659b0 00000104 fffdeffc 00000000 e863a9fc 00000004
GPR08: 00000004 00000000 00029002 00000004 22000028 00000000 00000000 00001000
GPR16: c28c1000 00000001 00000fff 00000000 e83fd910 e700d6d0 00000000 00000000
GPR24: e8077e48 e83fd8c0 00000000 fffdf000 00000200 c28c1000 00000200 e8077d28
NIP [c0019888] __copy_tofrom_user+0xac/0x2a4
LR [c00a4d04] file_read_actor+0x174/0x210
Call Trace:
[e8077cf0] [c00a4cf0] file_read_actor+0x160/0x210 (unreliable)
[e8077d20] [c00a7088] generic_file_aio_read+0x348/0x7d0
[e8077dc0] [c00e8848] do_sync_read+0xe8/0x170
[e8077e60] [c00e9370] vfs_read+0xb0/0x1a0
[e8077e80] [c00e94ac] sys_read+0x4c/0xb0
[e8077eb0] [c0803440] rd_load_image+0xc0/0x614
[e8077f00] [c0803aac] initrd_load+0x50/0x2bc
[e8077f20] [c08030f0] prepare_namespace+0xec/0x1e8
[e8077f30] [c0002684] kernel_init+0x14/0x110
[e8077f40] [c000f648] ret_from_kernel_thread+0x64/0x6c
Instruction dump:
2c000004 40810008 38e00004 7ce903a6 7c03222c 38630040 4200fff8 7d070050
7ce03b78 7d0903a6 7c03222c 7c0b37ec <80e40004> 81040008 8124000c 85440010
---[ end trace bddb8bbc1e1bd7a6 ]---

note: swapper/0[1] exited with preempt_count 1
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007

Rebooting in 180 seconds..

-Chandra

yipingwang · ‎07-24-2014

Hello Chandra,

According to your boot log, the following Kernel command line looks abnormal.

Kernel command line: ${bootargs} root /dev/ram0 rw console=ttyS0,9600

Please specify the bootargs as the following in u-boot.

setenv bootargs root=/dev/ram rw console=ttyS0,115200

Have a great day,
Yiping

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

chandrashekhar · ‎07-24-2014

Hi Yiping,

Even I tried this setenv bootargs root=/dev/ram rw console=ttyS0,115200. But result is same. It crashes at same point. We kept console=ttyS0,9600 because we were using baudrate 9600 for our test setup.

Regards,

-Chandra