From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Undefined instruction error on Cortex A57 (aarch64) in init process
Date: Thu, 01 Oct 2015 10:54:45 +0200 [thread overview]
Message-ID: <1631431.E7IDbh3b5M@wuerfel> (raw)
In-Reply-To: <CADTbHxpXCJZdK=iQc+FUxW27-vv1_kHXCeespDXR2fJ8UkfCCg@mail.gmail.com>
On Thursday 01 October 2015 13:02:46 Pankaj Jangra wrote:
> In android system, after system is running for long time say 10 hour,
> some time i am hitting below
> traces:
>
> init[1]: undefined instruction: pc=0000000000401624
> Code: 1a9f00c2 aa1703e0 2a1603e1 9400e1bf (6b1f001f)
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
>
>
Is it always the same address that causes the invalid instruction?
This is the main loop of the init process, so it clearly got executed
correctly before.
Arnd
next prev parent reply other threads:[~2015-10-01 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 7:32 Undefined instruction error on Cortex A57 (aarch64) in init process Pankaj Jangra
2015-10-01 8:54 ` Arnd Bergmann [this message]
2015-10-01 9:01 ` Pankaj Jangra
2015-10-01 13:02 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1631431.E7IDbh3b5M@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox