Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Michael Büsch" <m@bues.ch>, "Pavel Emelyanov" <xemul@parallels.com>
Cc: Eric Dumazet <edumazet@google.com>,
	linux-netdev <netdev@vger.kernel.org>,
	"David S.Miller" <davem@davemloft.net>,
	Mel Gorman <mgorman@suse.de>
Subject: Re: atl1c issues on 3.8.2
Date: Thu, 14 Mar 2013 15:31:00 +0100	[thread overview]
Message-ID: <1363271460.29475.14.camel@edumazet-glaptop> (raw)
In-Reply-To: <1363154258.13690.40.camel@edumazet-glaptop>

On Wed, 2013-03-13 at 06:57 +0100, Eric Dumazet wrote:
> On Tue, 2013-03-12 at 18:09 +0100, Michael Büsch wrote:
> > On Tue, 12 Mar 2013 16:45:44 +0100
> > Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > 
> > > On Tue, 2013-03-12 at 16:17 +0100, Michael Büsch wrote:
> > > > Hi,
> > > > 
> > > > Starting with 3.8.x scp stalls the atl1c based interface on my Asus Eeepc 1011px.
> > > > iperf (for example) does not do that. But after scp stalled the interface,
> > > > iperf transfers fail, too.
> > > 
> > > I am pretty sure David stable list contains the needed fix 
> > > 
> > > http://patchwork.ozlabs.org/bundle/davem/stable/?state=*
> > 
> > No this didn't fix it.
> > 
> > However, I tried to revert 69b08f62e17439ee3d436faf0b9a7ca6fffb78db again,
> > which already caused trouble for me in 3.7
> > and this fixed the issue.
> > 
> > So it seems that this still is the same or a related issue that I reported
> > for 3.7. I just wrongly stated that the problem was fixed in 3.8, because my
> > simple ping test doesn't catch it on 3.8.
> > 
> 
> 


And it seems the possible fix is here :

http://patchwork.ozlabs.org/patch/227666/

  reply	other threads:[~2013-03-14 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 15:17 atl1c issues on 3.8.2 Michael Büsch
2013-03-12 15:45 ` Eric Dumazet
     [not found]   ` <20130312180942.4198e88e@milhouse>
2013-03-13  5:57     ` Eric Dumazet
2013-03-14 14:31       ` Eric Dumazet [this message]
2013-03-14 22:17         ` Michael Büsch
2013-03-14 23:06           ` Eric Dumazet
2013-03-15 19:44             ` Michael Büsch
2013-03-22 11:28               ` Michael Büsch
2013-05-27 16:43                 ` Michael Büsch

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=1363271460.29475.14.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=m@bues.ch \
    --cc=mgorman@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@parallels.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