From owner-freebsd-bugs Wed Nov 24 12:50:27 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 85D3E155BB for ; Wed, 24 Nov 1999 12:50:23 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id MAA21695; Wed, 24 Nov 1999 12:50:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 24 Nov 1999 12:50:02 -0800 (PST) Message-Id: <199911242050.MAA21695@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Chris Dillon Subject: Re: kern/15075: Intel Etherexpress Pro timeouts when >1 card present Reply-To: Chris Dillon Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15075; it has been noted by GNATS. From: Chris Dillon To: lyndon@bsd4us.org Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/15075: Intel Etherexpress Pro timeouts when >1 card present Date: Wed, 24 Nov 1999 14:45:11 -0600 (CST) On Wed, 24 Nov 1999 lyndon@bsd4us.org wrote: > 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: Interesting. I currently have a large Compaq server with 6 Intel EtherExpress Pro 10/100 and 1 Dual Intel EtherExpress Pro 10/100 -- for a total of 8 interfaces -- running 3.3-STABLE (and initally was running 3.3-RELEASE, as you are) with no problems at all. See my paragraph below, however. > 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) I do recall having some kind of interrupt-related problem which caused many of the interfaces to stop working when I temporarily added a second processor to the machine to play with SMP. Try using a non-SMP kernel and see if that fixes the problem. You may even have to remove the additional processor(s) entirely to fix the problem. If there indeed is a problem related to SMP here, I'm sure some of the developers would love to know about it. Don't ask me though, that certainly isn't my area of expertise. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message