netgear FA 310tx crashes tulip 1.1.1 & 2.4.0t12
Brought to you by:
cssinnovations,
jgarzik
Sorry have not yet run diagnostics..
When ftping over the fa310tx all goes well until around
20 to 30 meg or so and then it slows down to a crawl.. even after ctrl-C out of ftp and kill -9 the ftp process, the ethernet port is trashed untill a reboot. Tried reversing port to a DAVicom 9102 ethernet port.. worked great..
have tried as modules and installed in kernel for version prior to tulip 1.1.1 .. only as module for tulip 1.1.1
as long as the transfer is under about 20Meg all is fine.
Sorry for the lack of detail -- hey i'm doing good to get this far..
have a similar system running 2.4.0test8, but have not tried pushing over 20Meg in one try.. it seems to be running ok.
Thanks!!!!!
More info - thanks for doing the drivers.. have liked them in the past and feel sure they will get better and better..
ran the tulip-diags after the lite-on crashed the eth1 port... crashes at 20-70megs in on a ftp of a 130Meg file from a 2.0.36 Linux with 3 netgear Fa310tx boards - its been up nonstop for 212 days now and running since may of 99 .. it may have netgear boards with Dec chips on them?? It's a 100Meg local net between the 2.0.36 and the 2.4.0test12. Eth0 on both connect to the world via dsl and eth1 is local
tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Davicom DM9102 adapter at 0xe400.
Davicom DM9102 chip registers at 0xe400:
ffc00000 ffffffff ffffffff 002a6200 002a6000 fc740000 00282002 ffffa2cd
00000000 fff583f8 fffc0000 fffe0000 ffffff29 0000e400 0000e470 fffffece
Port selection is 10mpbs-serial, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for Rx to finish'.
The Tx process state is 'Closing Tx descriptor'.
The transmit unit is set to store-and-forward.
EEPROM size is 6.
PCI Subsystem IDs, vendor 0291, device 8212.
CardBus Information Structure at offset 00000000.
Ethernet MAC Station Address 00:60:6E:38:0F:B8.
EEPROM transceiver/media description for the Davicom DM9102 chip.
Leaf node at offset 30, default media type 0830 (Autosense).
CSR12 direction setting bits 0x80.
6 transceiver description blocks:
Media MII, block type 1, length 14.
MII interface PHY 1 (media type 11).
21140 MII Reset sequence is 2 words: 80 00 No MII initialization sequence.
Media capabilities are 7800, advertising 01e1.
Full-duplex map 5000, Threshold map 1800.
Media 10baseT, block type 128, length 5.
UNKNOW MEDIA DESCRIPTION BLOCK TYPE!
80 00 20 00 40.
Media 10baseT, block type 0, length 5.
AUI or SYM transceiver for 10baseT (media type 0).
CSR12 control port setting 00, command 0x00 0x87.
Media detection by looking for a 0 on bit 3 of the CSR12 control port.
Media 10base2, block type 0, length 5.
AUI or SYM transceiver for 10base2 (media type 1).
CSR12 control port setting 00, command 0x00 0x87.
Media detection by looking for a 0 on bit 3 of the CSR12 control port.
Media 10baseT-Full Duplex, block type 0, length 5.
AUI or SYM transceiver for 10baseT-Full Duplex (media type 4).
CSR12 control port setting 00, command 0x00 0x87.
Media detection by looking for a 0 on bit 3 of the CSR12 control port.
Media 100baseTx Full Duplex, block type 0, length 5.
AUI or SYM transceiver for 100baseTx Full Duplex (media type 5).
CSR12 control port setting 00, command 0x00 0x87.
Media detection by looking for a 0 on bit 3 of the CSR12 control port.
MII PHY found at address 1, status 0x782d.
Index #2: Found a Lite-On 82c168 PNIC adapter at 0xe800.
Lite-On 82c168 PNIC chip registers at 0xe800:
00008000 01ff0000 01000608 073a7000 073a7200 02670055 814c2002 0000fbaf
00000000 00000000 073a7220 077b7ac8 00000024 00000000 00000000 10000001
00000000 00000000 f0041385 000000bf 609640a1 073a70d0 06410010 0001e078
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
Interrupt sources are pending! CSR5 is 02670055.
Tx done indication.
Tx out of buffers indication.
Link passed indication.
Rx Done indication.
A simplifed EEPROM data table was found.
The EEPROM does not contain transceiver control information.
MII PHY found at address 1, status 0x782d.
Logged In: NO
Same problem, FA 310TX crashes tulip, this time it's tulip 1.1.8 & 2.4.3-12 kernel (RedHat 7.1 with all the updates)
An if-down/if-up fixes it; below is my syslog:
kernel: Linux Tulip driver version 1.1.8 (June 16, 2001)
kernel: PCI: Found IRQ 9 for device 00:0e.0
kernel: tulip0: MII transceiver #1 config 3000 status 782d advertising 01e1.
kernel: eth0: Lite-On 82c168 PNIC rev 32 at 0xd087df00, 00:A0:CC:59:0F:4A, IRQ 9.
sysctl: net.ipv4.ip_forward = 0
sysctl: net.ipv4.conf.all.rp_filter = 1
sysctl: kernel.sysrq = 0
network: Setting network parameters: succeeded
network: Bringing up interface lo: succeeded
ifup: Determining IP information for eth0...
pumpd[1960]: starting at (uptime 0 days, 0:43:58) Tue Sep 25 23:16:23 2001
pumpd[1960]: configured interface eth0
ifup: done.
network: Bringing up interface eth0: succeeded
(a little while later, when a few downloads get going...)
kernel: NETDEV WATCHDOG: eth0: transmit timed out
last message repeated 3 times
kernel: nfs: server karrde not responding, still trying
last message repeated 2 times
kernel: NETDEV WATCHDOG: eth0: transmit timed out
last message repeated 4 times
last message repeated 8 times
kernel: nfs: task 3334 can't get a request slot
kernel: nfs: task 3335 can't get a request slot
kernel: nfs: task 3336 can't get a request slot
kernel: NETDEV WATCHDOG: eth0: transmit timed out
(so I do a if-down/if-up...)
pumpd[1960]: disabling interface eth0
pumpd[1960]: terminating as there are no more devices under management
network: Shutting down interface eth0: succeeded
sysctl: net.ipv4.ip_forward = 0
sysctl: net.ipv4.conf.all.rp_filter = 1
sysctl: kernel.sysrq = 0
network: Setting network parameters: succeeded
network: Bringing up interface lo: succeeded
ifup: Determining IP information for eth0...
pumpd[2388]: starting at (uptime 0 days, 0:51:03) Tue Sep 25 23:23:27 2001
pumpd[2388]: configured interface eth0
ifup: done.
network: Bringing up interface eth0: succeeded
kernel: nfs: task 3395 can't get a request slot
kernel: nfs: server karrde OK
and then everything is fine again.