From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/4] ARM: BCM5301X: workaround suppress fault
Date: Mon, 6 Jan 2014 17:09:12 +0100 [thread overview]
Message-ID: <201401061709.13217.arnd@arndb.de> (raw)
In-Reply-To: <1388965601-18329-5-git-send-email-hauke@hauke-m.de>
On Monday 06 January 2014, Hauke Mehrtens wrote:
> Without this patch I am getting a unhandled fault exception like this
> one after "Freeing unused kernel memory":
>
> Freeing unused kernel memory: 1260K (c02c1000 - c03fc000)
> Unhandled fault: imprecise external abort (0x1c06) at 0xb6f89005
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
>
> The address which is here 0xb6f89005 changes from boot to boot, with a
> new build the changes are bigger. With kernel 3.10 I have also seen
> this fault at different places in the boot process, but starting with
> 3.11 they are mostly occurring after the "Freeing unused kernel memory"
> message. I never was able to completely boot to userspace without this
> handler. The abort code is constant 0x1c06. This fault just happens
> once in the boot process I have never seen it happing twice or more.
>
> I also tried changing the CPSR.A bit to 0 in init_early, with this code
> like Afzal suggested, but that did not change anything:
> asm volatile("mrs r12, cpsr\n"
> "bic r12, r12, #0x00000100\n"
> "msr cpsr_c, r12" ::: "r12", "cc", "memory");
>
> Disabling the L2 cache by building with CONFIG_CACHE_L2X0 unset did not
> help.
>
> This workaround was copied from the vendor code including most of the
> comments. It says it they think this is caused by the CFE boot loader
> used on this device. I do not have any access to any datasheet or
> errata document to check this.
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2014-01-06 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:46 [PATCH v5 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU Hauke Mehrtens
2014-01-05 23:46 ` [PATCH v5 1/4] " Hauke Mehrtens
2014-01-05 23:46 ` [PATCH v5 2/4] ARM: BCM5301X: add early debugging support Hauke Mehrtens
2014-01-05 23:46 ` [PATCH v5 3/4] ARM: BCM5301X: add dts files for BCM4708 SoC Hauke Mehrtens
2014-01-06 1:00 ` Thomas Petazzoni
2014-01-06 21:17 ` Hauke Mehrtens
2014-01-07 16:22 ` Arnd Bergmann
2014-01-05 23:46 ` [PATCH v5 4/4] ARM: BCM5301X: workaround suppress fault Hauke Mehrtens
2014-01-06 16:09 ` Arnd Bergmann [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=201401061709.13217.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.