From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: mvebu: ethernet packets corruption and I/O coherency
Date: Tue, 18 Nov 2014 15:30:35 +0100 [thread overview]
Message-ID: <20141118153035.757fe0fc@free-electrons.com> (raw)
In-Reply-To: <20141118142520.GD24819@dev0.local>
Dear Francesco Dolcini,
On Tue, 18 Nov 2014 15:25:20 +0100, Francesco Dolcini wrote:
> I have seen your patches ("ARM: mvebu: no I/O coherency on non-SMP and
> related updates") regarding I/O coherency and I think it might be
> related to a problem I am experiencing.
>
> I do have a custom board based on Marvell Armada 370 running kernel
> 3.13.11 and I see random outgoing ethernet packet corruption (about 1
> packet every some million) using mvneta driver.
>
> I have tried linux kernel 3.17 without any improvement.
>
> What do you think? Can you backport the fix to 3.13 kernel?
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.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-18 14:30 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 [this message]
2014-11-19 16:01 ` Francesco Dolcini
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=20141118153035.757fe0fc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.