public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Holger Hoffstaette" <holger.hoffstaette@googlemail•com>
To: stable@vger•kernel.org
Cc: linux-kernel@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: r8169 on 3.8.13, 3.9.2, 3.10-rc1, was Re: [ 00/73] 3.8.13-stable review
Date: Wed, 15 May 2013 10:31:50 +0200	[thread overview]
Message-ID: <pan.2013.05.15.08.31.40.496197@googlemail.com> (raw)
In-Reply-To: 20130515000715.GA20099@milliways

On Wed, 15 May 2013 01:07:15 +0100, Ken Moffat wrote:

>  Cc'ing to netdev because I don't think this has had a response, and
> I care because I *might* be seeing the same problem on both 3.9.2 and
> 3.10-rc1, but my take on the problem is slightly different [ details after
> Holger's posting ]

I later isolated the regression to tx offloading, which allows one to
reproduce the problem on the fly (enable: b0rken internets, disable: all
fine). So unless you have tx offloading enabled then whatever you are
seeing has likely nothing to do with *this* problem.

Francois posted a patch to -netdev which I am running as we speak, and the
problem seems fixed for me; tx offloading (in adition to rx/gro) works
again, with no side effects. Please help test!

-h

      parent reply	other threads:[~2013-05-15  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130509222757.917088509@linuxfoundation.org>
     [not found] ` <pan.2013.05.10.10.54.26.943195@googlemail.com>
2013-05-15  0:07   ` r8169 on 3.8.13, 3.9.2, 3.10-rc1, was Re: [ 00/73] 3.8.13-stable review Ken Moffat
2013-05-15  6:14     ` Francois Romieu
2013-05-15 17:09       ` Ken Moffat
2013-05-15 20:39       ` David Miller
2013-05-15 23:15         ` David Miller
2013-05-15  8:31     ` Holger Hoffstaette [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=pan.2013.05.15.08.31.40.496197@googlemail.com \
    --to=holger.hoffstaette@googlemail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=stable@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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