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] [day] [month] [year] [list]
Message-ID: <20150507113239.GE3162@dragon>
Date:	Thu, 7 May 2015 19:32:41 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ?

On Thu, May 07, 2015 at 11:30:25AM +0900, Masahiro Yamada wrote:
> Hi Shawn,
> (Sorry for late reply, I's been a vacation in Japan.)
> 
> 
> 2015-05-06 17:56 GMT+09:00 Shawn Guo <shawn.guo@...aro.org>:
> > 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.
> 
> Yes, I have already solved my problem.
> 
> In my case,
> 
>  - The interrupt number for the UART device was wrong.  Fixed it.
>  - I regenerated the initramdisk with Buildroot
> 
> and then I could boot the kernel successfully.

Thanks for the update, Masahiro.

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