Date: Fri, 16 Feb 2001 15:10:02 -0800 (PST) From: "Young, Jason" <Jason.Young@anheuser-busch.com> To: freebsd-bugs@FreeBSD.org Subject: RE: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow f ull-duplex<->half-duplex communication Message-ID: <200102162310.f1GNA2885523@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/24811; it has been noted by GNATS. From: "Young, Jason" <Jason.Young@anheuser-busch.com> To: "'Ken Lui'" <klui@cup.hp.com>, "Young, Jason" <Jason.Young@anheuser-busch.com> Cc: "'freebsd-gnats-submit@FreeBSD.org'" <freebsd-gnats-submit@FreeBSD.org>, wpaul@FreeBSD.org Subject: RE: kern/24811: Networking in FreeBSD 4.2-RELEASE doesn't allow f ull-duplex<->half-duplex communication Date: Fri, 16 Feb 2001 17:05:01 -0600 > I would assume that autonegotiation worked under 3.2-R because I never > had to do anything and it is currently working. I don't have network > stalls nor does my connection wedge for no reason at all after an > indeterminate amount of time. For my work machine anyway, I have > remained at 3.2-R and will probably await for 5.0. One thing you can try on your work 4.2-RELEASE installation is running with the lnc driver instead of pcn. It's still present, but the enhanced pcn driver will claim your card before lnc if both are present. You can accomplish this by simply not building the pcn driver into your kernel, or not loading the module. If you're running GENERIC, you'll need to build a kernel without pcn (but make sure to keep lnc in). This may help isolate the problem to being the new OS, or the new driver. > I personally feel something in the networking code is broken under > 4.2 or is incompatible with certain switch configurations somehow. > The pcn, lnc, and ep drivers don't work correctly with my fxp at > home--they all drop the network connection after a certain amount of > data has been sent through. The baffling part is that they work when > transferring data between my Kayak (pcn, lnc, ep) to two HPUX boxes I > have access to. And those HPUX boxes transfer fine to my fxp 4.2-R > box at home via the WAN. > > Bill, is there anything I can provide that can help you? I'm having a lot of trouble sifting info out of these mails you're sending. I'm not sure if you're still having trouble after the full-duplex setting was forced or not. It sounds like you may have had two problems, a negotiation failure or setting problem that was hosing all traffic from your work box, and then something else after you fixed that that causes communications to break down between your home and work machines only. Is this the case? Bill Paul may be able to help with autonegotiation troubles, but autonegotiation isn't the most reliable thing in the world to begin with. He will need at least the following before he's able to make any attempt to help you: 1) The brand and model of switch you are connected to at work. If available, its software revision would be nice. 2) Its settings for your port. Speed and duplex settings. Autonegotiate settings for speed and duplex, hardcoded or negotiation turned on. Don't guess, don't try to remember. Find out from the switch itself what it's set for right now. 3) Whatever else you can think of that's relevant. Bill is a busy guy and really hates problem reports without adequate detail (just search the mailing list archive). Please make sure to have the above info ready before talking to him. Jason Young CNS - Network Design, Anheuser-Busch (314)577-4597 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102162310.f1GNA2885523>