Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1237084 > unrolled thread
| Started by | Pankaj Jangra <jangra.pankaj9@gmail.com> |
|---|---|
| First post | 2015-10-01 09:40 +0200 |
| Last post | 2015-10-01 15:10 +0200 |
| Articles | 4 — 3 participants |
Back to article view | Back to linux.kernel
Undefined instruction error on Cortex A57 (aarch64) in init process Pankaj Jangra <jangra.pankaj9@gmail.com> - 2015-10-01 09:40 +0200
Re: Undefined instruction error on Cortex A57 (aarch64) in init process Arnd Bergmann <arnd@arndb.de> - 2015-10-01 11:00 +0200
Re: Undefined instruction error on Cortex A57 (aarch64) in init process Pankaj Jangra <jangra.pankaj9@gmail.com> - 2015-10-01 11:10 +0200
Re: Undefined instruction error on Cortex A57 (aarch64) in init process Catalin Marinas <catalin.marinas@arm.com> - 2015-10-01 15:10 +0200
| From | Pankaj Jangra <jangra.pankaj9@gmail.com> |
|---|---|
| Date | 2015-10-01 09:40 +0200 |
| Subject | Undefined instruction error on Cortex A57 (aarch64) in init process |
| Message-ID | <qeGD7-5vh-13@gated-at.bofh.it> |
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
CPU: 0 PID: 1 Comm: init Tainted: G O 3.10.67-g978f332 #15
Call trace:
[<ffffffc000089ccc>] dump_backtrace+0x0/0xf4
[<ffffffc00008a05c>] show_stack+0x10/0x1c
[<ffffffc0003738c0>] dump_stack+0x1c/0x28
[<ffffffc0000aa84c>] panic+0xf8/0x118
[<ffffffc0000af790>] find_new_reaper+0x98/0x154
[<ffffffc0000b0490>] forget_original_parent+0x40/0x1cc
[<ffffffc0000b0630>] exit_notify+0x14/0x16c
[<ffffffc0000b0a4c>] do_exit+0x2c4/0x3ec
[<ffffffc0000b1814>] do_group_exit+0xe8/0xec
[<ffffffc0000c1b8c>] get_signal_to_deliver+0x310/0x3a8
[<ffffffc000089648>] do_signal+0x160/0x180
The objdump of binary around this address is :
401610: eb1f011f cmp x8, xzr
401614: 1a9f00c2 csel w2, w6, wzr, eq
bootchart_count = 0;
}
}
endif
nr = poll(ufds, fd_count, timeout);
401618: aa1703e0 mov x0, x23
40161c: 2a1603e1 mov w1, w22
401620: 9400e1df bl 439d9c <poll>
if (nr <= 0)
401624: 6b1f001f cmp w0, wzr
401628: 54fffccd b.le 4015c0 <main+0x558>
continue;
for (i = 0; i < fd_count; i++) {
40162c: 34fffcb6 cbz w22, 4015c0 <main+0x558>
401630: 510006c9 sub w9, w22, #0x1
401634: aa1703f3 mov x19, x23
401638: 9100052a add x10, x9, #0x1
40163c: 8b0a0ef4 add x20, x23, x10, lsl #3
Could any one please point me to what could be the problem here ? Or
how further i can approach to debug this further.
-Pankaj Kumar
--
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/
[toc] | [next] | [standalone]
| From | Arnd Bergmann <arnd@arndb.de> |
|---|---|
| Date | 2015-10-01 11:00 +0200 |
| Message-ID | <qeHSy-7yF-17@gated-at.bofh.it> |
| In reply to | #1237084 |
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 -- 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/
[toc] | [prev] | [next] | [standalone]
| From | Pankaj Jangra <jangra.pankaj9@gmail.com> |
|---|---|
| Date | 2015-10-01 11:10 +0200 |
| Message-ID | <qeI2e-7Z7-15@gated-at.bofh.it> |
| In reply to | #1237157 |
On Thu, Oct 1, 2015 at 2:24 PM, Arnd Bergmann <arnd@arndb.de> wrote: > 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 Yes Arnd, it always hits the same address. True, It must have been executed lots of time. -Pankaj Kumar -- 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/
[toc] | [prev] | [next] | [standalone]
| From | Catalin Marinas <catalin.marinas@arm.com> |
|---|---|
| Date | 2015-10-01 15:10 +0200 |
| Subject | Re: Undefined instruction error on Cortex A57 (aarch64) in init process |
| Message-ID | <qeLMv-53B-23@gated-at.bofh.it> |
| In reply to | #1237084 |
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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web