Date: Thu, 19 Oct 2006 14:18:13 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: em network issues Message-ID: <2a41acea0610191418q6c6fac45xdd9ad824bd6cae2f@mail.gmail.com> In-Reply-To: <20061019190221.GH71000@droso.net> References: <2a41acea0610181046k822afd1qcec4187dc8514187@mail.gmail.com> <b1fa29170610181523t6d240839i887632d6d7576762@mail.gmail.com> <2a41acea0610181531y732cd5sa7bf733cc445491c@mail.gmail.com> <20061018171704.A3851@demos.bsdclusters.com> <4537C126.5000207@FreeBSD.org> <2a41acea0610191140j13d43e12q72fc7697652e222a@mail.gmail.com> <20061019190221.GH71000@droso.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The engineer in our test group has installed 6.2 BETA2 and attempted via a number of tests to reproduce this problem, the machine even shares the em interrupt with usb, and yet so far he has been unsuccessful. I have an Intel driver about to be released, it is close, but not identical to the 6.2 driver, I would very much like to know if it has this same problem. Any volunteers that have this problem willing to load this driver, which will be called 6.2.9 when we release it I believe, and tell me if you still have these watchdogs? BTW, 6.2.9 also has TSO that can be enabled but you need to install the kernel stack patch. I'd like it tested without TSO at least at first. Thanks for the help, Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0610191418q6c6fac45xdd9ad824bd6cae2f>