Date: Fri, 16 Feb 2001 15:50:02 -0800 (PST) From: Ken Lui <klui@cup.hp.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: <200102162350.f1GNo2o88635@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: Ken Lui <klui@cup.hp.com>
To: "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 15:41:40 -0800 (PST)
On Fri, 16 Feb 2001, Young, Jason wrote:
> 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.
Tried it. Same "results." I will be more clear below.
> 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:
Sorry for the confusion. Here are the events that occurred from my
trying to install FreeBSD 4.2 on my Kayak XU with PCnet ethernet
card at work:
1. installed 4.2-release
2. pcn driver recognized my ethernet card
3. tried to ping my HPUX machine on my desk and get no route to host
4. tried to ping my mail HPUX server and get responses of 1sec.
tried to ping my 4.2-release w/ fxp driver at home via WAN and get
high ping times of over 1sec.
5. tried to ssh into my mail server but network delay made it unusable.
6. removed pcn driver and used lnc in the kernel.
7. ping times back to normal and I can ping my HPUX box on my desk.
8. problems occur while I try to transfer a batch of files via scp.
I would get a "stalled" status on files at seemingly random times.
Each time when it would stall, the files have transferred at least
100K. I have around 45 files, each over 100K. These network stalls
would also occur via ftp.
Also at times, when I'm at home, I would ssh into my 4.2-release
with fxp box and then ssh into my work box, with the lnc driver. If
I leave my terminal open and come back to it after around 1/2-1 hour,
my terminal would be unresponsive. I can open up another ssh session
and kill the old session, but I would have to manually close my
initial session's window.
I've also applied the patch discussed in kern/13062 but it didn't
fix these problems.
When I transfer from my work box to my HPUX mail server/workstation,
things work without any problems.
9. I then tried to use the pcn drivers but with the media and mediaopt
switches to use 10baset and full-duplex.
10.the ping times returned to normal and I was once again able to
ping my HPUX box, but the network stalls and network freezes remained.
11.installing a 3Com 509B ethernet card produced the same network stalls
and freezes.
NOTE: the network stalls and freezes only occured when I was linked
between my work 4.2-release box and my home 4.2-release box.
> 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.
I will try to get these pieces of information and forward it here.
> Jason Young
> CNS - Network Design, Anheuser-Busch
> (314)577-4597
Ken
--
Ken Lui 3000 Hanover Street
klui@cup.hp.com Palo Alto, CA 94304 USA
Hewlett-Packard Company invent 1.650.236.5364 FAX 1.650.857.2085
Views within may not be those of the Hewlett-Packard Company
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?200102162350.f1GNo2o88635>