From owner-freebsd-stable Thu Jul 11 3: 5:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12E5237B400; Thu, 11 Jul 2002 03:05:46 -0700 (PDT) Received: from mailhost.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.200.93.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 875D243E31; Thu, 11 Jul 2002 03:05:45 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by mailhost.firstcallgroup.co.uk with local (Exim 3.36 #1) id 17SapO-000OyE-00; Thu, 11 Jul 2002 11:05:38 +0100 To: kgunders@hpb50341.boi.hp.com, mike@sentex.net Subject: Re: intel etherexpress pro and fxp status?? Cc: freebsd-hardware@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <5.1.0.14.0.20020709220904.07342970@192.168.0.12> Message-Id: From: Pete French Date: Thu, 11 Jul 2002 11:05:38 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Thanks, bye." The only threads I remember around this were some people with > specific problems on specific SMP motherboards. I dont recall any mass > problems with the fxp cards... For what its worth, we have deployed some 50 The SMP problems also turned out to be nothing to do with the fxp cards and everything to do with shared interrupts. But cards which generate a lot of interrpts show this up well, hence it first showed up on FXP and has been misrememberd by people as the "fxp problem". just make sure you arent sharing interrupts on an SMP box and you will do fine. -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message