I am having problems with networking under heavy loads (tried
2.1.123 and 2.1.125, other versions may have the problem too).
I have an NFS-mounted tree on my box and the problem occurs when
I try to create an ISO 9660 image of it
using mkisofs (the image file itself is on the local disk, though).
After some time of running mkisofs (3 to 30 % of the image size)
the ethernet card stops the communication. After I ifconfig it down and up
again, it starts to work, but the networking is very slow (ping time
around 2000 ms over the local ethernet). After I reboot everything
starts to work well again until some other high networking load
occurs.
The machine is single-CPU P100, 32M RAM, RH5.1. The network card
and the driver is the following:
eth0: 3Com 3c590 Vortex 10Mbps at 0xff80, 00:a0:24:72:f1:30, IRQ 9
8K byte-wide RAM 1:1 Rx:Tx split, autoselect/10baseT interface.
eth0: Overriding PCI latency timer (CFLT) setting of 72, new value is 248.
3c59x.c:v0.99E 5/12/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Kernel messages during the failure follows (host names changed.
"server1" is Sun E5000 w/ solaris 2.5.1, "server2" is Linux 2.1.123
with user-space NFS-daemon:
eth0: Transmit error, Tx status register 90.
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server1.my.domain not responding, still trying
nfs: server server1.my.domain not responding, still trying
nfs: server server1.my.domain not responding, still trying
nfs: server server1.my.domain not responding, still trying
eth0: transmit timed out, tx_status 00 status e000.
eth0: transmit timed out, tx_status 00 status e000.
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
eth0: transmit timed out, tx_status 00 status e000.
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
eth0: transmit timed out, tx_status 00 status e000.
Socket destroy delayed (r=0 w=128)
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
eth0: transmit timed out, tx_status 00 status e000.
Socket destroy delayed (r=0 w=128)
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
eth0: transmit timed out, tx_status 00 status e000.
Socket destroy delayed (r=0 w=128)
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
eth0: transmit timed out, tx_status 00 status e000.
Socket destroy delayed (r=0 w=128)
eth0: transmit timed out, tx_status 00 status e000.
nfs: server server2.my.domain not responding, timed out
nfs_lookup: //links failed, error=-5
nfs_lookup: //links failed, error=-512
eth0: transmit timed out, tx_status 00 status e000.
Socket destroy delayed (r=0 w=128)
eth0: transmit timed out, tx_status 00 status e000.
The following is after ifconfig down/up:
RPC: sendmsg returned error 101
RPC: sendmsg returned error 101
nfs: server server1.my.domain OK
nfs: server server1.my.domain OK
My kernel config is (output of grep '=[ym]' /usr/src/linux/.config):
CONFIG_EXPERIMENTAL=y
CONFIG_M586=y
CONFIG_MODULES=y
CONFIG_KMOD=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_OPTIMIZE=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PNP=y
CONFIG_PNP_PARPORT=m
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_PARIDE_PARPORT=m
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_NAT=y
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_ALWAYS_DEFRAG=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_ROUTER=y
CONFIG_NET_IPGRE=m
CONFIG_IP_ALIAS=y
CONFIG_INET_RARP=m
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
CONFIG_WAN_ROUTER=m
CONFIG_NET_SCHED=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=y
CONFIG_NET_CLS_U32=m
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_POLICE=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
CONFIG_PPP=m
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_UNIX98_PTYS=y
CONFIG_PRINTER=m
CONFIG_PRINTER_READBACK=y
CONFIG_WATCHDOG=y
CONFIG_SOFT_WATCHDOG=m
CONFIG_RTC=y
CONFIG_NVRAM=m
CONFIG_EXT2_FS=y
CONFIG_ISO9660_FS=m
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_PROC_FS=y
CONFIG_NFS_FS=y
CONFIG_NFSD=m
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_CODA_FS=m
CONFIG_AUTOFS_FS=m
CONFIG_DEVPTS_FS=m
CONFIG_NLS=y
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_ADLIB=m
CONFIG_SOUND_GUS=m
CONFIG_GUSMAX=y
CONFIG_SOUND_MPU401=m
CONFIG_SOUND_OPL3SA1=m
CONFIG_SOUND_SOFTOSS=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_VMIDI=m
CONFIG_SOUND_UART6850=m
CONFIG_MAGIC_SYSRQ=y
I am willing to help to debug the problem, feel free to mail me
more questions on the Linux host or suggestions for more testing.
Thanks,
-Yenya
-- \ Jan "Yenya" Kasprzak <kas at fi.muni.cz> http://www.fi.muni.cz/~kas/ \\ PGP: finger kas at aisa.fi.muni.cz 0D99A7FB206605D7 8B35FCDE05B18A5E // \\\ Czech Linux Homepage: http://www.linux.cz/ /// /// I think I'd rather be forced to learn perl than 68020 MMU. -Alan Cox \\\- 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/