Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753469AbbDHG13 (ORCPT ); Wed, 8 Apr 2015 02:27:29 -0400 Received: from conssluserg003.nifty.com ([202.248.44.41]:58559 "EHLO conssluserg003-v.nifty.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751037AbbDHG11 (ORCPT ); Wed, 8 Apr 2015 02:27:27 -0400 X-Nifty-SrcIP: [74.125.82.54] MIME-Version: 1.0 In-Reply-To: <20150407124209.GA12633@lunn.ch> References: <20150407124209.GA12633@lunn.ch> Date: Wed, 8 Apr 2015 15:27:15 +0900 Message-ID: Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ? From: Masahiro Yamada To: Andrew Lunn Cc: Linux Kernel Mailing List , linux-arm-kernel@lists.infradead.org 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: 3179 Lines: 87 Hi Andrew, 2015-04-07 21:42 GMT+09:00 Andrew Lunn : > 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? > According to Dennis's pointer (https://lkml.org/lkml/2013/7/12/173), this message is a false alarm for Uni-processor implementation. I guess it is not related to the problem I am having now. -- Best Regards Masahiro Yamada -- 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/