From: Francois Romieu <romieu@fr.zoreil.com>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: Holger Hoffstaette <holger.hoffstaette@googlemail.com>,
linux-kernel@vger.kernel.org, stable@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 08:14:01 +0200 [thread overview]
Message-ID: <20130515061401.GA4382@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20130515000715.GA20099@milliways>
Ken Moffat <zarniwhoop@ntlworld.com> :
[...]
> Cc'ing to netdev because I don't think this has had a response, and
A patch has been sent to netdev a few hours ago. It needs more work,
especially testing (hint, hint) as I don't have a proven test case yet.
Please note:
- if you don't use a 8168evl (check your dmesg for the XID line emitted
by the r8169 driver), you are not the experiencing the same bug.
- if you don't enable Tx checksum offload (distro/vendor dependent though
disabled by default in the vanilla driver, see ethtool -k eth0,
ethtool -K eth0 tx on sg on)), you are not the experiencing the same
bug.
- if you are experiencing the same bug, 3.10-rc1 should work again
after reverting e5195c1f31f399289347e043d6abf3ffa80f0005
If someone comes with a failing network capture and a working one, it will
save time. A 64 bytes (max) packet is not correctly transmitted.
--
Ueimor
next prev parent reply other threads:[~2013-05-15 6:14 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 [this message]
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
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=20130515061401.GA4382@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zarniwhoop@ntlworld.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