From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: Cortex A9 MP: ARM errata 754323 implementation?
Date: Thu, 3 Sep 2015 10:26:49 +0200 [thread overview]
Message-ID: <55E80449.9040308@de.bosch.com> (raw)
In-Reply-To: <20150903080502.GT21084@n2100.arm.linux.org.uk>
On 03.09.2015 10:05, Russell King - ARM Linux wrote:
> On Thu, Sep 03, 2015 at 09:40:21AM +0200, Dirk Behme wrote:
>> looking through the ARM Cortex A9 errata list [1] I wonder why we don't have
>> a workaround for
>>
>> (754323) Repeated Store in the same cache line might delay the visibility of
>> the Store
>>
>> in the kernel? Or have I missed it?
>
> The policy for errata is not to implement them unless there's a requirement
> to do so - and then the errata should be implemented in board firmware in
> preference to the kernel where possible.
>
> Are you seeing a problem directly attributable to this errata?
I got a report from some internal testing that an issue they see goes
away if they enable 754327. I rejected this because i.MX6 is > r2p0 and
therefore can't be affected by this errata. Looking through the list of
erratas I then found the related 754323 which seems to apply to i.MX6,
but is not implemented.
The issue we are talking about is
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
PC is at kfree+0x10c/0x238
LR is at release_firmware+0x5c/0x70
which is said to be triggered by this code
void kfree(const void *x)
...
page = virt_to_head_page(x);
if (unlikely(!PageSlab(page))) {
BUG_ON(!PageCompound(page));
...
on a custom 3.14.x kernel. I haven't looked into this myself, but at
least two people think that the kmalloc/kfree is correct with the
request_firmware()/release_firmware() usage in the driver.
Best regards
Dirk
next prev parent reply other threads:[~2015-09-03 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 7:40 Cortex A9 MP: ARM errata 754323 implementation? Dirk Behme
2015-09-03 8:05 ` Russell King - ARM Linux
2015-09-03 8:26 ` Dirk Behme [this message]
2015-09-03 17:29 ` Catalin Marinas
2015-09-04 14:00 ` Dirk Behme
2015-09-04 14:23 ` Catalin Marinas
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=55E80449.9040308@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--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.