Date: Thu, 11 Nov 2010 13:34:34 -0800 From: Rob Farmer <rfarmer@predatorlabs.net> To: pyunyh@gmail.com Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Pyun YongHyeon <yongari@freebsd.org>, Joel Dahl <joel@freebsd.org> Subject: Re: svn commit: r215132 - head/sys/dev/nfe Message-ID: <AANLkTikCUBj=j7smC7Jpw_p9g1chPsShEhYEFGws7EHY@mail.gmail.com> In-Reply-To: <20101111211808.GE17566@michelle.cdnetworks.com> References: <201011111808.oABI8olX079570@svn.freebsd.org> <20101111183409.GA1011@pluto.vnode.local> <20101111191900.GC17566@michelle.cdnetworks.com> <AANLkTimjUgNLsvqzGNn7SEHZ_=7oF-BJyG2jS7bezy55@mail.gmail.com> <20101111211808.GE17566@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 11, 2010 at 13:18, Pyun YongHyeon <pyunyh@gmail.com> wrote: > Yes, but I think this has nothing to do with the subject. > I think MCP controllers have a silicon bug that does not generate > TX completion interrupts under certain conditions/controller models. > The PR indicates what was really happened which also indicates > possible silicon bug. nve(4) also seems to have some workaround for > that but I wanted to verify it since we don't know what binary blob > did during controller initialization. The message just shows > informational message and does not reset controller so I think that > edge case is already handled by nfe(4). > I have a system that does this same thing - watchdog timeout (missed Tx interrupts) over and over. It also generates so much bogus traffic that all other systems connected to the same switch/hub lose their network connection while the machine is running. Switching to nve resolves the problem. If it can't be fixed, that's fine. Just please don't remove nve - there are systems that need it. -- Rob Farmer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikCUBj=j7smC7Jpw_p9g1chPsShEhYEFGws7EHY>