Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Jun 2002 14:51:33 -0700 (PDT)
From:      Frank Mayhar <frank@exit.com>
To:        pjklist@ekahuna.com
Cc:        stable@FreeBSD.ORG
Subject:   Re: Status of fxp / smp problem?
Message-ID:  <200206202151.g5KLpXJ9065056@realtime.exit.com>
In-Reply-To: <20020620214043573.AAA681@empty1.ekahuna.com@pc02.ekahuna.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206202151.g5KLpXJ9065056>