From: Stefan Bader <stefan.bader@canonical.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Subject: Re: rtl8168e-vl dropping tftp ack
Date: Thu, 18 Apr 2013 11:51:20 +0200 [thread overview]
Message-ID: <516FC218.3060002@canonical.com> (raw)
In-Reply-To: <20130417213251.GA13790@electric-eye.fr.zoreil.com>
[-- Attachment #1.1: Type: text/plain, Size: 1660 bytes --]
On 17.04.2013 23:32, Francois Romieu wrote:
> Stefan Bader <stefan.bader@canonical.com> :
> [...]
>> The Xen host has the Realtek NIC:
>>
>> 2:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168B PCI Express Gigabit Ethernet controller
>> [10ec:8168] (rev 06)
>> Subsystem: Micro-Star International Co., Ltd. Device [1462:7798]
>
> Please include the XID line from the stock kernel.
r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at 0xffffc900000cc000,
d4:3d:7e:37:f5:7b, XID 0c900800 IRQ 73
r8169 0000:02:00.0 eth0: jumbo features
[frames: 9200 bytes, tx checksumming: ko]
r8168 Gigabit Ethernet driver 8.035.00-NAPI loaded
eth%d: RTL8168E-VL/8111E-VL at 0xffffc900000cc000, d4:3d:7e:37:f5:7b, IRQ 73
eth0: Identified chip type is 'RTL8168E-VL/8111E-VL'.
>
> [...]
>> I am not sure this is enough to find out what goes wrong but I can
>> add debugging code to the kernel driver or gather other info if
>> someone can hint me which things would be of interest.
>
> (tentative guess: small packet / checksumming problem)
>
> A pcap capture file at the interface of the tftp server with Realtek's
> driver (working) then with the kernel driver (failing) should help a
> lot. No need to play the soft link trick but using a recent kernel will
> be appreciated - fixes will be backported to stable kernels if needed.
>
This was taken with a 3.9-rc7 kernel running on the Xen host, listening on the
tftp server. First run is with the kernel driver and the second pass with
Realteks's driver (had to do minor adaption to handle the removed __devinit/exit
annotations).
[-- Attachment #1.2: guestpxe.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 89740 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-04-18 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 14:31 rtl8168e-vl dropping tftp ack Stefan Bader
2013-04-17 21:32 ` Francois Romieu
2013-04-18 9:51 ` Stefan Bader [this message]
2013-04-18 21:55 ` Francois Romieu
2013-04-19 3:27 ` hayeswang
2013-04-19 6:14 ` Francois Romieu
2013-04-19 7:49 ` hayeswang
2013-04-25 10:56 ` Stefan Bader
2013-04-25 23:03 ` Francois Romieu
2013-04-19 12:54 ` Stefan Bader
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=516FC218.3060002@canonical.com \
--to=stefan.bader@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.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;
as well as URLs for NNTP newsgroup(s).