Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752974AbbDGMWm (ORCPT ); Tue, 7 Apr 2015 08:22:42 -0400 Received: from mout.kundenserver.de ([212.227.126.187]:49454 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752720AbbDGMWj (ORCPT ); Tue, 7 Apr 2015 08:22:39 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Masahiro Yamada , Linux Kernel Mailing List Subject: Re: not syncing: Attempted to kill init! exitcode=0x00000004 ? Date: Tue, 07 Apr 2015 14:22:35 +0200 Message-ID: <19177883.oJbWsfhyVG@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: References: <3196164.8b31S2QWFd@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:CjEW8aPFPBf0yicTpKxAxJC/+wAMm7ZbRWtpxu4ojfGLJM9ct73 eEFfcq8h9Xr0bbxWXLA5lQK5Ego57ziQBWd8N2eLamY/KmRA93BTjmI0dTZfL4WoozKYalU lwKiiHAfCK1hjfB4pd4ie1ALaxb8wVxwcfVmDeLaL7DRDL1UIJ499p9IOyGImru7msLpwCd mD0OuBydl3YFIuXr35a/w== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1476 Lines: 38 On Tuesday 07 April 2015 17:22:32 Masahiro Yamada wrote: > Hi Arnd, > > Thanks for your comment! > > 2015-04-07 16:41 GMT+09:00 Arnd Bergmann : > > On Tuesday 07 April 2015 12:34:30 Masahiro Yamada wrote: > >> > >> What is the cause of the kernel panic? How to fix it? > >> Any hint is very appreciated. > >> > > > > Cortex-A9 usually need to set up the L2 Cache controller, and you > > don't have a node for that. > > > > Can you try adding a DT node for it? You may also have to specify > > the overrides for its aux control register in DT if that is not > > set up right by the boot loader or the power-on defaults. > > I have not checked the L2 (outer) cache yet. > > The L2 cache on our SoC is not a famous IP, but our own implementation. > I will have to implement L2 code as well as the device tree node. > Is there any workaround to boot Linux without L2 cache? It should work normally, I think the only dangerous combination is when the L2 controller is enabled but not configured correctly. It's also quite likely that there is some other problem with your user space image. Are you able to boot the same image inside of qemu or on another hardware that is supported with multi_v7_defconfig? Arnd -- 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/