From owner-freebsd-current Thu Dec 5 3:12:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21B7D37B404 for ; Thu, 5 Dec 2002 03:12:40 -0800 (PST) Received: from swan.mail.pas.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE1A43EC5 for ; Thu, 5 Dec 2002 03:11:14 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0020.cvx40-bradley.dialup.earthlink.net ([216.244.42.20] helo=mindspring.com) by swan.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18JtuJ-0001hO-00; Thu, 05 Dec 2002 03:11:04 -0800 Message-ID: <3DEF33F9.655D19E0@mindspring.com> Date: Thu, 05 Dec 2002 03:09:45 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Brad Knowles Cc: Craig Reyenga , Christopher J Olson , freebsd-current@freebsd.org, ianf@za.uu.net Subject: Re: Any ideas at all about network problem? References: <51189.1038911493@wcom.com> <003001c29c0f$1a9e0000$0200000a@sewer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Brad Knowles wrote: > Other than that, you should try swapping out as much hardware as > you can -- the cards, the cables, etc.... If possible, you should > also test with other computers (in case the problem is with one > specific machine when it is running 5.0). Swapping 5.0 out for 4.7 will also work. 8-). Seriously: go through the intermediate versions of FreeBSD. Do you have a local CVS tree? Have you ever played the guessing game "higher or lower"? It only takes you at most log2(N)+1 "guesses", and you will have the day the change was made. Then you "cvs diff -r -r", and you will have the code that changed that day. Revert the change in the bus, rl, or other code that's in the code path, and you have your fix. Very easy. > Just because something appears to work perfectly in another OS is > not an indication that there is not anything wrong with that setup. Only with the second OS, when it fails to workaround the problem that the first OS works around without being asked... > However, since there are many potential software components that > could be involved, while testing each component individually between > now and then should theoretically be doable in 10 tests (as > previously mentioned), the combinatorial explosion will be > exceptionally nasty. You only need the delta for the day it was introduced, vs. the day before. Unless it was the KSE import that did it, it's very likely that it will be very obvious, in context. On an 800MHz box, you are talking 6 hours to do this, including all the tests that you have to run. If you have a fast box, you can cut this in half. Or if you have three fast boxes (so you can do branch prediction up and down on two while testing on the third), you can cut this to about 40 minutes. That's less than an hour, and far less time than it's taken the original poster to post messages in this thread, describing the problem. BTW: Good reason to buy hardware for your senior engineers there, and not complain when they ask for it, isn't it? 8-) 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message