Date: Tue, 28 Mar 2006 16:13:23 +0200 From: Pieter de Goeje <pieter@degoeje.nl> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org Subject: Re: new sk driver [was: nve timeout (and down) regression?] Message-ID: <200603281613.24065.pieter@degoeje.nl> In-Reply-To: <20060328020840.GA8189@cdnetworks.co.kr> References: <20060324223317.2069564f@it.buh.tecnik93.com> <200603280221.28996.pieter@degoeje.nl> <20060328020840.GA8189@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 28 March 2006 04:08, Pyun YongHyeon wrote: > On Tue, Mar 28, 2006 at 02:21:28AM +0200, Pieter de Goeje wrote: > > On Monday 27 March 2006 23:48, JoaoBR wrote: > > > On Monday 27 March 2006 15:51, Mark Linimon wrote: > > > > On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote: > > > > > well, the actual driver is trash and unusable and overall crashes > > > > > SMP systems ... so more testing to see if it crashes more? ;) > > > > > > > > As with any other software development project, you have to draw a > > > > line somewhere and say "these things will be in the release and > > > > these things will not be in the release"; otherwise, you will never > > > > have a release at all. > > > > > > > > I am not familiar with the code in this case but if its inclusion > > > > changed enough other things in the system where _everything_ had to > > > > be re-tested then it's not worth the regression. > > > > > > > > These are just the simple facts of (any) software development. > > > > > > well, ok that is completly understandable basicly > > > > > > but this driver is unusable since dec/jan for me, for others probably > > > longer > > > > > > IMO it would make sense to be replaced by Pyuns driver because the > > > original is not functional > > > > > > kind of strange getting a new release with a known not functional > > > driver > > > > > > Jo?o > > > > This is not quite true; I am running 2 systems with the sk driver. One > > of them is a dual core athlon64, and it's network connection is indeed > > flawed unless I change debug.mpsafenet to 0. The other machine is a > > regular athlon64 and has no problems at all. Both systems are running > > 6.1-PRERELEASE amd64. > > Does it happen on my latest sk(4) driver? I'll give it a try. > > I don't have amd64 systems but the driver was tested on i386(SMP) > and sparc64(SMP) and I never see above errors. > The only issue known to me is occasional watchdog timeout error > which I really want to fix. But the watchdog timeout error is hard > to reproduce and I couldn't reproduce the error on my system. > > > With debug.mpsafenet=1, cvsup failes with "protocol error"s on the SMP > > box. Also, I run several Half-Life: Counter-Strike servers on it and > > clients occasionaly receive corrupted UDP packets which cause them to > > drop the connection. However as soon as I changed debug.mpsafenet to 0, > > all problems were gone. > > How about stock sk(4)? Does it have the same issue too? I am using stock sk(4) now. I'm not seeing any watchdog timeout errors. > > > So, maybe you should try changing debug.mpsafenet. > > FYI: the SMP box has an Asus A8V (agp) mobo, and the other box an Asus > > K8V SE. I did try an old realtek (rl(4)) card, it had the same problems and I could fix the problems with that card too by turning off mpsafenet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603281613.24065.pieter>