From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: keystone: add a work around to handle asynchronous external abort
Date: Fri, 14 Aug 2015 22:56:17 +0100 [thread overview]
Message-ID: <20150814215617.GA7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <55CE633C.10402@ti.com>
On Fri, Aug 14, 2015 at 05:53:00PM -0400, Murali Karicheri wrote:
> We have spend some time already to debug the root cause. Do you have idea on
> how this was hunted down on OMAP that we can learn from? The bad address is
> NULL and it seems to happen very rarely and is not easily reproducible.
> Don't want to put this workaround, but we couldn't track it down either. So
> any help to debug this will be appreciated.
If you try applying Lucas' patch, you should receive the abort earlier
in the kernel boot up, which may help narrow down what is provoking it.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-08-14 21:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 19:13 [PATCH] ARM: keystone: add a work around to handle asynchronous external abort Murali Karicheri
2015-08-14 14:04 ` Murali Karicheri
2015-08-14 14:09 ` Russell King - ARM Linux
2015-08-14 14:20 ` Lucas Stach
2015-08-14 21:55 ` Murali Karicheri
2015-08-14 21:56 ` Russell King - ARM Linux
2015-08-17 14:09 ` Murali Karicheri
2015-08-14 15:14 ` santosh shilimkar
2015-08-14 21:53 ` Murali Karicheri
2015-08-14 21:56 ` Russell King - ARM Linux [this message]
2015-08-17 22:12 ` Murali Karicheri
2015-08-17 22:47 ` Russell King - ARM Linux
2015-08-18 3:09 ` santosh.shilimkar at oracle.com
2015-08-18 8:13 ` Russell King - ARM Linux
2015-08-18 8:28 ` Lucas Stach
2015-08-18 12:06 ` Afzal Mohammed
2015-08-18 8:28 ` Jisheng Zhang
2015-08-18 14:49 ` Murali Karicheri
2015-08-18 20:25 ` Murali Karicheri
2015-08-15 0:01 ` santosh.shilimkar at oracle.com
2015-08-14 14:11 ` Lucas Stach
2015-08-17 14:11 ` Murali Karicheri
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=20150814215617.GA7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).