Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755337AbbDGOJ2 (ORCPT ); Tue, 7 Apr 2015 10:09:28 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:33201 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754210AbbDGOJ0 (ORCPT ); Tue, 7 Apr 2015 10:09:26 -0400 MIME-Version: 1.0 In-Reply-To: <20150407124209.GA12633@lunn.ch> References: <20150407124209.GA12633@lunn.ch> Date: Tue, 7 Apr 2015 14:09:25 +0000 Message-ID: Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ? From: Dennis Mungai To: Andrew Lunn Cc: Masahiro Yamada , linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3430 Lines: 97 Hello Masahiro, Please see this patch here on the LKML: https://lkml.org/lkml/2013/7/12/173 signed off by Stephen Boyd This may be related to the problem you're having. Regards, Dennis. On 7 April 2015 at 12:42, Andrew Lunn wrote: > On Tue, Apr 07, 2015 at 12:34:30PM +0900, Masahiro Yamada wrote: >> Hello experts, >> I hope this is the correct ML to ask this question. >> >> I am struggling to port Linux-4.0-rc7 onto my SoC/board, >> based on ARM cortex-A9 (single CPU), but the kernel fails to boot >> with the error: >> "not syncing: Attempted to kill init! exitcode=0x00000004" >> >> >> I want to use NS16550-compatible UART, Global Timer, and GIC. >> I wrote a simple device tree source for my own board like this: >> >> ------------------>8------------------------------ >> /dts-v1/; >> /include/ "skeleton.dtsi" >> >> / { >> compatible = "socionext,ph1-ld4"; >> >> memory { >> device_type = "memory"; >> reg = <0x80000000 0x20000000>; >> }; >> >> chosen { >> bootargs = "root=/dev/ram0 console=ttyS0,115200"; >> }; >> >> aliases { >> serial0 = &uart0; >> }; >> >> cpus { >> #size-cells = <0>; >> #address-cells = <1>; >> >> cpu@0 { >> device_type = "cpu"; >> compatible = "arm,cortex-a9"; >> reg = <0>; >> }; >> }; >> >> clocks { >> [ 0.000000] Virtual kernel memory layout: >> [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) >> [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) >> [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) >> [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) >> [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) >> [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) >> [ 0.000000] .text : 0xc0208000 - 0xc0d03b7c (11247 kB) >> [ 0.000000] .init : 0xc0d04000 - 0xc0dce000 ( 808 kB) >> [ 0.000000] .data : 0xc0dce000 - 0xc0ecbde0 (1016 kB) >> [ 0.000000] .bss : 0xc0ecbde0 - 0xc0f1aee8 ( 317 kB) >> [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 >> [ 0.000000] Hierarchical RCU implementation. >> [ 0.000000] Additional per-CPU info printed with stalls. >> [ 0.000000] RCU restricting CPUs from NR_CPUS=16 to nr_cpu_ids=1. >> [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 >> [ 0.000000] NR_IRQS:16 nr_irqs:16 16 >> [ 0.000000] GIC CPU mask not found - kernel will fail to boot. >> [ 0.000000] GIC CPU mask not found - kernel will fail to boot. > > I assume you have seen this, have taken a deeper look, and know it is > not your issue? > > Andrew > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/