Date: Tue, 14 Sep 1999 23:03:31 -0500 From: river <river@theriver.nu> To: freebsd-isp@freebsd.org Subject: RE: fxp0: device timeout Message-ID: <21DC5E98AE1FD311B1290020AFDB6C6E63D1@cx288885-b.okcs1.ok.home.com>
next in thread | raw e-mail | index | archive | help
It sounds as if they have the switch and the netcard config'd differently. I.E. switch half duplex and NIC full duplex or vice versa. I have seen this before and it causes horrible network performance just like you are describing. If the NIC is set to 100mb full duplex have them check the switch. Also, fxp0's are notorious for not detecting full duplex, check the log files if it is set to auto-detect.... hope this helps -----Original Message----- From: Palle Girgensohn [mailto:girgen@partitur.se] Sent: Tuesday, September 14, 1999 7:54 PM To: freebsd-isp@freebsd.org Subject: fxp0: device timeout Hi! fxp0: device timeout... I suppose this probably means that the network is statured, right? Are there any problems running fxp0 in full duplex? This machine is running at a client's site, and they complain it's slow, still the CPU is idle and I get the impression their entire LAN is completely satured. They had problems starting the machine in full duplex so they set the NIC up in simplex (by configuring the network switch it is connected to). Can they just pull the rj45 LAN connection, reconfig the switch and put the cord back in, or do they need to do a ifconfig down && ifconfig up? FreeBSD-3-STABLE from beginning of July. 2 proc SMP, 400 MHz, lots of RAM. Thanks for any input. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21DC5E98AE1FD311B1290020AFDB6C6E63D1>