From owner-freebsd-stable Thu Apr 29 2:51:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id A9123157E6 for ; Thu, 29 Apr 1999 02:51:09 -0700 (PDT) (envelope-from tom@embt.com) Received: from gizmo (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id EAA02161 for ; Thu, 29 Apr 1999 04:46:18 GMT (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990429055322.007880d4@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 29 Apr 1999 05:53:22 -0400 To: freebsd-stable@freebsd.org From: Tom Embt Subject: pn0 driver sometimes loses connectivity ?? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I was FTPing a large (~300MB) file from my headless FreeBSD machine to a Windoze 98 one, and somewhere in the middle, it stopped transferring. That's when I found out my telnet sessions had also disconnected, and I couldn't ping the BSD machine at all. This has happened once before, several weeks ago, but I don't remember the circumstances that time. I'm no TCP/IP expert (yet) but I did notice one thing I thought was funny. The BSD machine is a DHCP server for the Win98 one, and after I lost network connectivity I brought up winipcfg for some reason. If I tried to "Renew" the lease, it would refuse, but if I first "Release"'d it, I could successfully renew the lease. Anyway, getting back on the subject... even though I could get a DHCP lease from the FreeBSD box, I could not ping it's IP address or any of it's aliases. So, I grabbed the keyboard of the FreeBSD box and blindly logged in and typed: ifconfig pn0 down ifconfig pn0 up Fixed! All network connectivity was restored. Since it's easy to remedy I am not too worried about this problem, but still I'd like to know if this is a known bug, or if anyone else has had similar problems. I have not been successful in reproducing it, so I don't know if it is related to network load. As I said it has only happened twice so far. System info: FreeBSD 3.1-Stable (cvsup'd 4/19/1999) Kingston KNE110TX network card AOpen AP58 motherboard (33MHz async PCI) Pentium 166MMX @ 189MHz (75x2.5, CPU can do 208MHz) 32MB 10ns SDRAM (can do 83MHz) 1.2GB Seagate Medalist ST31276A IDE 420MB WD Caviar AC2420F IDE Win98 machine has same NIC, connected by a 10base-T hub. pn0: <82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 10 on pci0.9.0 pn0: Ethernet address: 00:c0:f0:2d:bb:72 pn0: autoneg complete, link status good (half-duplex, 10Mbps) pn0: flags=8843 mtu 1500 inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 inet 10.0.0.11 netmask 0xffffff00 broadcast 10.0.0.255 inet 10.0.0.50 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:c0:f0:2d:bb:72 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP Name Mtu Network Address Ipkts Ierrs Ibytes Opkts Oerrs Obytes Coll pn0 1500 00.c0.f0.2d.bb.72 4393772 0 775710224 2130723 0 1675292757 5499 pn0 1500 10/24 odin 4393772 0 775710224 2130723 0 1675292757 5499 pn0 1500 10/24 ns 4393772 0 775710224 2130723 0 1675292757 5499 pn0 1500 10/24 valhalla 4393772 0 775710224 2130723 0 1675292757 5499 If anyone has any idea what's happening, I'd like to hear them. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message