From: Tony Lindgren <tony@atomide.com>
To: Matthijs van Duin <matthijsvanduin@gmail.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-arm <linux-arm-kernel@lists.infradead.org>,
Peter Hurley <peter@hurleysoftware.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [4.8.0-rc1] am335x-evm boot failure: n_tty_receive_buf_common: "Unable to handle kernel paging request.."
Date: Fri, 9 Sep 2016 16:47:43 -0700 [thread overview]
Message-ID: <20160909234742.becrs3zb4ihc2mq6@atomide.com> (raw)
In-Reply-To: <CAALWOA_=9fMG156H_XSZBjeckQUK-moDWoRE6_kr-8=Z_-KZuA@mail.gmail.com>
* Matthijs van Duin <matthijsvanduin@gmail.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
next prev parent reply other threads:[~2016-09-09 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 16:50 Grygorii Strashko
2016-09-09 22:23 ` Matthijs van Duin
2016-09-09 23:47 ` Tony Lindgren [this message]
2016-09-09 23:53 ` Matthijs van Duin
2016-09-10 13:10 ` Tony Lindgren
2016-09-12 17:57 ` Grygorii Strashko
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=20160909234742.becrs3zb4ihc2mq6@atomide.com \
--to=tony@atomide.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=matthijsvanduin@gmail.com \
--cc=peter@hurleysoftware.com \
/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
Powered by JetHome