[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 9 Sep 2016 16:47:43 -0700
From: Tony Lindgren <tony@...mide.com>
To: Matthijs van Duin <matthijsvanduin@...il.com>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
linux-arm <linux-arm-kernel@...ts.infradead.org>,
Peter Hurley <peter@...leysoftware.com>,
Lokesh Vutla <lokeshvutla@...com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [4.8.0-rc1] am335x-evm boot failure: n_tty_receive_buf_common:
"Unable to handle kernel paging request.."
* Matthijs van Duin <matthijsvanduin@...il.com> [160909 15:23]:
> If you look more carefully the first problem is actually a bus error:
> [ 15.776190] Unhandled fault: external abort on non-linefetch (0x1028)
> at 0xf9e3e044
> [ 15.825925] PC is at omap_hwmod_read+0x14/0x28
> [ 15.830583] LR is at omap_rtc_wait_not_busy+0x1c/0x44
>
> I have no idea how the kernel manages to continue after a bus error in
> a driver (inside local_irq_disable even), but I wouldn't be inclined
> to take any later errors seriously.
>
> See also the "4.8 crash on BeagleBone" thread on linux-omap.
Yeah. Just disable omap_l3_smx/noc driver and you should see
a proper stack trace. With the L3 driver we're seeing the trace
for L3 error interrupt.
Regards,
Tony
Powered by blists - more mailing lists