From owner-freebsd-stable@FreeBSD.ORG Tue Apr 10 13:05:24 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1075716A405 for ; Tue, 10 Apr 2007 13:05:24 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF1713C45B for ; Tue, 10 Apr 2007 13:05:23 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id l3AD58vO069157; Tue, 10 Apr 2007 10:05:09 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: Andrew Reilly Date: Tue, 10 Apr 2007 09:54:19 -0300 User-Agent: KMail/1.9.5 References: <20060327093011.GA21070@math.jussieu.fr> <200603280747.55047.joao@matik.com.br> <20070410042415.GA50510@duncan.reilly.home> In-Reply-To: <20070410042415.GA50510@duncan.reilly.home> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200704100954.20900.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: shih@math.jussieu.fr, freebsd-stable@freebsd.org, Marian Hettwer Subject: Re: watchdog network card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2007 13:05:24 -0000 On Tuesday 10 April 2007 01:24, Andrew Reilly wrote: > Wow. Somehow we've slipped through a one-year timewarp: > > On Tue, Mar 28, 2006 at 07:47:54AM -0300, JoaoBR wrote: > > On Tuesday 28 March 2006 07:40, Andrew Reilly wrote: > > > After the last rebuild on my amd64-x2 box, both the nve ethernet > > > on the motherboard and the dc ethernet that I had been using to > > > work around other problems in the nve driver stopped working in > > > this way. DEVICE_POLLING and ifconfig...polling has got me > > > going again. I thoroughly recommend it. > > > > nve does not run polling mode but dc does > > > > I guess you have an IRQ conflict, nve and dc on the same hw interrupt,= =20 > > and that setting dc in polling mode worked around this problem then > > > > you could check vmstat -i with and without polling enabled to see it > > Thanks for the tip. I haven't been running dc or nve for about > a year, now :-) Nfe has been working beautifully for me, > without polling. I guess that I should have a look to see if > nve has improved in the interim, but it's difficult to make > oneself mess with something that isn't broken... > nfe appears to work much better (also with polling) and flawless. I tried o= ne=20 and another time nve but nfe is what works, at least on amd64 and newer=20 hardware so probably you don't need to waste your time ;) =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br