Bizarre tulip receive problem
"Paul Jones" <[email protected]> Sun, 27 Oct 2002 20:27:06 +0000
| Newsgroups | gmane.linux.drivers.tulip.bugs |
|---|---|
| Message-ID | <[email protected]> |
Hi My D-Link System Inc DFE-500TX Fast Ethernet card is having problems receive packets on a regular and timely basis. For example here is the output of a ping command to a computer on my network PING 192.168.0.177 (192.168.0.177) from 192.168.0.1 : 56(84) bytes of data. 64 bytes from 192.168.0.177: icmp_seq=1 ttl=128 time=1708 ms 64 bytes from 192.168.0.177: icmp_seq=2 ttl=128 time=696 ms 64 bytes from 192.168.0.177: icmp_seq=3 ttl=128 time=0.565 ms 64 bytes from 192.168.0.177: icmp_seq=4 ttl=128 time=1622 ms 64 bytes from 192.168.0.177: icmp_seq=5 ttl=128 time=622 ms 64 bytes from 192.168.0.177: icmp_seq=6 ttl=128 time=0.556 ms 64 bytes from 192.168.0.177: icmp_seq=7 ttl=128 time=1548 ms 64 bytes from 192.168.0.177: icmp_seq=8 ttl=128 time=549 ms 64 bytes from 192.168.0.177: icmp_seq=9 ttl=128 time=0.568 ms As you can see the ping times are wildly erratic. These are the only two computers on the network!! My network card works in Windows, so I'm fairly sure it is not an ethernet, wire, or hub problem. Here is some information that may be useful in debugging the problem ./tulip-diag -aemf tulip-diag.c:v2.15 9/23/2002 Donald Becker ([email protected]) http://www.scyld.com/diag/index.html Index #1: Found a Digital DS21143 Tulip adapter at 0xd800. Digital DS21143 Tulip chip registers at 0xd800: 0x00: ffa08000 ffffffff ffffffff 0ff43000 0ff43200 f0660000 b2422002 fbfffbff 0x40: e0000000 fff483ff ffffffff fffe0000 000010c6 ffff0001 fffbffff 8ff04008 Port selection is 10mpbs-serial, half-duplex. Transmit started, Receive started. The Rx process state is 'Waiting for packets'. The Tx process state is 'Idle'. The transmit threshold is 72. The NWay status register is 000010c6. EEPROM 64 words, 6 address bits. PCI Subsystem IDs, vendor 1186, device 1101. CardBus Information Structure at offset 00000000. Ethernet MAC Station Address 00:40:05:A0:0D:0C. EEPROM transceiver/media description table. Leaf node at offset 30, default media type 0800 (Autosense). 4 transceiver description blocks: Media 10baseT, block type 2, length 12. Serial transceiver for 10baseT (media type 64). CSR13 0001 CSR14 ff3f CSR15 0008. GP pin direction 08a0 GP pin data 0000. Media 10baseT-Full Duplex, block type 2, length 12. Serial transceiver for 10baseT-Full Duplex (media type 68). CSR13 0001 CSR14 ff3d CSR15 0008. GP pin direction 08a0 GP pin data 0000. Media 100baseTx, block type 4, length 8. SYM transceiver for 100baseTx (media type 3). GP pin direction 08a0 GP pin data 0000. No media detection indication (command 80 61). Media 100baseTx Full Duplex, block type 4, length 8. SYM transceiver for 100baseTx Full Duplex (media type 5). GP pin direction 08a0 GP pin data 0000. No media detection indication (command 80 61). No MII transceivers found! Internal autonegotiation state is 'Transmit disabled'. Relavent part of /sbin/lspci -vvv: 00:0b.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 30) Subsystem: D-Link System Inc DFE-500TX Fast Ethernet Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 32 (5000ns min, 10000ns max), cache line size 08 Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at d800 [size=128] Region 1: Memory at df040000 (32-bit, non-prefetchable) [size=128] Expansion ROM at <unassigned> [disabled] [size=256K] Relevant part of cat /proc/interrupts: 10: 48814 XT-PIC eth0 And yes the interrupt number increases from ethereal: No. Time Source Destination Protocol Info 1 0.000000 192.168.0.1 192.168.0.177 ICMP Echo (ping) request 2 1.015895 192.168.0.1 192.168.0.177 ICMP Echo (ping) request 3 1.717519 192.168.0.177 192.168.0.1 ICMP Echo (ping) reply 4 1.717639 192.168.0.177 192.168.0.1 ICMP Echo (ping) reply 5 2.024718 192.168.0.1 192.168.0.177 ICMP Echo (ping) request 6 2.025225 192.168.0.177 192.168.0.1 ICMP Echo (ping) reply 7 3.024776 192.168.0.1 192.168.0.177 ICMP Echo (ping) request 8 4.024757 192.168.0.1 192.168.0.177 ICMP Echo (ping) request 9 4.653732 192.168.0.177 192.168.0.1 ICMP Echo (ping) reply 10 4.653853 192.168.0.177 192.168.0.1 ICMP Echo (ping) reply I am running Redhat 7.3 with the 2.4.19 kernel. The tulip ethernet driver is compiled directly into the kernel. Well I hope that I provided all of the necessary information. Thanks in advance Paul _________________________________________________________________ Choose an Internet access plan right for you -- try MSN! http://resourcecenter.msn.com/access/plans/default.asp _______________________________________________ tulip-bug mailing list, [email protected] To change to digest mode or unsubscribe visit http://www.scyld.com/mailman/listinfo/tulip-bug