I found out that it was unsupported hardware issue.
Machine A windows98 with a SVEC PNT102TX 10/100 Adapter.
Machine B Linux running RH with a Intel Etherexpress Pro 10/100
Every time I booted my machine there the machines would connect for about 5
minutes with really bad performance so I started using tcpdump to find out
what was going on. Then these exact same errors appeared.
For me it ended up being that the SVEC adapter did not support PCI steering
(IRQ sharing) in Windows98.
My options were to disable the PCI steering or swap the Ethernet adapters in
the two machines.
I swapped them.
But these errors were reported under Linux because of hardware errors coming
from the SVEC adapter.
Hope this additional info helps.
Earle
> My problems seemed to come with me switching over to RedHat 6.0. I'm
> running their 2.2.5-22 kernel. I didn't have these problems when I
> was running Slackware 3.4 with a 2.0.36 kernel.
>
> When saturating the connection (a V.90 connection,say by downloading
> a news active file), if I issue a ping, I get lots of messages about
> byte 8 not being correct:
>
> $ ping iwvisp.com
> PING iwvisp.com (207.141.203.5) from 207.141.203.99 : 56 data bytes
> 64 bytes from 207.141.203.5: icmp_seq=0 ttl=198 time=676.7 ms
> 64 bytes from 207.141.203.5: icmp_seq=1 ttl=198 time=199.8 ms
> 64 bytes from 207.141.203.5: icmp_seq=2 ttl=198 time=1430.4 ms
> wrong data byte #8 should be 0x53 but was 0x52
> 52 81 bc 37 6e 94 6 0 8 9 a b c d e f 10 11 12 13 14
> 15 16 17 18 19 1a 1b 1c 1d 1e 1f
> 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
> 64 bytes from 207.141.203.5: icmp_seq=3 ttl=198 time=1280.1 ms
> wrong data byte #8 should be 0x54 but was 0x53
> 53 81 bc 37 81 95 6 0 8 9 a b c d e f 10 11 12 13 14
> 15 16 17 18 19 1a 1b 1c 1d 1e 1f
> 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
> 64 bytes from 207.141.203.5: icmp_seq=4 ttl=198 time=1459.5 ms
> wrong data byte #8 should be 0x55 but was 0x54
> 54 81 bc 37 2f 97 6 0 8 9 a b c d e f 10 11 12 13 14
> 15 16 17 18 19 1a 1b 1c 1d 1e 1f
> 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
> 64 bytes from 207.141.203.5: icmp_seq=5 ttl=198 time=1149.4 ms
> wrong data byte #8 should be 0x56 but was 0x55
> 55 81 bc 37 79 99 6 0 8 9 a b c d e f 10 11 12 13 14
> 15 16 17 18 19 1a 1b 1c 1d 1e 1f
> 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
> 64 bytes from 207.141.203.5: icmp_seq=6 ttl=198 time=309.6 ms
> 64 bytes from 207.141.203.5: icmp_seq=7 ttl=198 time=444.2 ms
> 64 bytes from 207.141.203.5: icmp_seq=8 ttl=198 time=150.2 ms
> 64 bytes from 207.141.203.5: icmp_seq=9 ttl=198 time=140.2 ms
>
> I don't believe that this is a flow control problem, since it's always
> byte 8. Also, "ifconfig ppp0" doesn't report any errors. I
> don't get this
> problem when the only thing going over the connection is a ping.
>
> Secondly, if I start two simultaneous ftp downloads, the ppp
> connection will appear to hang. I can see by the TX light on my modem
> that packets are being sent, and by the RX light that packets are
> coming back, but "ifconfig ppp0" reports RX and frame errors on every
> packet.
>
> I can completely reproduce these problems. How do I begin to debug
> them?
>
> --
> Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
> Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142
> President, CEO Fax: (760) 499-9152
> My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/