From: francesco@dolcini.it (Francesco Dolcini)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: mvebu: ethernet packets corruption and I/O coherency
Date: Wed, 19 Nov 2014 17:01:08 +0100 [thread overview]
Message-ID: <20141119160108.GJ24819@dev0.local> (raw)
In-Reply-To: <20141118153035.757fe0fc@free-electrons.com>
Hi Thomas and all
On Tue, Nov 18, 2014 at 03:30:35PM +0100, Thomas Petazzoni wrote:
> It could indeed be related. I have marked the relevant patches in the
> "ARM: mvebu: no I/O coherency on non-SMP and related updates" series as
> to be backported to stable up to v3.8, so when they get accepted, I'll
> take care of backporting them.
I prepared and tested this small patch to fix the problem on kernel
3.13.11 and it seems to fix my ethernet packet corruption problem.
Do you think it is fine?
Do you think that this bug on I/O cache coherency could also trigger some
sporadic random OOPS and kernel panic? I got an OOPS with a broken LR in
skb_segment() and a kernel panic in put_page(), but I was never able to
reproduce any of them.
Thanks,
Francesco
--- a/arch/arm/mach-mvebu/coherency.c
+++ b/arch/arm/mach-mvebu/coherency.c
@@ -124,6 +124,12 @@
{
struct device_node *np;
+ if (!is_smp())
+ {
+ pr_info("Coherency fabric disabled\n");
+ return 0;
+ }
+
np = of_find_matching_node(NULL, of_coherency_table);
if (np) {
struct resource res;
@@ -150,6 +156,9 @@
{
struct device_node *np;
+ if (!is_smp())
+ return 0;
+
np = of_find_matching_node(NULL, of_coherency_table);
if (np) {
bus_register_notifier(&platform_bus_type,
next prev parent reply other threads:[~2014-11-19 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 14:25 ARM: mvebu: ethernet packets corruption and I/O coherency Francesco Dolcini
2014-11-18 14:30 ` Thomas Petazzoni
2014-11-19 16:01 ` Francesco Dolcini [this message]
2014-11-19 16:40 ` Thomas Petazzoni
2014-11-19 16:57 ` Willy Tarreau
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=20141119160108.GJ24819@dev0.local \
--to=francesco@dolcini.it \
--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).