public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Jackson <mpfj-list@mimc.co.uk>
To: Daniel Mack <zonque@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Excessive ethernet interrupts on AM335x board
Date: Wed, 13 Mar 2013 10:36:59 +0000	[thread overview]
Message-ID: <514056CB.6070808@mimc.co.uk> (raw)
In-Reply-To: <CACTFLAPv=OGaWaz+BdPxr56e56c=cx8QYuc9TUK61Bk4WD5=vg@mail.gmail.com>

On 13/03/13 10:32, Daniel Mack wrote:
> On Tue, Mar 12, 2013 at 4:35 PM, Mark Jackson <mpfj-list@mimc.co.uk> wrote:
>> I'm just fighting an issue with ethernet on our custom AM335x board:-
>>
>> # uname -a
>> Linux nanobone 3.9.0-rc2-00113-gd60f039 #139 Tue Mar 12 15:14:01 GMT 2013 armv7l GNU/Linux
>>
>> Every now and then, the whole unit slows to a crawl.  The only indication of any problem is:-
>>
>> (a) the serial tty port becomes much less responsive
>> (b) normal ping times jump from 1ms to >10sec (sometimes >20sec !!)
>> (c) the ethernet interrupt count rockets (see below)
>>
>> I've tried to force the problem by flood pinging from my PC.

<snip>

>> As you can see, when I stop the flood pings, the nfs link is now reported
>> as being lost.
> 
> I had the same problem. Please check this patch, I'm sure it will fix you issue:
> 
>   https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=d35162f89b8f00537d7b240b76d2d0e8b8d29aa0

Brilliant ... that's the one !!  

Cheers
Mark J.

      reply	other threads:[~2013-03-13 10:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 15:35 Excessive ethernet interrupts on AM335x board Mark Jackson
2013-03-12 15:54 ` Mark Jackson
2013-03-13  8:44 ` Koen Kooi
2013-03-13 10:11   ` Mark Jackson
2013-03-13 10:32 ` Daniel Mack
2013-03-13 10:36   ` Mark Jackson [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=514056CB.6070808@mimc.co.uk \
    --to=mpfj-list@mimc.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=zonque@gmail.com \
    /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