linux-kernel - Re: Undefined instruction error on Cortex A57 (aarch64) in init process

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]

Date:	Thu, 1 Oct 2015 14:02:32 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Pankaj Jangra <jangra.pankaj9@...il.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: Undefined instruction error on Cortex A57 (aarch64) in init
 process

On Thu, Oct 01, 2015 at 01:02:46PM +0530, 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
[...]
>  401624:       6b1f001f        cmp     w0, wzr

Hard to tell. What I can see is that the instruction opcode as read (via
the D-cache) looks fine. I suspect some form of corruption in the
I-cache. Other things like temporary TLB corruption are possible, though
I would expect to see them on the D side as well.

One thing to try is disabling the deeper CPU idle states, only leave
WFI. I've seen failures in the past caused by insufficient TLB or cache
maintenance in firmware.

-- 
Catalin
--
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/