public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Dean Jenkins <Dean_Jenkins@mentor•com>
To: netdev@vger•kernel.org
Cc: "David S. Miller" <davem@davemloft•net>,
	Greg Kroah-Hartman <gregkh@suse•de>, Lucas Stach <dev@lynxeye•de>
Subject: D-Link DUB E100 C1 not working when pinged by "ping 172.17.0.1 -c 1 -s 1965"
Date: Wed, 17 Apr 2013 12:55:37 +0100	[thread overview]
Message-ID: <516E8DB9.9060805@mentor.com> (raw)
In-Reply-To: <516E7E26.10603@linutronix.de>

Hi,

I think the drivers/net/usb/asix.c drivers is broken for the C1 hardware 
of the D-Link DUB E100 USB Ethernet Adapter.

I setup my ARM target board with D-Link DUB E100 C1 USB Ethernet Adapter 
by using
ifconfig eth0 172.17.0.1

On a Linux PC directly connected via an Ethernet cable to the target I do
ping 172.17.0.1 -c 1 -s 1965

but no response is received by the PC.

The ARM target generates errors such as:
[  202.519377] asix 1-2:1.0: eth0: asix_rx_fixup() Bad Header Length
[  202.525593] asix 1-2:1.0: eth0: asix_rx_fixup() Bad RX Length 1925

Note that this following ping works OK by shortening the length by 1:
ping 172.17.0.1 -c 1 -s 1964

Note that this ping test causes IP fragmentation to be used.

I am using a modified 2.6.34.13 kernel with back-ported changes for the 
ASIX driver.

I note that Linux 3.9-rc7 has an additional change to asix_rx_fixup() 
that looks helpful. I backported that commit 
8b5b6f5413e97c3e8bafcdd67553d508f4f698cd to the ARM now
ping 172.17.0.1 -c 1 -s 1965

gives the following run-time kernel errors on the ARM target and the 
ping does not work
[ 1193.872116] asix 1-2:1.0: eth0: asix_rx_fixup() Bad Header Length 
0xffff2f13, offset 6

It is possible that my back-porting is wrong or I have commits missing.

As the ping test is simple, please can anyone with a D-Link DUB E100 C1 
USB Ethernet Adapter run my ping test on any platform to see whether any 
Linux version has a working ASIX driver for this C1 hardware.

I note that the ASIX driver split into multiple files in Linux 3.6 which 
complicates back-porting.

Thanks for any observations of a working ASIX driver for this C1 
hardware variant using my ping test.

Regards,
Dean Jenkins
Mentor Graphics

next prev parent reply	other threads:[~2013-04-17 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 18:21 [PATCH] net/cpsw: don't disable_irqs() after an interrupt has been received Sebastian Andrzej Siewior
2013-04-17  6:19 ` Mugunthan V N
2013-04-17  7:44   ` Sebastian Andrzej Siewior
2013-04-17  8:46     ` Mugunthan V N
2013-04-17  9:02       ` Sebastian Andrzej Siewior
2013-04-17 10:08         ` Mugunthan V N
2013-04-17 10:49           ` Sebastian Andrzej Siewior
2013-04-17 11:44             ` Mugunthan V N
2013-04-17 11:55             ` Dean Jenkins [this message]
2013-04-17 21:12           ` Sebastian Andrzej Siewior
2013-04-17  9:19 ` Sebastian Andrzej Siewior

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=516E8DB9.9060805@mentor.com \
    --to=dean_jenkins@mentor$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dev@lynxeye$(echo .)de \
    --cc=gregkh@suse$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox