From owner-freebsd-hackers Fri Jun 21 02:04:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA03366 for hackers-outgoing; Fri, 21 Jun 1996 02:04:04 -0700 (PDT) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA03361 for ; Fri, 21 Jun 1996 02:04:01 -0700 (PDT) Received: (from mbarkah@localhost) by hemi.com (8.6.12/8.6.12) id DAA27179 for freebsd-hackers@freebsd.org; Fri, 21 Jun 1996 03:03:56 -0600 From: Ade Barkah Message-Id: <199606210903.DAA27179@hemi.com> Subject: Help: le0 gets stuck at OACTIVE. To: freebsd-hackers@freebsd.org Date: Fri, 21 Jun 1996 03:03:56 -0600 (MDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, One of our machines has a DEC204-AB (ethernet, 10-BaseT) on it, running FreeBSD 2.1-RELEASE. However, eventually the interface gets stuck in OACTIVE; I can force this condition by doing a ping -f on the interface. The machine has another interface (SMC Ultra C)... I can ping -f on that one all day long without problems. Sometimes doing a 'ifconfig le0 down' followed by an 'ifconfig le0 up' fixes the problem momentarily. Some more background. Here's what dmesg says: | le0 at 0x300-0x31f irq 5 maddr 0xd0000 msize 2048 on isa | le0: DE204-AB ethernet address 08:00:2b:93:3b:e7 Here's ifconfig when it dies: | le0: flags=8c63 mtu 1500 | inet 204.133.181.5 netmask 0xfffffffc broadcast 204.133.181.7 Notice the netmask, there are only two hosts on this subnet. They are connected by a Cat 5 UTP crossover patch cable, 10' in length. The "remote" machine runs a pair of SMC EtherEZs. Ping reports: | .ping: sendto: No buffer space available Followed by netstat -m: | 57 mbufs in use: | 49 mbufs allocated to data | 1 mbufs allocated to packet headers | 5 mbufs allocated to protocol control blocks | 2 mbufs allocated to socket names and addresses | 0/2 mbuf clusters in use | 11 Kbytes allocated to network (64% in use) | 0 requests for memory denied | 0 requests for memory delayed | 0 calls to protocol drain routines When this happens, sometimes the TX light on the card is stuck on, sometimes it's not. netstat -i reports few errors (Oerrs=5, no Collisons, would be a typical output on about 52 Ipkt 54 Opkt, before the flood ping takes its toll.) My guess is that I have a bad NIC and the solution is to buy a new one... but please let me know if you have any ideas of what may be going on (just in case it's something stupid on my end.) Thanks again, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - -------------------------------------------------------------------