From owner-freebsd-hackers Fri Jun 21 04:05:31 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA08244 for hackers-outgoing; Fri, 21 Jun 1996 04:05:31 -0700 (PDT) Received: from epprod.elsevier.co.uk (epprod.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA08233 for ; Fri, 21 Jun 1996 04:05:26 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by epprod.elsevier.co.uk (8.6.13/8.6.12) with ESMTP id MAA12419 for ; Fri, 21 Jun 1996 12:03:57 +0100 Received: from cadair.elsevier.co.uk (actually host cadair) by snowdon with SMTP (PP); Fri, 21 Jun 1996 12:04:15 +0100 Received: (from dpr@localhost) by cadair.elsevier.co.uk (8.6.12/8.6.12) id MAA15928; Fri, 21 Jun 1996 12:03:30 +0100 Date: Fri, 21 Jun 1996 12:03:30 +0100 Message-Id: <199606211103.MAA15928@cadair.elsevier.co.uk> To: Ade Barkah Cc: freebsd-hackers@FreeBSD.org Subject: Help: le0 gets stuck at OACTIVE. In-Reply-To: <199606210903.DAA27179@hemi.com> References: <199606210903.DAA27179@hemi.com> Reply-To: p.richards@elsevier.co.uk From: Paul Richards X-Attribution: Paul X-Mailer: GNU Emacs [19.30.1], RMAIL, Mailcrypt [3.3] Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Ade" == Ade Barkah writes: Ade> Hello, One of our machines has a DEC204-AB (ethernet, 10-BaseT) Ade> on it, running FreeBSD 2.1-RELEASE. However, eventually the Ade> interface gets stuck in OACTIVE; I can force this condition by Ade> doing a ping -f on the interface. The machine has another Ade> interface (SMC Ultra C)... I can ping -f on that one all day long Ade> without problems. Sometimes doing a 'ifconfig le0 down' followed Ade> by an 'ifconfig le0 up' fixes the problem momentarily. Ade> Some more background. Here's what dmesg says: Ade> | le0 at 0x300-0x31f irq 5 maddr 0xd0000 msize 2048 on isa | le0: Ade> DE204-AB ethernet address 08:00:2b:93:3b:e7 I file a PR about this some time ago. If you re-configure the card to use more than 2K then the problem will go away. I had this problem consistently with a 2K setting and since reconfiguring the card (over 6 months ago) I've not seen it happen again. You'll have to use the dos configure disk you had with the card to change the card's settings.