Re: [PATCH] new device support for forcedeth.c second try

[Kalin KOZHUHAROV]

Carl-Daniel Hailfinger wrote:
> Does the driver work for you when a cable is plugged in? Please test
> normal network traffic.

No, definately not :-( I just saw that I can up the iface and assign it addresses, but when I try to use it...

I tried a ping and on the other host (directly connected with a cross cable) I got a lot of:

eth1: bogus packet size: 1774, status=0x21 nxpg=0x66.
eth1: bogus packet size: 1774, status=0x21 nxpg=0x6d.
eth1: bogus packet size: 1774, status=0x21 nxpg=0x74.
...
eth1: bogus packet size: 1774, status=0x21 nxpg=0x78.
eth1: bogus packet size: 1779, status=0x21 nxpg=0x7f.
eth1: bogus packet size: 1779, status=0x21 nxpg=0x52.
eth1: bogus packet size: 1779, status=0x21 nxpg=0x59.
eth1: bogus packet size: 1779, status=0x21 nxpg=0x60.
eth1: bogus packet size: 1779, status=0x21 nxpg=0x67.

The size seems to fluctuate between 1774 and 1779, more like random.

The iteresting thing is that sometimes it just starts and works!
Like in the middle of a ping (or ping -f), or just starting iptraf (and get into promiscuous mode), the best description that fits here is "random"...

Trying with tcpdump on the othe host:
#  tcpdump  -XX -vvv -n -p -i eth1
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
06:34:30.708109 IP truncated-ip - 23 bytes missing! (tos 0x0, ttl  64, id 0, offset 0, flags [DF], length: 84) 192.168.44.20 > 192.168.44.123: icmp 64: echo request seq 1
       0x0000:  0090 fe52 8bab 000c 6ecd ae29 0800 4500  ...R....n..)..E.
       0x0010:  0054 0000 4000 4001 60c9 c0a8 2c14 c0a8  .T..@.@.`...,...
       0x0020:  2c7b 0800 3864 b42c 0001 6054 d740 e2d5  ,{..8d.,..`T.@..
       0x0030:  0600 0809 0a0b 0c0d 0e0f 1011 1213 1415  ................
       0x0040:  1617 1819 1a1b 1c1d 1e1f 20              ...........
06:34:31.707072 IP truncated-ip - 23 bytes missing! (tos 0x0, ttl  64, id 1, offset 0, flags [DF], length: 84) 192.168.44.20 > 192.168.44.123: icmp 64: echo request seq 2
       0x0000:  0090 fe52 8bab 000c 6ecd ae29 0800 4500  ...R....n..)..E.
       0x0010:  0054 0001 4000 4001 60c8 c0a8 2c14 c0a8  .T..@.@.`...,...
       0x0020:  2c7b 0800 a166 b42c 0002 6154 d740 78d2  ,{...f.,..aT.@x.
       0x0030:  0600 0809 0a0b 0c0d 0e0f 1011 1213 1415  ................
       0x0040:  1617 1819 1a1b 1c1d 1e1f 20              ...........

when doing this on the A7X8N-Deluxe:
# ping  -c 2 192.168.44.123

The MSG "23 bytes missing!" is different (saw 28, 29, etc).

arping seems to work OK, so it is the IP that gets shreded here.

Kalin.

--
||///_ o  *****************************
||//'_/>     WWW: http://ThinRope.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/