Re: not syncing: Attempted to kill init! exitcode=0x00000004 ?

[Arnd Bergmann]

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 <arnd@xxxxxxxx>:
> > 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/