Date: Tue, 10 Apr 2007 14:24:15 +1000 From: Andrew Reilly <andrew-freebsd@areilly.bpc-users.org> To: JoaoBR <joao@matik.com.br> Cc: shih@math.jussieu.fr, freebsd-stable@freebsd.org, Marian Hettwer <MH@kernel32.de> Subject: Re: watchdog network card Message-ID: <20070410042415.GA50510@duncan.reilly.home> In-Reply-To: <200603280747.55047.joao@matik.com.br> References: <20060327093011.GA21070@math.jussieu.fr> <4427E3B1.3020704@kernel32.de> <20060328104007.GD87799@gurney.reilly.home> <200603280747.55047.joao@matik.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
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, 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... Cheers, -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070410042415.GA50510>