From owner-freebsd-current@FreeBSD.ORG Sun Nov 11 20:25:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98D3916A417 for ; Sun, 11 Nov 2007 20:25:02 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.org [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6316113C480 for ; Sun, 11 Nov 2007 20:25:00 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63049 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IrJLW-000FY9-0X for freebsd-current@freebsd.org; Sun, 11 Nov 2007 20:23:54 +0000 Message-ID: <473764D9.6060609@conducive.net> Date: Sun, 11 Nov 2007 20:23:53 +0000 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <507457093.20071111190706@rulez.sk> <47375ADD.2020001@conducive.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Reproducible problems with re(4) on RELENG_7 and HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2007 20:25:02 -0000 Aryeh Friedman wrote: >> OS build: >> >> FreeBSD chameleon.triligon.to 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Sat Oct 20 >> 22:37:19 UTC 2007 root@chameleon.triligon.local:/usr/obj/usr/src/sys/WBH_ULE >> i386 > > FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Nov 11 > 05:22:44 EST 2007 > aryeh@monster:/usr/obj/FreeBSD/FreeBSD-current/src/sys/MONSTER amd64 > > (I always do a cvs right before kernel builds so it is as recent as > about 10 mins before the above0 > _______________________________________________ My 8- stuff is on another MB (Asus P5K at the moment - restricted to add-on NIC's as the onboard one is a POS.) I *hope* the OP is not planning production use of 8-CURRENT just yet.... and you had mentioned this as a 'while ago' problem in your case, so was that not still under 7-something? Has it recurred under 8-? Can you 'make' it happen again? The OP's network environment can just as easily be a contributor as the NIC & drivers. All these are external, so only a good quality cable back-to-back eliminates them from the equation, and the OP may not have that option, even with site-tech help, on boxen he's never laid eyes on. I'll test what I can to see if it occurs here, but what has been mentioned so far has been done, and has not been problematic - yet. Bill