From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: L2C boot crash on BCM Capri
Date: Thu, 24 Apr 2014 19:13:36 +0100 [thread overview]
Message-ID: <20140424181336.GW26756@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140424174456.GV26756@n2100.arm.linux.org.uk>
On Thu, Apr 24, 2014 at 06:44:56PM +0100, Russell King - ARM Linux wrote:
> On Thu, Apr 24, 2014 at 10:26:11AM -0700, Kevin Hilman wrote:
> > [ 0.100000] L2C-310 enabling early BRESP for Cortex-A9
> > [ 0.110000] L2C-310 full line of zeros enabled for Cortex-A9
> > [ 0.110000] L2C-310 dynamic clock gating enabled, standby mode enabled
> > [ 0.120000] Unhandled fault: imprecise external abort (0xc06) at 0x44a42d67
>
> The unfortunate thing about imprecise external aborts is that they don't
> tell us what went wrong - we have to guess.
>
> My guess would be that something isn't wired up correctly between the
> Cortex-A9 and L2 controller in Broadcom SoCs. You could try disabling
> the clock gating/standby mode - I doubt it's the FLZ feature as that
> also requires the Cortex-A9 configuration to be changed as well, which
> wouldn't have happened at the point this fault occurred.
>
> Also, it's possible that BRESP could cause it. Try disabling each in
> turn and see what effect they have...
BTW, this is something _you_ will have to do, because _I_ don't have
access to the failing hardware.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
prev parent reply other threads:[~2014-04-24 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 17:14 L2C boot crash on BCM Capri (was: next boot: 47 pass, 2 fail (next-20140424)) Kevin Hilman
2014-04-24 17:26 ` L2C boot crash on BCM Capri Kevin Hilman
2014-04-24 17:44 ` Russell King - ARM Linux
2014-04-24 18:13 ` Russell King - ARM Linux [this message]
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=20140424181336.GW26756@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).