From owner-freebsd-current@FreeBSD.ORG Sun Nov 11 20:57:09 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 465A816A418 for ; Sun, 11 Nov 2007 20:57:09 +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 0E14A13C494 for ; Sun, 11 Nov 2007 20:57:08 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63111 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IrJrY-000Fgo-CH for freebsd-current@freebsd.org; Sun, 11 Nov 2007 20:57:00 +0000 Message-ID: <47376C9C.50505@conducive.net> Date: Sun, 11 Nov 2007 20:57:00 +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> <473764D9.6060609@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:57:09 -0000 Aryeh Friedman wrote: >> Has it recurred under 8-? > > Yes... but as I said I have had no error messages just random dropouts > and then reconnects after about 15 secs > > >> Can you 'make' it happen again? > > On demand no but everyday use yes. and off-list said: Aryeh Friedman wrote: >> Ok - here's what may be a slightly earlier rev on a Gigabyte GA G33-DS3R: > > For once you won't be accusing me of seeing ghosts ;-) It isn't about 'ghosts'. Its about thorough troubleshooting and reporting of the available facts vs the dollar under the tin-bin side-trips. The NIC and drivers are only a small part of the network environment. Long ago and far away, ethernet ran out of hard-coded MAC ID's (shorter at the time), so we assigned them by manual over-ride. As with setting up duplicate IP's inadvertantly, you can guess that there were problems. Recently I've run into Pegasus II chipset USB ethernet adapters with ... duplicate factory-assigned MAC addresses. Something I hadn't expected to need to watch for in over a decade. And only a problem if they show up on the same LAN, but - go figure - we had it happen on a 192 - internal subnet with just four machines, so... Then there are ARP caches not cleared fast enough when you migrate IP's, faulty routers, hubs, cables, shit-storms on the channel from *other* boxen that block your packets...and so on... None of which driver coders can do SQRT of FA about... Let's find out what we actually have here... 'More facts, please'.... Bill