From: Andrew Lunn <andrew@lunn.ch>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-arm-kernel@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ?
Date: Tue, 7 Apr 2015 14:42:09 +0200 [thread overview]
Message-ID: <20150407124209.GA12633@lunn.ch> (raw)
In-Reply-To: <CAK7LNATT8cJoQh+7ZEyUXgMtL0OSYg+69t8wcuNSk+SN+Rwf2g@mail.gmail.com>
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
next prev parent reply other threads:[~2015-04-07 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 3:34 not syncing: Attempted to kill init! exitcode=0x00000004 ? Masahiro Yamada
2015-04-07 7:41 ` Arnd Bergmann
2015-04-07 8:22 ` Masahiro Yamada
2015-04-07 12:22 ` Arnd Bergmann
2015-04-08 6:23 ` Masahiro Yamada
2015-04-07 12:42 ` Andrew Lunn [this message]
2015-04-07 14:09 ` Dennis Mungai
2015-04-08 6:45 ` Masahiro Yamada
2015-04-08 9:23 ` Dennis Mungai
2015-04-08 6:27 ` Masahiro Yamada
2015-05-05 11:54 ` Shawn Guo
2015-05-06 8:56 ` Shawn Guo
2015-05-07 2:30 ` Masahiro Yamada
2015-05-07 11:32 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150407124209.GA12633@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).