From owner-freebsd-isp Tue Sep 14 17:54:19 1999 Delivered-To: freebsd-isp@freebsd.org Received: from maild.telia.com (maild.telia.com [194.22.190.3]) by hub.freebsd.org (Postfix) with ESMTP id 377CC152AC for ; Tue, 14 Sep 1999 17:54:13 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from stordatan.telia.com (t2o62p50.telia.com [195.198.198.110]) by maild.telia.com (8.8.8/8.8.8) with ESMTP id CAA28858 for ; Wed, 15 Sep 1999 02:54:12 +0200 (CEST) Received: from partitur.se (localhost [127.0.0.1]) by stordatan.telia.com (8.9.3/8.9.1) with ESMTP id CAA08753 for ; Wed, 15 Sep 1999 02:53:52 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <37DEEE20.69C0958D@partitur.se> Date: Wed, 15 Sep 1999 02:53:52 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Subject: fxp0: device timeout Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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