From owner-freebsd-bugs  Wed Nov 24  9:20:25 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id B2B6915062
	for <freebsd-bugs@FreeBSD.org>; Wed, 24 Nov 1999 09:20:06 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id JAA02422;
	Wed, 24 Nov 1999 09:20:06 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 12F9614BC4; Wed, 24 Nov 1999 09:13:41 -0800 (PST)
Message-Id: <19991124171341.12F9614BC4@hub.freebsd.org>
Date: Wed, 24 Nov 1999 09:13:41 -0800 (PST)
From: lyndon@bsd4us.org
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: kern/15075: Intel Etherexpress Pro timeouts when >1 card present
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         15075
>Category:       kern
>Synopsis:       Intel Etherexpress Pro timeouts when >1 card present
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Nov 24 09:20:00 PST 1999
>Closed-Date:
>Last-Modified:
>Originator:     Lyndon Griffin
>Release:        3.3-Release
>Organization:
bsd4us.org
>Environment:
FreeBSD server.server.com 3.3-RELEASE FreeBSD 3.3-RELEASE #1: Mon Oct 11 14:58:54 PDT 1999	root@server.server.com:/usr/src/sys/compile/GENERIC-SMP  i386
>Description:
intel Etherexpress Pro 10/100B Ethernet (one on intel n440bx2 board, other as PCI expansion).
platform is a VAResearch VAR-501, dual pIII stepping 2 500mHz, 512mb RAM.
When only one card is ifconfig'd up and link up, everything is great.  try and
bring up the other card, and within 36 hours both interfaces stop responding.
error on console:
server /kernel: fxp1: device timeout
server /kernel: fxp0: device timeout
repeatedly until reboot.
the only kernel changes are as follows:
	maxusers 120 (changed from 32)
	options SMP (uncommented to build SMP)
	options APIC_IO (uncommented to build SMP)
	options NBUS=2 (uncommented to build SMP)
The problem results in a server that doesn't talk on any network, but is
available via local console or tty
>How-To-Repeat:
link up and ifconfig up both interfaces.  This happens (to me, anyways) regardless
of which interface is on what network.  There is no problem if only one of the interfaces
is config'd and up, regardless of which interface.  I have reproduced this
on three identically-configured machines.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message