From owner-freebsd-current@FreeBSD.ORG Tue May 13 20:54:10 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E3FD1065673 for ; Tue, 13 May 2008 20:54:10 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id B37958FC17 for ; Tue, 13 May 2008 20:54:09 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so4723854fgb.35 for ; Tue, 13 May 2008 13:54:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; bh=903REh/0AN/hBwq1ToJe0GtaqHj5F8sbKLaQL3vyYGo=; b=qQRco5KkSo1NT7IWAAn5lDLeYhQmCeJzDxK3EGUiUVQiXIadlPiOXS2gO/fTFUJNVqsGsOKuLgab+K/LLVeDA0YYMkYkNO4toU43lfX5ntqWjGb8NGpflyPhpCvvVHiS271Uo/mAADbjwn9zxck9hum3CPNTKey0VVMmPqGPO0A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; b=hoQeQ93Nc/EdGuHhJp4X8bd5PyrwWKRpgfE0TqCPXM6ZXL7I785RO1MgKCThCsTKhoBSKv2kvsERtNTZIKdkyjIghrokQKiA2U2pmPRrNtwPWxzJx3X2DKbJwdX0bgDk6fOnm+dtzP4gWDqOA323YgjU0/66qHvEpRCfVhURgEw= Received: by 10.86.87.13 with SMTP id k13mr492267fgb.1.1210712046937; Tue, 13 May 2008 13:54:06 -0700 (PDT) Received: from nebuchadnezzar ( [87.151.42.95]) by mx.google.com with ESMTPS id 4sm310950fgg.6.2008.05.13.13.54.05 (version=SSLv3 cipher=RC4-MD5); Tue, 13 May 2008 13:54:06 -0700 (PDT) Date: Tue, 13 May 2008 22:53:59 +0200 From: Pascal Hofstee To: pyunyh@gmail.com Message-ID: <20080513225359.6219367c@nebuchadnezzar> In-Reply-To: <20080513085938.GB888@cdnetworks.co.kr> References: <20080512181259.04a2f542@nebuchadnezzar> <20080513020927.GD32942@cdnetworks.co.kr> <20080513073809.3b163baa@nebuchadnezzar> <20080513085938.GB888@cdnetworks.co.kr> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, yongari@freebsd.org Subject: Re: nfe0 watchdog timeout 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: Tue, 13 May 2008 20:54:10 -0000 On Tue, 13 May 2008 17:59:38 +0900 Pyun YongHyeon wrote: > > May 10 15:59:31 trinity kernel: ums0: at uhub0 port 1 (addr 2) > > disconnected May 10 15:59:31 trinity kernel: ums0: detached > > May 10 15:59:33 trinity kernel: nfe0: link state changed to DOWN > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Something happend here. But I have no idea why link state was > changed here. > > > May 10 15:59:45 trinity kernel: nfe0: link state changed to UP > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Shomething brought up the link again. If link partner is switch then > I hardly guess this unless you unplug/plug UTP cable. Well ... I can't tell for sure yet, but i am starting to smell a false alarm. It's been about a week now since i switched and have observed the nfe0 link down, link up, followed by perpetual timeout scenario. During this same period the weather around here has started to feel like it's mid-summer with temperatures easily reaching the upper 20s to lower 30s. We share our internet-connection here with about 6 appartments and as it turns out over the last couple of days i have not been the only person who has had some oddball network events happen to him. As it turns out some people have had problems where they simply wouldn't get a link until after they pulled the cable and plugged it back in again, and since about 2 hours ago the power supply of our Gb-switch seems to have become of the persuasion it wants to become a space-heater instead. Initially the Switch's Power LED would still turn green though no link LEDs would light up (and no links were established) and about 15 minutes after that the power LED also no longer turns on. This could very well explain the spurious link losses i've been observing. So i'll likely be getting us a new switch tomorrow (currently have the whole thing running through an old 10-baseT HUB) and keep an eye on things to see how they will develop from there on out. If the nfe problems persist, i'll definitely try the provided suggestions but for now i'll put the investigations on hold. With kind regards, Pascal Hofstee