linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: itooo@itooo.com (Greg)
To: linux-arm-kernel@lists.infradead.org
Subject: MVEBU and MVNETA driver
Date: Fri, 19 Apr 2013 15:07:40 +0200	[thread overview]
Message-ID: <5171419C.2090003@itooo.com> (raw)

Hello All,

This is my first post there, let me introduce myself: I am an embedded 
systems designer working in a French ISP. My goal is to design devices 
with a minimalistic software package installed that system/software 
engineers can use as a base for their work. Said in a few words : I'm 
not the kernel expert but I have some knowledge of it.

That being said, I'm currently working with a Marvell ArmadaXP SoC and 
I'm performing the transition from Marvell "Linux Support Package" to 
MVEBU in the 3.8.8 Vanilla.
Having the system up and running was actually quite easy, Thomas 
Petazzoni and his team did a very good job!

I'm facing a problem with ethernet transmission (reception -seems- to be 
fine), at best is it slow (~90Mbps), at worst the kernel OOPSes at 
various locations dealing with memory (tcp_v4_destroy_sock, free_block 
and skb_put seen so far) and ends up crashing right after.
I'm simply using iperf to generate traffic and the system has been 
stable for a while with Marvell's LSP so I can say with confidence the 
hardware is pretty stable.

My question is fairly simple : before complaining about the network 
driver (which might not even be involved in this), what is the starting 
point to gather more information about this problem and what data should 
I provide you to help you advising me ?

Thank you very much!

             reply	other threads:[~2013-04-19 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 13:07 Greg [this message]
2013-04-19 13:12 ` MVEBU and MVNETA driver Willy Tarreau
2013-04-19 14:13   ` Greg
2013-04-19 14:43     ` Willy Tarreau
2013-04-19 14:59       ` Gregory CLEMENT
2013-04-19 16:02         ` Greg
2013-04-22  6:20           ` Willy Tarreau
2013-04-22  8:19             ` Greg
2013-04-22  9:08               ` Willy Tarreau
2013-04-22  9:40                 ` Greg

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=5171419C.2090003@itooo.com \
    --to=itooo@itooo.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 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).