Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751666AbbEGCag (ORCPT ); Wed, 6 May 2015 22:30:36 -0400 Received: from conssluserg001.nifty.com ([202.248.44.39]:30330 "EHLO conssluserg001-v.nifty.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750865AbbEGCaf (ORCPT ); Wed, 6 May 2015 22:30:35 -0400 X-Nifty-SrcIP: [209.85.212.172] MIME-Version: 1.0 In-Reply-To: References: <20150505115446.GA26467@dragon> Date: Thu, 7 May 2015 11:30:25 +0900 Message-ID: Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ? From: Masahiro Yamada To: Shawn Guo Cc: Linux Kernel Mailing List , linux-arm-kernel 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: 1215 Lines: 40 Hi Shawn, (Sorry for late reply, I's been a vacation in Japan.) 2015-05-06 17:56 GMT+09:00 Shawn Guo : > On Tue, May 5, 2015 at 7:54 PM, Shawn Guo 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. -- 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/