From owner-freebsd-stable@FreeBSD.ORG Tue Mar 28 00:21:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A334816A440 for ; Tue, 28 Mar 2006 00:21:53 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from netlx014.civ.utwente.nl (netlx014.civ.utwente.nl [130.89.1.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08C043D46 for ; Tue, 28 Mar 2006 00:21:52 +0000 (GMT) (envelope-from pieter@degoeje.nl) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by netlx014.civ.utwente.nl (8.11.7/HKD) with ESMTP id k2S0LTW06312 for ; Tue, 28 Mar 2006 02:21:29 +0200 From: Pieter de Goeje To: freebsd-stable@freebsd.org Date: Tue, 28 Mar 2006 02:21:28 +0200 User-Agent: KMail/1.9.1 References: <20060324223317.2069564f@it.buh.tecnik93.com> <20060327185142.GC24315@soaustin.net> <200603271848.19010.joao@matik.com.br> In-Reply-To: <200603271848.19010.joao@matik.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603280221.28996.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-MailScanner-From: pieter@degoeje.nl Subject: Re: new sk driver [was: nve timeout (and down) regression?] 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, 28 Mar 2006 00:21:53 -0000 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 chang= ed > > 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 origin= al > is not functional > > kind of strange getting a new release with a known not functional driver > > Jo=E3o This is not quite true; I am running 2 systems with the sk driver. One of t= hem=20 is a dual core athlon64, and it's network connection is indeed flawed unles= s=20 I change debug.mpsafenet to 0. The other machine is a regular athlon64 and= =20 has no problems at all. Both systems are running 6.1-PRERELEASE amd64.=20 With debug.mpsafenet=3D1, cvsup failes with "protocol error"s on the SMP bo= x.=20 Also, I run several Half-Life: Counter-Strike servers on it and clients=20 occasionaly receive corrupted UDP packets which cause them to drop the=20 connection. However as soon as I changed debug.mpsafenet to 0, all problems= =20 were gone. So, maybe you should try changing debug.mpsafenet. =46YI: the SMP box has an Asus A8V (agp) mobo, and the other box an Asus K8= V SE. Pieter de Goeje