From owner-freebsd-bugs Tue Nov 28 7:35:49 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from phobia.ms (ns.wmol.com [208.242.83.254]) by hub.freebsd.org (Postfix) with ESMTP id 6D21A37B400 for ; Tue, 28 Nov 2000 07:35:45 -0800 (PST) Received: from desktop (desktop.wmol.com [208.242.83.251]) by phobia.ms (8.11.1/8.11.1) with SMTP id eASFZbg62933; Tue, 28 Nov 2000 10:35:38 -0500 (EST) (envelope-from djhill@novagate.net) Message-ID: <003101c05950$57a10500$fb53f2d0@wmol.com> From: "David" To: "William Schmidt" , "David Greenman" Cc: References: <200011130620.WAA26438@freefall.freebsd.org> <3A2324F0.3AE50202@htslabs.com> Subject: Re: kern/22768: fxp get slow often! Date: Tue, 28 Nov 2000 10:31:55 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I also have an Intel NIC (fxp0). I must manually set it at 10BaseT/UTP for it to work on the network. If its set at 100BaseTX, i can't ping anything except for the interface itself. I've also had the problem with a Linksys 10/100 NIC (dc0). This started happening sometime in the 4.x series. I don't remember having any trouble in FreeBSD 3.x. I know they both work at 100BaseTX, because I used both perfectly running Windows ME. Anyone having any solutions? Or is there a problem with something in the 4.x drivers? Thanks David ----- Original Message ----- From: "William Schmidt" To: "David Greenman" Cc: Sent: Monday, November 27, 2000 10:22 PM Subject: Re: kern/22768: fxp get slow often! > David Greenman wrote: > > > The following reply was made to PR kern/22768; it has been noted by GNATS. > > > > From: David Greenman > > To: Wei-Kai Wu > > Cc: FreeBSD-gnats-submit@FreeBSD.ORG > > Subject: Re: kern/22768: fxp get slow often! > > Date: Sun, 12 Nov 2000 22:10:51 -0800 > > > > >On Sat, Nov 11, 2000 at 07:36:52AM -0800, David Greenman wrote: > > >> >ifconfig fxp0 140.113.214.152 netmask 0xffffff00 media 100BaseTX > > >> >sleep 1 > > >> >ifconfig fxp0 140.113.214.152 netmask 0xffffff00 media autoselect > > >> >running 2 times every hour to keep the speed of ftpd. > > >> I have no idea what you are trying to accomplish with the above, but it is > > >> weird in the extreme. The problem that you are describing sounds like a duplex > > >> negotiation problem with your switch. Try setting both sides to full duplex. > > >> For the FreeBSD side remove your cronjob and then: > > >> ifconfig .... media 100basetx mediaopt full-duplex > > > > > >I am quite sure that the Intel 8-port 10/100 Switch work well. > > >I also tried your suggestion, still not work. > > > > > >In fact, I used the dc0 network card before. > > >I thought the problem may cause by dc0, so I buy the fxp0. > > > > > >Is there any other possibilities? > > > > So you're having the same problem with 'tulip' clones (dc device)? Have you > > tried using a different cable? Does the Intel switch have any error stats that > > might give a clue why the performance is bad? What does "ifconfig fxp0" show > > (speed/duplex) when the performance is low? > > > > -DG > > I have been work on this problem for sum time now and have determined that It seems > to be the data coming in that is slow. For example I can ftp put at about 2.7-3.0 > MB/sec but only ftp get the same file at about 40-120 KB/sec. and that was manually > setting ifconfig for 100baseTX and full-duplex. Manually setting to 10BaseT results > at a rate of 700-900KB/secin both directions. Furthermore If I reboot the same > system to 3.5.1-release the problem goes away and rate in both direction are over > 2.7MB/sec. I have taken all my systems back to 3.5.1 to temporally solve these > problems and left one dual boot system for testing. > > Bill > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message