From owner-freebsd-stable Thu Jun 20 14:51:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A3AC637B40B for ; Thu, 20 Jun 2002 14:51:47 -0700 (PDT) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.12.3/8.12.3) with ESMTP id g5KLpY48068373; Thu, 20 Jun 2002 14:51:34 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.12.3/8.12.2) with ESMTP id g5KLpXac065059; Thu, 20 Jun 2002 14:51:33 -0700 (PDT) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.12.3/8.12.3/Submit) id g5KLpXJ9065056; Thu, 20 Jun 2002 14:51:33 -0700 (PDT) From: Frank Mayhar Message-Id: <200206202151.g5KLpXJ9065056@realtime.exit.com> Subject: Re: Status of fxp / smp problem? In-Reply-To: <20020620214043573.AAA681@empty1.ekahuna.com@pc02.ekahuna.com> To: pjklist@ekahuna.com Date: Thu, 20 Jun 2002 14:51:33 -0700 (PDT) Cc: stable@FreeBSD.ORG Reply-To: frank@exit.com X-Copyright0: Copyright 2002 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII 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 Philip J. Koenig wrote: > Over the past couple/few weeks there were lots of reports of systems > which had trouble with the fxp (Intel Pro 10/100 NIC) drivers, > particularly on SMP systems. > > Are people still having these problems with 4.6-RELEASE or RELENG4? > I've been waiting for an indication this has been fixed, as I've got > a couple of boxes here waiting to be installed, that I wanted to > update first - but not if that problem was still there, as they're > both SMP boxes that use the affected Intel NICs. I don't think the NIC really matters, as I've seen it even without an fxp. I managed to alleviate the problem somewhat by killing the dnetc processes. It appears that pegging CPUs makes the problem much worse (I'm not sure whether pegging one is sufficient or if both should be pegged; based on my experience, though, I strongly suspect the former). I've still had no good suggestions as to what to examine. I looked at the low-level code, but there were no obvious smoking guns there. A few commits in the relevant time period, but none that seemed likely to cause interrupt problems. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message