lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAQ0ZWRyndnoSs5D+AcOZB-7hSnhSULTYVu=TRtcGR-CfB9xGQ@mail.gmail.com>
Date:	Wed, 6 May 2015 16:56:28 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ?

On Tue, May 5, 2015 at 7:54 PM, Shawn Guo <shawn.guo@...aro.org> 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"
>
> Hi Masahiro,
>
> Have you track it down to the cause?  I'm asking because I'm seeing the
> same issue with v4.0 on a vendor single Cortex-A9 SoC.

For record, in my case, it's caused by that the user space is built
with VFP support while the SoC does not have VFP.

[    0.091938] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.092049] Setting up static identity map for 0x402bf028 - 0x402bf080
[    0.131141] Brought up 1 CPUs
[    0.131165] SMP: Total of 1 processors activated (1196.85 BogoMIPS).
[    0.131180] CPU: All CPU(s) started in SVC mode.
[    0.132122] devtmpfs: initialized
[    0.133079] VFP support v0.3: not present

Shawn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ